Repository navigation
docs: publish user-approved ecosystem README and install routes #3044
Description
Situation and authorization
The user approved a replacement repository README after browser review and instructed room32 to have room18 update its repositories and publish it. The exact approved patch was received on 2026-10-16; it is integrated at 3c087cdc6fbd4fcb1386aebf156a2f39faa5af41, with one invisible compatibility anchor authorized by room32. No additional visible README edits are authorized.
Independent domain verification found F1: docs/quickstart.md:19–21 promises pinned contract/SHA, plan/checksum/asset/destination/privileges/PATH/rollback and waiting for approval, but the approved brief prompt at README.md:65–66 requests stable npm installation, verification, launch instructions and concepts. The alias keeps the link valid but does not preserve that promise.
Room32 explicitly authorized expanding only to the installation explanation in docs/quickstart.md to resolve F1, preserving the approved README and its alias. Source: room32 message 20261016-195057-room32-gtm-coach-to-room18-ac-tech-lead-v5-resolver-f1-quickstart.md, copied to room18/room-shared/readme-f1-quickstart-authorization.md.
Mandatory acceptance
- Preserve the exact approved README and sole authorized invisible
install-with-a-coding-agentalias. Preserve experience/refinement/reuse positioning, hero before installation, npm/winget/brief prompt routes, platform limitations and backup links. Keep comparison/comparison.md, code-signing, frontend coverage and MarianoBluaEN removed. - Change only quickstart's installation explanation to describe faithfully what the brief prompt asks: stable npm installation, verification that it works, launch instructions, Agents-Matrix/Teams/Rooms. Do not attribute pinned-contract/SHA or plan/checksum/rollback/approval guarantees to that prompt. Preserve the detailed installation guide as an optional separate resource.
- Touch only README.md and docs/quickstart.md in the final delivery; the rework commit changes only that quickstart explanation. No other guides, application, website, npm package, policy, version, release or installation changes. Existing PR2878 remains outside scope and on its own hold.
- Independent verifier rechecks F1, modified claims/links, unchanged README bytes and exact final scope/HEAD, reusing unaffected prior evidence. No global/local install, launch, GUI/input/capture or build is required; report those execution limits honestly. Room32 expressly accepts preserving the approved README without adding visible command-output text; npm guide retains those details.
- Deliver via PR, required checks and normal merge/cleanup flow; do not skip required checks or cancel CI. Record final verification verdict, PR/head/merge/main SHAs, checks and limitations. No build or release requested.
Evidence and workflow
Original patch source: room18/room-shared/readme-publication-approved-source.md; original base b9f1ae598a60927d32924f4ba9487fb719ce4fcc; synchronized integration base fb3cce95340c81fb6187fd9801278521f3817609.
At README integration HEAD 3c087cdc6fbd4fcb1386aebf156a2f39faa5af41: independent evidence confirms approved patch plus alias, 37 valid local references/assets, npm latest/Node>=18/bin metadata, exact winget package identity/source, relevant current capability claims, one-file diff and clean tree; F1 is reproduced by comparing quickstart:19–21 against README:34 and :65–66. Full evidence: room18/room-shared/3044-verification.md, SHA256 3c83786137b2df6f04bdcf930fafde0d28de8e99222661e08d412abc19442bc1.
Selected workflow: docs-implementation-workflow, supplemented by the explicit Role.md plan/consensus gates. Current immutable scope: .ac/plans/3044-approved-ecosystem-readme/plan-v3-approved-ecosystem-readme.md. Same three participants (technical writer, dev-rust verifier, architect-grinch) must explicitly approve v3 before rework; votes recorded externally. First independent verification already followed writer closure and successful workgroup purge; preserve writer/verifier sessions during this rework round and revalidate only affected evidence. Prior broad README issues are not closed by this narrowly approved delivery.
Activity
mblua commentedon Oct 16, 2026
Role.md explicitly requires a canonical versioned plan even for documentation. The minimal delivery plan is .ac/plans/3044-approved-ecosystem-readme/plan-v1-approved-ecosystem-readme.md; writer and independent domain verifier are reviewing v1. Room32 separately authorized invisible HTML aliases to preserve incoming README anchors without altering the approved visual text. No required checks may be skipped or CI cancelled. The original README patch and all other scope constraints remain.
mblua commentedon Oct 16, 2026
Plan v2 reached explicit consensus from ac-technical-writer-v5, ac-dev-rust-v5 and ac-architect-grinch-v5. Plan SHA256: c944867475da956755aacf99508c38721b5d10f660e27cfda5b4c54540c35491. Evidence: .ac/plans/3044-approved-ecosystem-readme/consensus-v2-20261016-193720.md. The approved patch is unchanged visually; the sole incoming anchor confirmed in the repository is install-with-a-coding-agent from docs/quickstart.md:19, retained as an invisible compatibility alias.
mblua commentedon Oct 16, 2026
Independent verification at 3c087cd: FAIL, landing blocked pending interlocutor scope decision. docs/quickstart.md:19–21 promises that the README installation prompt reads a pinned contract, reports asset/checksum/destination/privilege/PATH/rollback and waits for approval. The approved replacement prompt at README.md:65–66 requests npm latest, verification, launch instructions and basic concepts; the compatibility alias at README.md:34 preserves the anchor but not that observable promise. No additional product files changed and no push/PR. Room32 has been asked whether to authorize a minimal quickstart installation-section correction while preserving the approved README. Other verified results: approved patch plus one alias, 37 valid local references/assets, diff check, exact one-file scope, current npm/winget metadata and relevant capability claims. No installs, launch, GUI or build were executed. Full independent evidence: room18/room-shared/3044-verification.md, SHA256 3c83786137b2df6f04bdcf930fafde0d28de8e99222661e08d412abc19442bc1.
Merge pull request #3049 from mblua/docs/3044-approved-ecosystem-readme
mblua commentedon Oct 16, 2026
Delivered via PR #3049, merged at 2026-10-16T21:51:00Z. Final main/merge SHA:
739162c65f31710d8b3d67803ebe8934e6e89189; tested feature head:24028e9fcb142f1db5625f4609e395339c682fa6.The approved ecosystem README, installation routes and invisible compatibility alias are published. The independently discovered quickstart promise mismatch was resolved by the separately authorized two-paragraph installation adjustment; the approved README stayed byte-identical through that rework.
Independent domain verification: PASS. Full PR CI run 38966399287: success, with every currently required context PASS, including frontend, Windows/Linux/macOS regression, four named portable-snapshot matrices and Windows release CLI smoke. Branch, lockfile, debt, formatting, SonarCloud and security checks passed. The initial light run also succeeded. No required check was bypassed and no CI was cancelled.
The designated interlocutor explicitly resolved the inspected nominal release0.45 drift as unrelated to this documentation PR and authorized reusing the exact-head green result without another update/run. No policy changes were made.
Post-merge verification: local main == origin/main == merge SHA; clean worktree; README and docs/quickstart.md identical to the reviewed head; local/remote feature branch removed; only origin/main and origin/HEAD tracking refs remain. Issue auto-closed. No remaining work for this issue. No build was requested; installation, launch and GUI verification were not performed.