[yia-mw-agent]

Reconciles the public records with main after the E21 repairs landed: the view composition Blueprint and the three Blueprints it amends now state what is implemented, where, and what is still open. Documentation only; no runtime, dependency, API or policy change, and the five public source versions stay at 0.7.6-rc.1.

What changed

• View composition Blueprint. The Status is one table of Blueprint revision, landed commit, pull request, review and reviewed head, in place of a long per-change narrative. It cites the single human-approved fourth revision 7a78e7e as the authority for the whole E2 amendment (neutral whole-result reader, content-policy and server subpaths, readingProfile aliases, strong/em/hr styling, the Lit construction API and the server-only dependency trade-off). PR feat(stack): preserve application card result projection through composition stacks #229's earlier scope record is described as not being an approval. The design text, the earlier approvals and the earlier landed records are unchanged.
• Lit adapter, MCP connector and application setup Blueprints. Their view-composition entries now name main and the actual landed commits instead of the retired integration branch. The connector records the neutral result adapter (deliveredResultFromToolResult, classifyResult removed) and the package directions asserted by scripts/package-direction.ts.
• Evidence attribution. Install, bundle, branding and update claims name the test that runs them. Install is scripts/check-react-pnpm.ts. The emitted browser graph is each stack's exports.test.ts plus scripts/pack1.test.ts. scripts/answer-consumer.test.ts builds a card application and was wrongly cited for an own-catalog bundle. Lower-level card styling is no longer credited with stack-level behavior.
• Hapi. The Blueprint no longer points at an external "reference bridge"; it says the bridge was adapted from an earlier proof of concept that is not part of this repository. The real Hapi history and records are preserved. The init-pair text now says init offers five pairs.
• Guides. The release guide's sequence drops the integration branch and describes current release-candidate preparation, with stable promotion held and nothing published. The public install page gives the stack install line the strict pnpm recipe exercises, and says plainly that no 0.7.x version exists on the registry. The development reference status, package table and tour/demo wording are corrected (the repository is public; Lit and lit-mcp-stack are the private, unpublished packages).

Not changed

• docs/attach-to-existing-backend.md is generated and is untouched.
• demo/tour/src/tour.ts still says the repository is private. Fixing that string is a product-path change that would bump every package version, so it is left for the next product change and the tour README says so.
• The two stacks keep their duplicated lifecycle modules. Duplication alone is not a defect and each stack's tests cover its copy.
• Publication, stable promotion, Ansari adoption and named-host acceptance are separate and open. An earlier first-load observation on a frozen earlier snapshot is not evidence for the final revision.

Checks

• npm run test:docs: 4 files, 125 tests passed (the same count as the boundary repair's record).
• Version policy: mw-version.py check reports no change for this documentation-only diff, and all five versions stay 0.7.6-rc.1.
• Relative links and anchors in every changed file resolve; every commit SHA cited in the changed Blueprints exists on main.
• Reused unchanged, not rerun: the source evidence recorded on the linked reviews for fix: align renderer update failures and default the Lit session #238 through fix: let the Lit stack adopt application card styles and qualify branding through both stack starts #248.

[timeleft--]

Independently reviewed exact head f407d79 in a separate clean Captain checkout with current main78223b5b as ancestor. The fourteen Markdown files match the accepted final documentation scope. The view-composition table preserves the human-approved full design7a78e7eae99285174a11c62d43c1f0035658ec96, earlier approvals and actual code revisions, while the amended Lit/connector/setup records name the settled source and real result/entry contracts. Installation versus emitted-graph evidence, private Lit packages versus public registry packages, historical integration versus current RC preparation, and source versus named-host acceptance are correctly separated. No runtime, API, dependency or generated-guide changes.

Fresh independent validation:125 documentation/boundary tests and3 Blueprint example tests pass; actual PR version policy leaves all five0.7.6-rc.1 versions unchanged; diff, hook and18 LFS pointers pass. All new local link targets and53 owned exact GitHub commit references resolve. Initial broad lexical audit hits were unchanged Markdown examples and external upstream commits, not defects. GitHub API confirms public repository visibility, and current npm metadata confirms no0.7.x publication or React-stack registry release. The private finding dispositions retain supported non-actions without introducing release gates.

The remaining tour wording in a product file and historic dated statements are explicitly identified and do not block this documentation scope. This approval establishes source documentation readiness only. Exact final release artifact qualification, the final-SHA application demonstration and tag, and later npm publication/anonymous installation remain separate. No final host or publication acceptance is implied.