Annotation loop: file bus first, MCP server second, chat panel deferred
Decision. Stage 1 is .feedback/comments.jsonl as a versioned message
bus. Stage 2 upgrades to an MCP server in the dev process (transport open —
DEC-0005). An embedded chat panel on the site via the Agent SDK is
explicitly deferred.
Why. The file/MCP route delivers ~90% of the experience with ~10% of the moving parts, and the staging is an upgrade path, not a rewrite. The chat panel adds an agent runtime to the site for marginal gain while the methodology is still proving itself.