[ancongui]

Product workflows keep long forms in the workspace, connect reviewed source inspection to product conversations, and retain uncertain assistant requests across navigation. Project access now uses a compact person search with identifiable results and an explicit selection. Protected consent dialogs adapt to the available space while preserving typed input, keyboard access and visible confirmation actions.

The GitHub Projects workflow adds project-scoped account verification, private board discovery and creation, status mapping, and delivery receipts. Retained-result recovery checks the original claimed action and native owner before local postprocessing; it preserves spent usage and grants no additional coding or tool execution.

Status replies now distinguish current typed checks and the current error from historical worker quotations. The writer receives the classifier draft as untrusted context, preserves the same claimed recovery and verified delivery links, and shares one fact packet across drafting, review and one correction. It adds no execution grant or new draft-length cap.

Documentation follows the account, scope and trust-confirmation steps and includes current screenshots from controlled fixtures.

Validation:

• Studio: 926 unit tests, TypeScript and production build pass; lint and formatting pass. Its 488 capture inputs remain unchanged after the backend-only status fix.
• Status communication: 290 host cases on the initial fix and 99 affected cases on the follow-up pass, with real models, SQL, network and forbidden processes disabled. Independent review confirmed the final source and all 366 historical template rows/bytes are preserved.
• Browser walkthrough: one fresh complete run, 138 passed. All 694 captures are bound to the current frontend, helpers, producers and configuration. The earlier 136/2 result is preserved; its visible-scrollbar defect is fixed and covered.
• Documentation: both strict MkDocs builds, 22 Python tests, 10 Node tests, six responsive gallery cases and five Pages cases pass. The path check verifies 76 outputs and 11,067 local URLs.
• The composed backend retains 202 MCP tools and 373 versioned templates. Source-level compatibility checks are separate from the required native runtime qualification.

PR94 was merged normally into PR93. Current head 997b91bd0909784762dfa629fa21393b8b46292e has parents 5ed901b and 486696c; its Git tree 49f21c4f50f161afcb7abf182f300d400003949b is byte-exact to qualified source 486696ccb982b8e283813c566d3de7dc9e2edfd2. Fresh CI for 997b91b is pending; no new-head success is claimed. Exact 486696 previously passed full Verify 41333778963 and Documentation 41333779009, actual Native250/251 requests, SQL201 in 12 drained packets, REG34/loader35 registration and installed App22 profile/RPC/native-UoW verification. These runtime proofs remain bound to 486696; tree equality is source-content evidence, not a retargeted qualification or new installed adoption. Native tool-boundary proof does not establish whole-controller production confinement. Main is not merged. Screenshots use synthetic API fixtures and do not establish generated CRM acceptance. Runtime deployments remain local.

Known product boundary: Original same-claim reconciliation is accepted at journal 361. One separate seven-check operation has four known successful commands and is held in needs_reconciliation, unknown=false, with no ordinal 5 intent. The original exception was not recorded; a controlled reproduction identified a selected untracked Vitest cache-file guard. Its source fix and the bot current-facts correction remain isolated and uninstalled. The latest real bot reply contradicted the accepted recovery and known results. No rerun, reset, replacement operation, new coding grant or new CRM commit/PR is claimed; acceptance remains 41/87. Source integration does not assert completed CRM end-to-end acceptance or authorize replay.