docs: reconcile protected capability maturity

[seonghobae]

Problem

Protected shipped truth remains exact main@3b38ead2d00f44eb578d0689087b9293b3dabe1e. Multiple canonical maturity records contradict that protected implementation authority:

• merged editor-placeholder accessibility from feat(accessibility): refresh editor placeholder semantics on protected package baseline #131 was still documented as active-PR work;
• merged framework-neutral Markdown package work from feat(package): expose headless deterministic Markdown serialization #114 was still documented as active-PR work in doctoring/package distribution;
• protected ARCHITECTURE.md still labeled the shipped @contextualwisdomlab/cwl-editor/markdown subpath as Proposed / active PR feat(package): expose headless deterministic Markdown serialization #114 / unshipped even though protected package.json exports ./markdown and Accepted ADR 0020 names protected feat(package): expose headless deterministic Markdown serialization #114 as the integration authority;
• protected ARCHITECTURE.md still labeled the shipped CSS @media print boundary as Proposed ADR 0021 / active PR feat(print): add paged-media-safe document output #116 / unshipped even though protected src/styles.css contains the print boundary and Accepted ADR 0021 names protected feat(print): add paged-media-safe document output #116 as implementation authority; and
• protected docs/TRD.md still labeled the already-merged DOCX rich-run hyperlink boundary as Active PR feat(office): preserve bounded hyperlinks in DOCX rich paragraphs #137 / Proposed ADR 0026 / implemented_on_active_pr, despite Accepted ADR 0026 and protected integration through feat(office): preserve bounded hyperlinks in DOCX rich paragraphs #137.

The implementation/package/CSS/Office sides are already correct on protected main. This existing documentation-maturity lane is the canonical writer for the residual stale capability-maturity claims. Fresh owner search found no live competing documentation writer for the remaining TRD hyperlink contradiction; the earlier #139 reconciliation lane is already merged/closed. No runtime/package/release behavior changes here.

Test-first lineage

• Original exact RED cbd14a851481b0de5ba9fa0ee441b1f83d55ccbb required merged placeholder/Markdown records to identify protected-main maturity.
• Repair 536f12ad4322e1290ec658ec620f5bdef9193256 reconciled those doctoring/package-distribution records.
• Architecture RED 69cd3d671102f0a83ea7d4d13d7f97bed21d028f extended src/protectedDocumentationMaturity.test.ts with executable contracts binding architecture maturity to protected package.json, Accepted ADR 0020, protected src/styles.css, and Accepted ADR 0021.
• GREEN source 5de95663afae33a88fb35f0b3c979481fc6e7dbe reconciled the Markdown and print architecture claims.
• Writer-scope predecessor b0e62eadedc5f064d17c82826ae4efbfd1664cec temporarily removed the DOCX/TRD assertion while another owner was believed active. Fresh live ownership inspection disproved that premise: no open alternate owner remains for the protected TRD contradiction.
• DOCX maturity RED 3949217c6dee889feaf1eb6d69b92abfcc664adf adds a machine-checkable contract requiring Accepted ADR 0026, protected PR feat(office): preserve bounded hyperlinks in DOCX rich paragraphs #137, and implemented_on_protected_main, while forbidding the stale Active/Proposed/active-PR claims.
• Current GREEN source head e78d6d840694a5a7511a2763801ec3bad11ff386 updates only authoritative docs/TRD.md text to match already-protected hyperlink behavior and the accepted ADR.

Current exact diff / authority boundary

Current exact Draft head is e78d6d840694a5a7511a2763801ec3bad11ff386 on fix/protected-doc-maturity-20260811, based on protected main@3b38ead2d00f44eb578d0689087b9293b3dabe1e.

The semantic diff remains capability-maturity/document-contract scope only:

• ARCHITECTURE.md;
• docs/TRD.md;
• docs/doctoring/editor-placeholder-accessibility.md;
• docs/doctoring/headless-markdown-package.md;
• docs/package-distribution.md;
• src/editorPlaceholderDocumentation.test.ts; and
• src/protectedDocumentationMaturity.test.ts.

The TRD now records Accepted ADR 0026 and protected #137 as the shipped bounded external-hyperlink authority. It does not broaden hyperlink schemes, Office relationship authority, destination trust, network behavior, or host ownership.

No runtime serializer, package export, stylesheet, Office renderer, release workflow, dependency, persistence, transport, credential, model, collaboration, print-service, or host-authority behavior changes in this lane.

Exact-current-head verification

For exact current head e78d6d840694a5a7511a2763801ec3bad11ff386 at the latest refetch:

• the permanent documentation-maturity test and authoritative TRD now agree on Accepted ADR 0026 / protected feat(office): preserve bounded hyperlinks in DOCX rich paragraphs #137 / implemented_on_protected_main;
• CI 32682480191: in progress / non-passing until terminal success; Office Python 3.11–3.14 are already success, while root coverage/package/demo and cross-engine browser work are still in progress;
• Security Scan 32682480196: queued / non-passing;
• SAST Semgrep 32682480154: queued / non-passing;
• formal submitted reviews: 0;
• unresolved inline review threads: 0;
• GitHub reports the Draft mechanically mergeable.

Earlier workflow generations and test-only RED generations are predecessor evidence and do not transfer. Pending, queued, skipped, cancelled, absent, neutral, failed, stale, predecessor, status-only, synthetic-source, wrong-checkout, and model-only evidence is non-passing.

Governance and integration boundary

Live organization governance must be freshly established before any lifecycle action. Keep this PR Draft/unmerged while #118 owns the frozen v0.6.0 operational-publication boundary and while exact-current-head workflows, qualifying independent approval, and every applicable central exact-source gate remain incomplete.

Do not self-approve, transfer predecessor evidence, weaken gates, synthesize release identity, force-push/destructively rebase, or create a competing documentation-maturity writer.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}