docs(ci): exercise prose-only CI partition

[seonghobae]

Stacked prose-only acceptance fixture for #279/#282. Keep Draft.

Current GitHub base is predecessor fix/docs-only-ci-partition@b54a5856d8201911f05d69622f0d5594a371adf0 and current child head is c904300a6a1bda83af24f84d586f1c5f6a6491aa. The effective child delta remains exactly one prose file, docs/doctoring/ci-docs-only-partition-canary.md (+7/-0), with no child .github/**, Rust, test, script, dependency, browser/policy, ruleset, secret, release, or contributor-instruction delta.

Parent #282 has since advanced to b64e0708584beff3fb54acf226cb3e667773e473, so this child is stale-parent evidence and must not be used as current acceptance. More importantly, the new #282 generation itself now conflicts with protected #286 by removing converted_to_draft/closed lifecycle events and the closed-event job guard. The authorized #279 owner must first reconstruct the parent on the protected classifier generation while preserving those lifecycle controls.

Only after that corrected parent is exact-head verified should this one-file canary be non-destructively restacked. Acceptance remains: the exact prose-only head executes Classify CI scope and Repository and documentation contracts, classifies the ordinary Markdown delta as documentation-only, and does not materialize Rust build/test/rustdoc/Clippy or Production coverage jobs. Cancelled/skipped heavy jobs are not equivalent to absence, and queued/runner-less/predecessor results are not GREEN.

Do not Close or discard this canary. Do not copy parent workflow source into the child, force-push, destructively rebase, self-approve, bypass, weaken gates, tag, release, or publish.

[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.}

[seonghobae]

Current exact-head canary recheck: parent→child compare remains exactly one added docs file, yet CI run 33800552815 materialized Rust contracts job 100798748081 and Production coverage job 100798748513. Both are still queued with steps=[], runner_id=0, and no runner group assignment. Their materialization on this one-file prose delta is fresh trigger-shape RED for #279; runner starvation is separate and is not treated as the cause. Keep Draft until the authorized workflow owner satisfies the status-aware #282 contract and an unchanged canary head proves exact-head documentation contracts execute without Rust-heavy jobs.

[seonghobae]

Fresh exact-head canary evidence: current parent→child semantic delta is still one docs file (+7/-0), but CI run 33813551801 materialized both Production coverage 100840591085 and Rust contracts 100840591337. Both are queued with no executed steps, so this is not a runtime verdict; however the heavy-job materialization itself reproduces #279의 trigger-shape RED on the new parent generation. Keep Draft until an authorized workflow owner connects #282's fail-closed classifier and the unchanged prose canary stops materializing Rust-heavy work while repository/documentation contracts still execute.

[seonghobae]

Exact-head canary remains RED at the trigger shape after non-force restack. Parent→child compare is still one prose file (+7/-0), but CI run 33816040229 materialized both Rust contracts job 100848292357 and Production coverage job 100848292745. Both are currently queued with no steps/runner, so this is not runtime evidence; job existence alone proves protected-main CI has not adopted #282's docs-only partition. The authorized owner must switch the scope producer to complete mode-aware git diff --raw -z evidence and keep exact-head repository/documentation contracts while gating only Rust-heavy jobs. No approval.

[seonghobae]

Fresh exact-head canary evidence after non-force restack onto #282 75d1432e8...: parent→child compare remains exactly one added prose file (+7/-0), merge base is the current parent, 0 behind. CI run 33820228681 nevertheless materialized Rust contracts job 100861121978 and Production coverage job 100861122055; both are queued with steps=[] and no runner. This remains trigger-shape RED, not runtime evidence. The new parent object-ID integrity hardening does not change the canary's one-file docs delta or authorize workflow mutation.

[seonghobae]

Current exact-head canary review after non-force restack: merge base is exactly parent #282 49f94d4c..., parent→child semantic delta remains one prose file (+7/-0), and the PR is mergeable/0 behind. CI 33824265448 nevertheless materialized Production coverage 100873441456 and Rust contracts 100873441577; both are queued with no runner. That job materialization is fresh trigger-shape RED for #279, independent of runner admission. Keep Draft; no predecessor status transfers.

[seonghobae]

Fresh exact-head canary after non-force restack onto #282 7c87bc30...: merge base is exactly the current parent, 0 behind, and parent→child semantic delta remains one added Markdown file (+7/-0). CI 33827986843 nevertheless materializes Production coverage 100884643624 and Rust contracts 100884643842; both are queued with steps=[] and no runner. That is current trigger-shape RED for #279. The parent now also rejects regular non-prose .js/.py/.rs/.json blobs under docs/** from lightweight authority, so this Markdown canary is still a valid positive fixture rather than a generic docs-directory bypass.

[seonghobae]

Non-force restack is coherent: exact base 5e88f9c5d008dcaf5d010ab6147605ef83036488 is the merge base, head 1a0114640845e4528e12e7e8eac3b1335b4c224e is 0 behind, and the semantic compare remains exactly one added Markdown canary (+7/-0). Fresh CI 33835200121 nevertheless materializes Production coverage 100906175087 and Rust contracts 100906175269 for the prose-only delta; both are queued with no runner/steps. Job existence remains the current trigger-shape RED for #279; it is not runtime GREEN.

[seonghobae]

Current-head canary verification after non-force restack: exact base is #282 b2bd01b90b176c340b44aeebb9a55383570fa323, exact head is 92f21a4c948ead9eee586e486e283ef2c018aebe, and the semantic parent→child delta remains one Markdown canary (+7/-0). CI 33839139750 nevertheless materializes Rust contracts 100917663147 and Production coverage 100917663489; both are queued with steps=[] and runner_id 0. That job existence is the #279 workflow-shape RED independent of runner admission. Keep Draft/stacked; no workflow weakening or source-only GREEN claim.

[seonghobae]

Current-head verification: the first non-force restack commit d88c1a29eef746403b113626a40ffbd5d662bc3b preserved ancestry but reused the old child tree, so relative to the moved #282 base it temporarily reverted parent changes. 73fd6261a2a0ea005dbaa6e7aa2a42a29c3611c9 repairs that finding by rebuilding from exact parent tree 2a6b6221016babee2573f0aee229af21f15f8d97 plus the unchanged canary blob. Fresh compare is 0 behind with exactly one added Markdown file (+7/-0). CI 33843159637 still materializes Rust contracts 100929401742 and Production coverage 100929401936, both runner-less queued; trigger-shape RED remains open.

[seonghobae]

Current-head verification: non-force two-parent restack adopts exact parent bd7046f1dbec5e26f49e68c624ebb911c4c8e674 and preserves the unchanged canary. Exact parent→child compare is 0 behind with only docs/doctoring/ci-docs-only-partition-canary.md (+7/-0). CI 33843743684 still materializes Production coverage 100931119974 and Rust contracts 100931120197, both queued with no steps/runner. The docs-only workflow-shape RED therefore persists after the Gemini-instruction authority repair.

[seonghobae]

Exact-head canary re-check after non-force restack: base is now #282 b947dcdd0a652217425e255f27ed2b42baeba293, head is 5ca7285ca9532b3441fbd2acf61aae4baa35b79a, mergeable, and parent→child compare is still exactly one added Markdown canary (+7/-0) with merge base equal to the parent and 0 behind. Fresh CI 33844845002 nevertheless materializes Production coverage 100934388748 and Rust contracts 100934388895; both are queued with no runner and no steps. Job existence remains the trigger-shape RED for #279, separate from runner admission.

[seonghobae]

Current-head canary verification after non-force restack onto #282 06d04b786fc470f821cf2e91c6546cb53d488783. Exact parent→child compare is still one added Markdown canary (+7/-0), merge base is the exact parent, and 0 commits are behind. Fresh CI 33847182872 nevertheless materializes queued Rust contracts 100941549519 and Production coverage 100941549710 with no runner/steps. That preserves the trigger-shape RED: the workflow owner has not yet wired the trusted docs-only partition. Keep Draft; this is not GREEN.

[seonghobae]

Restacked the canary onto exact parent 5fd4b3d3831a86d5f862dea3bb2eb59963b47727 at head 9ab10a75. The PR delta remains one non-executable documentation file. Local raw-object classification returned documentation_only=true and rust_required=false; the full 206-test contract suite and git diff --check passed. The new exact-head Actions run must now prove that scope/contracts execute while Rust and coverage are skipped by the governed partition.

[seonghobae]

Exact-head canary finding: the child effective diff is still exactly one Markdown file (+7/-0), but its parent #282 currently carries .github/workflows/ci.yml. Therefore this canary can validate job topology only after the authorized #279 workflow-owner boundary is repaired; it cannot legitimize the parent workflow delta by inheritance. Current head has CI 33917263830 queued, so no GREEN or heavy-job-absence acceptance is claimed yet.

[seonghobae]

Restacked on parent PR #282 exact head b54a585. Exact child head c904300 remains a single documentation canary file relative to its parent. Local evidence: actionlint passed; 206 Python repository contracts passed; the trusted classifier reports documentation_only=true and rust_required=false; diff hygiene passed. This PR remains draft, so CI jobs are expected to skip under #286.