Skip to content

FEAT-011: app.agent.update writes project_path via direct UPDATE (no FEAT-006 set_project_path service method) #37

@brettheap

Description

@brettheap

Source: FEAT-011 Polish checkpoint (tasks.md T060/§250) — deferred, non-blocking.

app.agent.update writes the project_path field via a direct SQLite UPDATE rather than through a FEAT-006 service method. FEAT-006 ships set_role / set_label / set_capability but no set_project_path, and the only upstream path that mutates project_path is a full register_agent re-registration.

This breaks the FR-004 "all mutations ride the same service layer the CLI uses" invariant for that one field.

Location: src/agenttower/app_contract/mutations.py:532-540 (see the "Upstream-service-gap note").

Fix: add a set_project_path service method in FEAT-006 and route app.agent.update through it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions