feat(btw): query work status within the owning profile and session

[YUZHEthefool]

Preflight

• Existing Issues and PRs were searched.
• This follows the current-branch, no-legacy, Python 3.14+ policy.
• Exactly one Agent note is provided by the actual author.

Problem

Users need to inspect work progress without ordinary conversation text being intercepted as a status command or one profile exposing another profile's task state.

Proposal

Make /work and /work status query the latest task for the current profile and origin. Define empty-state, retention, profile lifecycle, and group-session visibility semantics explicitly.

Design: PR #28 and its English proposal. Parent: P / #122. PR #28 is documentation only; this issue tracks follow-up implementation or evaluation.

Associated PR: PR #140 (non-draft; base split/btw-work-command).

Acceptance criteria

• Bare /work and an exact case-insensitive status argument return the latest task state for the selected config_id and origin; ordinary progress questions remain conversation input.
• Pending, running, completed, failed, cancelled, missing, and expired states have accurate localized output.
• Profiles do not share status accidentally; profile reload/removal and manager registration cleanup have defined behavior.
• The UI/docs describe latest-per-origin and group-session query scope. Query authorization follows the current command/session model.
• Only terminal tasks expire under retention; a newer task changes the latest-query target without corrupting an older active task.

Dependencies and delivery

Blocked by: B2 / #124, B3 / #125

Independent of classifier selection; uses the runtime state owned by B3 / #125 rather than adding a second job store.

Implementation anchors

Historical prototype 33ee103a62937db3e930c89ba47a648b75cc7772 provides provenance, not code to copy unchanged:

• astrbot/core/agent/btw/runtime_registry.py: register / unregister / latest_status.
• astrbot/core/agent/btw/work_sessions.py: get_for_origin / terminal retention.
• astrbot/builtin_stars/builtin_commands/commands/work.py: WorkCommands.status.

Integrate with the current tool catalog, Skill snapshot assembly, and authorization service, rechecking current master when implementation begins.

Validation

Commands below are required for the implementation PR, not results claimed by this issue.

Existing current-master regression baseline:

uv run pytest tests/unit/test_builtin_command_extensions.py

Historical prototype tests to adapt with the feature (they are not shipped by documentation-only PR #28):

• tests/unit/test_btw.py
• tests/unit/test_conversation_loop.py

For changed documentation, run pnpm run docs:build from docs/ and make check-md from the repository root. Update OpenAPI and generated outputs together only if the HTTP contract changes.

Out of scope

Listing every task, persistent history, a task-management Dashboard, and task cancellation commands are separate features.

Repository requirements

Follow AGENTS.md, GOVERNANCE.md, and AI_POLICY.md. This issue uses the feature_request template. Keep Python 3.14+, current configuration shapes, existing authorization boundaries, and bilingual feature documentation. A follow-up PR requires human maintainer review and a separate AI-assisted review. Use the feat PR template for the corresponding work.

Author

Agent

Agent note

Codex prepared this development issue at the user's request from PR #28, its discussion, the referenced source, existing tests, and current-master integration points. AI assisted the research and English drafting. Filing this issue changes no runtime behavior and does not claim feature tests or model trials have passed. Remaining decisions concern implementation details and experimental evidence within the stated scope.