feat(btw): add opt-in conversation and work entry

[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

The prototype bundles dual-loop admission with automatic classification and multiple capability changes. Operators need an explicit enablement boundary that preserves ordinary conversations before a classifier is selected.

Proposal

Introduce opt-in conversation/work admission through the current Agent request path. Keep ordinary conversation usable and make the disabled path behaviorally equivalent to current master. Explicit work submission is supplied by B2 / #124; classifier experiments remain independent.

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 #136 (non-draft; base master).

Acceptance criteria

• With BTW disabled, ProcessStage directly uses the established Agent request path and retains the current model, tool catalog, Skill snapshot, and plugin request behavior.
• With BTW enabled, an admitted ordinary request reaches the conversation loop once; existing wake, command, session LLM, and stop-propagation rules remain effective.
• Enabling the conversation path does not enable work or automatic classification implicitly. Invalid configuration has a defined outcome and no legacy configuration adapter is introduced.
• Profile settings, Dashboard hints, bilingual documentation, and regressions cover both enabled and disabled behavior.

Dependencies and delivery

Blocked by: None.

Provides the enablement boundary for B2 / #124-B10 / #132. R1 / #133-R3 / #135 are not prerequisites.

Implementation anchors

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

• astrbot/core/pipeline/process_stage/stage.py: ProcessStage.initialize / _dispatch_agent.
• astrbot/core/agent/conversation_loop.py: ConversationLoop.process.
• astrbot/core/config/default.py: DEFAULT_CONFIG and configuration metadata.

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_process_stage.py tests/unit/test_config.py

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

• 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

Automatic classifier selection, background execution, provider changes, and capability-assignment UI belong to their own slices.

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.