docs(rfc): move dated checkpoint into ledger

[mikamikasuki]

Goal And Delivered Outcome

• Outcome basis / optional anchor: RFC execution-ledger convention and failing docs-governance smoke.
• Goal/source and gap: The accepted External Evidence Research Capability RFC retained a dated delivery checkpoint in both language versions, although repository convention requires dated checkpoints in paired per-entry ledger files.
• Observable before → after, with the validation row that proves it: The RFC dated headings are replaced by ledger pointers; bilingual ledger entries preserve the checkpoint content and identify the source, former heading, move date, and baseline commit. The docs-governance smoke passes.
• Issue/task and intended base: Documentation governance correction; main.

Author Declaration

• Written by: model_agent — GPT-6 model family, OpenAI Codex

Implemented against

• Specification and revision: docs/architecture/rfcs/ledger/README.md and examples/docs-governance-smoke.py at 1af7dbd43a1629b0356ecd5ee28a426ad45d1d7a.
• Criteria:

Criterion (spec clause)	Disposition	Symbol / path	Test or command
Dated checkpoints live in per-RFC ledger files	implemented	paired ledger/external-evidence-research-capability-v0/2026-10-02-public-github-method-delivery*	uv run --extra test python examples/docs-governance-smoke.py
RFC bodies point to the checkpoint and maintain an execution-ledger appendix	implemented	English and Chinese RFCs; generated STATUS.md indexes	same docs-governance smoke
Moved sections identify their source, prior heading, move date, and baseline commit	implemented	first paragraph of both ledger entries	manual content review

• Self-check before submission: Compared the moved text to the baseline section, verified both mirror links and the versioned capability guide link, and confirmed the checkpoint evidence claims and limitations are unchanged.

Scope And Continuation

• Completed scope and remaining work: The dated checkpoint now follows the repository bilingual per-entry ledger convention. The factual checkpoint content and limitations are preserved.
• Slice boundary / successor: Complete within this documentation correction.

Validation

• Current-main integration check: At main 2f68e3b835c3bfc0e3718373cdb6c72eea99291e, the docs-governance smoke fails on the two dated checkpoint headings this PR moves. The same command passes with this PR head f9ef0d199bb2b9728040cab9041f26805e5c4eee integrated into that main revision (docs-governance smoke ok).

• Tested revision: f9ef0d199bb2b9728040cab9041f26805e5c4eee

• Run state: finished

• Input classes: public_fixture

Check kind	Result	Public-safe evidence / limitation
static	passed	uv run --extra test python examples/docs-governance-smoke.py → docs-governance smoke ok.
static	passed	git diff --check; no whitespace errors.
static	passed	uv run --extra test loopx check over six changed files; public-boundary scan clean, with two warnings because local .loopx/registry.json is absent.

• Coverage and gaps: Documentation structure, local links, bilingual ledger pairing, and the public-boundary scan were checked. Runtime behavior is unchanged.

See validation disclosure guidance.

Frontend / Visual Evidence

• UI impact: none
• Before: N/A
• After: N/A
• States and viewports shown: N/A
• Source data: none
• Attention review: N/A

Type of Change

• Documentation update

LoopX Area

• Public docs or presentation surface (README, protocols, dashboard)

Technical Direction

• Direction / acceptance reference, when applicable: RFC execution-ledger convention in docs/architecture/rfcs/ledger/README.md.

Shared-authority RFC fixture impact

• N/A — this PR does not claim progress against the shared-authority RFC.

Boundary Checklist

• No private state, credentials, raw traces, internal links, or local machine paths are included.
• No maintainer-owned benchmark work is duplicated.
• The change only moves an existing dated checkpoint into the required ledger structure and updates generated indexes.
• UI impact is none.
• The commit includes a DCO Signed-off-by trailer.