[documentation-writing-alignment] State migration skill conditions without session-specific wording #561

Context and request

Agents need durable v8 and Zensical migration framing that does not depend on the session that authored it. This delivery owns only the time/session-dependent framing released by the existing integration coordinator in two skills.

Exact source and region handback

The verified main source is 64ffb1d87f86bd5d487891fdb140b78385a00531.

Use exact text/context anchors; incidental line movement does not revoke a linguistic handback. The grant releases regions, not whole skills or proposal contracts. Existing template/caller/authoring proposal owners keep all other changes.

Protected scope and acceptance criteria

• Keep exact caller YAML, template/version selection, TestData, layout options and conditions, migration actions, optional-versus-required distinctions, stop conditions, triggers/front matter, links and normative force unchanged.
• Do not widen migration scope, remove a supported layout, universalize an example or assert that every current template has the old layout.
• Keep procedures imperative and descriptions clear, present-tense en-US. General version-specific migration instructions remain valid and are not deleted as history.
• Read both skills in full and record concrete before/after and unchanged/protected evidence.
• One fresh-main focused draft PR opens after the first coherent commit and uses small follow-ups. It changes no live consumer repository, metadata structure, framework/runtime behavior or site design.
• Existing Markdown/link/front-matter checks verify the deliverable. No new dependency, enforcement tool or repository prose-snapshot test is added.

Apply the fixed Natural Language, Writing Guide, Documentation Model and applicable guide format. Preserve the exact templates and conditions even where other proposal work remains unmerged.

Technical decisions and before/after expectations

The branch migration-framing-prose starts at the verified main commit. Both complete skills and the fixed MSX sources are reviewed. Before editing, a session-local JSON record defines the following exact replacements and checks. No repository test or enforcement tool is added.

Before-edit evidence: all three recorded target replacements are absent and their exact source spans are present. The one-off comparison verifies both immutable source blobs and every source text byte outside those spans, with CRLF normalized to LF. It also compares ordered front matter, headings, fenced blocks, inline literals, and links exactly: v8 has 1/11/6/62/13; Zensical has 1/8/2/73/7. The one local skill link resolves. No separate plugin link or front-matter checker exists in this checkout; the existing YAML parser accepts both front-matter maps, and both plugin metadata JSON files parse.

Existing baseline checks: the repository Markdown configuration reports zero issues for both files; the repository spelling configuration passes; git diff --check passes. The existing textlint command reports No rules found before any source edit. This baseline failure is not a passing natural-language check. No tool was installed during the baseline. The final check method and result are recorded below.

Delivery evidence

The focused draft PR opened after the first real commit, c43c36e1012859388d378a838c27e318893d933c, on migration-framing-prose. The second small commit, 21cc8b3c5f6f5bce6fe245ffd181fea5d0c496c4, contains only the two-line Zensical framing. Both commits are pushed. The final head is 21cc8b3c5f6f5bce6fe245ffd181fea5d0c496c4; the main base is 64ffb1d87f86bd5d487891fdb140b78385a00531. Live ownership and unchanged main source blobs were rechecked immediately before each commit. The worktree is clean.

Only the two exclusive skill files change: 11 insertions and 8 deletions across the three recorded framing spans. Both full skills are reviewed. The v8 head blob is be52d02d835f639786cff51122c3ecd873f98eb0; the Zensical head blob is c0f49052a8b25dde9be6f3cf60e45ed30926ca11. Every recorded replacement matches the final text. Reversing only those replacements reproduces every source text byte, with CRLF normalized to LF. All ordered protected collections remain exact: v8 front matter/headings/fences/inline literals/links 1/11/6/62/13; Zensical 1/8/2/73/7.

The exact caller YAML, template/version selection, TestData, anatomy tree, layout alternatives, optional assets/test phases, migration actions, stop conditions, and normative force remain unchanged. Documentation moves only under the existing requested-migration condition; otherwise preserve the working configuration and report the difference. Zensical still requires a successful site build before removal of obsolete active configuration. No example becomes universal, and no consumer upgrade command runs. All other skills, proposal branches, runtime, metadata, site design, dependencies, and repository tests remain unchanged.

Local checks pass: the repository Markdown configuration reports zero issues for both files; the repository spelling configuration passes; git diff --check passes; both YAML front-matter maps and both unchanged metadata JSON files parse; the one relative skill target resolves. All 20 links remain exact. No separate plugin link/front-matter checker exists in this checkout, and unchanged external URLs are not claimed as network-checked.

The plain textlint CLI reports no rules before editing and cannot resolve its configured packages on this host. After the actual missing-package failure, the existing tools were restored only in the npm cache. The existing textlint 15.8.0, terminology 5.2.16, and comments 1.3.0 rules pass through their installed API with the unchanged repository options and Markdown plugin: zero messages on both immutable source files and both final files. Anonymous incorrect-term and comment-filter probes confirm that the rules and filter execute. No repository tooling or dependency is added. The session-local exact-content and textlint JSON evidence identifies the final head.

Hosted checks for the exact final head pass: CodeQL, Analyze (actions), and Lint code base. Copilot review 5769461963 approves that head at 2026-11-04T13:52:17Z with no inline comments. Implementation and verification are complete. Parent current-head content review accepts 21cc8b3c5f6f5bce6fe245ffd181fea5d0c496c4. Both skill diffs stay within the exact framing handback, and the selected-revision/requested-upgrade conditions preserve templates, paths, optional/required distinctions, scope, and procedure. No further source change is requested. The PR stays draft and this issue stays open until the owning process accepts and merges it. Only this leaf has a closing reference.

Fixed MSX sources, official STE overview/FAQ, and relevant Issue 9 rules/dictionary inform only the released wording. The manual stays local; its PDF checksum matches the official record. No full or certified STE conformance is claimed. No merge, ready transition, auto-merge, Agent merge, release-label, or lifecycle setting changes.

Implementation plan

• Verify both source blobs and record the integration coordinator's exact bounded handback; replace the blanket ownership hold with the released scope.
• Read both skills and applicable sources; record original/expected framing and protected-content checks before editing.
• Establish existing Markdown/link/front-matter and exact snippet/token/heading baselines.
• Change only the released framing in small commits and open a draft PR early.
• Recheck source/ownership before each commit; stop only for changed meaning, not incidental line movement.
• Verify all conditions, exact snippets, links and existing checks; record acceptance evidence and leave the PR in draft.

Do not wake/amend held proposal branches, import proposal-only content, perform an upgrade, merge, or change lifecycle settings. The existing proposal owners retain all template/caller decisions outside the framing grant.