skill-authoring §3 + operational-rigor §2: contributing is not adopting; re-resolve citations on install; stage by pathspec

[firaen22]

Summary

Three clauses from one downstream consumer's adoption pass over this repo — reading rules in, not writing them.

• skill-authoring §3, on the merged-integration bullet: that bullet tracks the campaign continuing upstream. This is the mirror case — an author's own adoption. A merge closes the contribution while the author's always-loaded files still lack the rule, and nothing feels missing because the author has been applying it from working context the whole session. Binds the adoption debt to the same ledger row that logs the merge, since a debt parked only in a plan or summary is the invalidation-clause failure this file already warns about, wearing a different hat.
• skill-authoring §3, new rule ahead of the packaging trio: a distributable skill's section-number and named-anchor citations address ITS library. Installed into a library that numbers differently, or never adopted the sibling, each citation still reads as valid and now resolves to the wrong content — a dangling §3 resolving to a real section is more dangerous than a 404. Re-resolve every citation against the destination by grep, classify retargeted / unchanged / absent-here, and record retargets in the port note as upstream-citation → local-target pairs — unrecorded, the next diff-against-upstream reads your own retargets as drift and a re-sync silently restores the broken numbers.
• operational-rigor §2, one clause on the baseline bullet: the mutation-side half of a baseline the rule already required. With pre-existing changes present that you did not author, stage by explicit pathspec (git add <path>), never -A/-u/. — on a tree that's entirely yours, -A is fine; the baseline read is what tells you which case you're in.

All three ship unprobed per the covenant; Provenance entries added to both files.

Note

Applying the new citation-resolution rule to this draft's own Provenance entries caught two mis-numbered section references before commit (both said §4/§3 where the rules actually landed in §3/§2) — fixed. Not a probe, just the rule firing on its own author.

Test plan

• git diff --word-diff against branch point — zero words removed, additions only
• Line-width sweep on added lines — none over 80
• Non-ASCII sweep — only expected house glyphs (§, —, ❌)
• All new/existing citations in the touched files re-resolved against actual section numbers

🤖 Generated with Claude Code