live: heartbeat sync 2026-10-19T11:18:41-07:00 (Refs #11)

agent/managed-skills/vault-one-fact-one-owner-dedupe/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vault-one-fact-one-owner-dedupe
-description: "\"Collapse per-payload/per-attempt vault pages into one owner page per endpoint without losing a fact: port-before-cut orphan census, doubled-page repair, trash-aware tools, delegated-write verification, index regeneration, and the merge-resolution order.\""
+description: "\"Collapse per-payload/per-attempt vault pages into one owner page per endpoint without losing a fact: port-before-cut orphan census (corpus must exclude the file under test), doubled-page repair, trash-aware tools, delegated-write verification, honest per-area line accounting, index regeneration, and the merge-resolution order.\""
 ---
 
 # One fact, one owner: dedupe the vault without losing a fact
@@ -37,12 +37,19 @@ file being rewritten. Any line with **no** surviving key is an orphan → port,
 deliberately and say so. Use `scripts/port-census.py <new-dir> <git-HEAD:path|file>` (numbers
 with ≥ 4 int digits, decimals, flags, paths, backticked spans, `--`, ALL-CAPS, or ≥ 2 hyphens).
 
-Two calibration traps:
+Three calibration traps:
 - **Prose words are not facts.** A hyphen or trailing period inside a word (`long-standing`,
   `deployed:`) was counted as a tracked token while real identifiers hid behind it; that noise
   buried 300 real lines under 979 fake ones. Strip punctuation, require fact shape.
 - **The corpus decides the question.** Corpus = the new file only → "what did this rewrite
   drop?" Corpus = whole vault → "is the dropped fact orphaned repo-wide?" Ask one at a time.
+- **The corpus MUST exclude the file under test, and you must assert it.** A census pointed at
+  the directory that *contains* the page proves the page is held by itself: ten era pages
+  reported `0 sole-record lines`, which reads as "pure duplication, trash it". With the file
+  excluded, the same pages held **14–63 sole-record lines each** — campaign ledgers that exist
+  nowhere else. A tool's own docstring promise ("excluding it") is not a check: print the
+  corpus size, assert the target is absent, and treat `0 unheld` on a long page as a tool bug
+  until proven otherwise. A mechanical census is a scout: its verdict is a lead, not a finding.
 
 Also grep `AGENTS.md` separately — a fact it carries is not an orphan.
 
@@ -52,7 +59,7 @@ Signature: a page whose `wc -l` is ~2× its `HEAD` size, with a **second frontma
 the body** whose closing `---` is glued onto the end of a body/timestamp line. Cause chain: a
 frontmatter rewrite that re-reads the file it just wrote (so its own output becomes the body),
 then a fence-repair pass keyed on `line == "---"` that cannot see a glued fence and inserts a
-fence mid-page, so the next pass treats the tail as a new document.
+fence mid-page, so the next page-tail becomes a new document.
 
 Un-double rule that worked: find the first frontmatter's close (accepting a glued fence), then
 the first `type:` line after it that has more keys (`title|description|tags|timestamp`) behind
@@ -82,9 +89,10 @@ grep -rnoE "\((page-a|page-b|...)\.md\)"  --include="*.md" serverAppConfigs-docs
 
 Both wikilinks and markdown path refs must be repointed (Research `See Also` lists and bench
 pages are where path refs hide). Then **regenerate** index rows with a script, never by hand.
-The generator bug to check for: presence tested as a **bare stem substring** — a page whose
-name prefixes another's (`frank-medium` inside `frank-medium-rocmfpx`) then silently never
-gets a row. Test the wikilink form `[[<stem>]]`.
+Generator bugs to check for: presence tested as a **bare stem substring** — a page whose name
+prefixes another's (`frank-medium` inside `frank-medium-rocmfpx`) then silently never gets a
+row (test the wikilink form `[[<stem>]]`); and **no dead-row sweep**, so deleting a page leaves
+an index row that fails the link check — the generator must drop rows for absent pages too.
 
 ## 7. Enforce the law with a seam
 
@@ -96,6 +104,12 @@ re-created era page then cannot pass tests. For the length hint, prefer **derive
 owned by the page that measured it) plus one documented per-page opt-out; never let a size
 ceiling force a ledger to be split across two owners.
 
+Splitting an over-long page to satisfy a ceiling is usually line-NEGATIVE: one measured split
+turned a 700-line page into 488 + 306 across five files (+23 for the folder net of stub
+deletions), because frontmatter blocks, pointer sections and connective prose are charged per
+file while the facts move for free. Roll the split back, carry `okf-exempt: length` with the
+reason, and keep the stub pages deleted.
+
 ## 8. Edit-tool hazard (costs the most time)
 
 Body rows beginning with `-` or `+` are op markers. The documented `+-` escape **writes a
@@ -104,6 +118,10 @@ line untouched and PUT only the indented continuation lines, or convert the note
 bullet whose body lines start with two/four spaces. If a wrapped `[[Two Word Page]]` shows up
 as an unresolved link, the target was hard-wrapped across lines — unwrap it.
 
+A `PUT` that spans a multi-line statement can silently drop neighbouring assignments
+(auto-repaired boundary echo); after editing a constants block, `grep -n "^[A-Z_]* = "` and
+run a syntax probe before executing.
+
 ## 9. Delegated writes: verify bytes, never narrative
 
 Measured in one campaign, all four failure modes live:
@@ -146,7 +164,24 @@ matter how concrete they read; and re-read the source bullet before trusting a t
 - Open the PR through the API with a 600-perm curl config (managed skill
   `gitea-api-pr-operations`), end the body with the `cwd:` / `session:` footer, then
   `xdg-open <PR-URL>` the instant it exists. Never merge without Frank's current explicit OK.
+  Push with an explicit refspec (`HEAD:refs/heads/<pr-branch>`) — a worktree's own branch name
+  is not the PR branch, and `git push origin HEAD` opens a stray branch.
 - Docs-only change ⇒ **no deploy**. Fast-forward the deploy checkout only
   (`git -C ~/Projects/serverAppConfig merge --ff-only origin/main`).
 - Say what was NOT done, in the PR body: soft lint tallies left (missing `## Citations`),
   conflicts left standing, repo config that was never installed on a host.
+
+## 12. Report line counts per area, never one net
+
+"Compaction" measured against the merge-base **per area**: docs / `scripts/` / `AGENTS.md`.
+A single headline number hides that tooling and prose move in opposite directions — one
+campaign reported "−1,849 vault lines" while the vault was flat and the growth was the two
+enforcement scripts that made the law mechanical. Expect a mature one-owner vault to land
+**docs flat**: the reductions available are deletions of *restatement* (duplicated pages,
+transient deploy chatter in `log.md`, `AGENTS.md` bullets whose numbers an endpoint page owns)
+and they are roughly cancelled by the cost of the citations the verification pass adds. When
+asked to shrink further, show the menu — drop the tools, drop the citations, or accept content
+loss — instead of inventing cuts. `log.md` compaction rule that survived census: drop a line
+only when it matches a transient shape (`/health`, `deployed`, `restart`, `systemctl start`)
+**and** every fact token in it is held by an owner page; a token-held line can still be the
+only record of *when* an incident happened.