Make the verified capture path the one the commits skill teaches

[MongLong0214]

Closes #340

skills/commitlore-commits/SKILL.md taught hand-written trailers first and
reached the capture pipeline only as an aside, so the product's own agent
workflow defaulted to the one path with no verification behind it.

Before

1. What a record is
2. When to record
3. The vocabulary (two tables)
4. The harvest pipeline — harvest --prompt-only, a worked draft JSON, a
   worked verified/rejected pair, --repair-prompt, then "fold the trailers in
   by hand and commit"

Trailer syntax was the thing the reader was being taught to produce. capture,
the transaction that binds a record to a nonce, anchors expires_at at stage
time and refuses fabricated evidence, appeared nowhere.

After

1. What a record is, and that capture is how it gets recorded
2. When to record
3. Capture — the five steps an agent executes: prepare → draft → verify →
   stage → commit, with the MCP tool names and argument shapes
   (commitlore_prepare_capture, commitlore_verify_capture,
   commitlore_stage_capture) alongside the CLI (commitlore capture --transcript … --draft …), the rejection reasons verify returns, and the
   five gates prepare-commit-msg applies at commit time plus the five-minute
   window that opens at stage — the part no prompt contract carries
4. The vocabulary (one table)
5. Fallback: writing the block by hand — stated to apply when capture cannot
   bind: a commit that already exists, or a repository without the hooks, with
   backfill named for past commits and harvest/harvest-verify for evidence
   checking without the transaction

Net 151 lines against 162. The harvest walkthrough and the drafted-JSON example
came out because prepare's prompt prints both at the moment they are needed;
the vocabulary table stayed because the fallback writes from it.

Verified

• prepare → verify → stage round-tripped against the real stdio MCP server
  in a scratch repo, and separately through commitlore capture --transcript --draft; both reached a git commit whose trailer block the
  prepare-commit-msg hook appended on its own.
• A fabricated quote was refused (evidence-not-found) with nothing staged, at
  exit 0.
• Every command and tool name in the file was executed before being written down.
• npx vitest run test/manifest.test.ts test/doctor.test.ts test/agent-configs.test.ts — 99 passed. (test/skills.test.ts does not exist;
  those are the files matching skill/plugin/manifest, and no test asserted the
  old harvest-first content.)

Known gap, not closed here

The transcript is composed by the same agent that writes the draft, so
"refuses fabricated evidence" means "refuses quotes absent from what the agent
submitted as the transcript". The skill now says to write it in the words
actually exchanged rather than a summary, but nothing mechanical enforces
transcript fidelity.

[github-actions]

CommitLore — record lint

Trailers: clean — 1 commit in origin/dev..6947cf9612ad252479191bbf6d7720411fd1c3ba
Active constraints: 2 limits · 4 ruled-out · 1 warnings — from 2 records over 1 changed path

Active constraints for the paths this PR touches

Limits (2)

• r-captureskill 6947cf9 — a skill loads into every agent's context, so a paragraph duplicating what the runtime prompt already prints is paid for on every session
• r-9f3b16 6b13589 — git decides rename lineage by content similarity, so any claim about following renames is a claim about a threshold, not a guarantee

Ruled out (4)

• r-captureskill 6947cf9 — Documenting both paths as equals | an agent takes the first workable path it reads, and the manual one produces a record no checker has seen
• r-captureskill 6947cf9 — Dropping the vocabulary table along with the harvest walkthrough | it is what the fallback writes from and what a reader parses existing records with, and neither of those has a prompt contract to lean on
• r-9f3b16 6b13589 — assert only that renames are followed | it would pass with the threshold anywhere, which is the same as not testing it
• r-9f3b16 6b13589 — paper over delete-then-recreate | git links nothing there, and pretending otherwise would invent a lineage

Warnings (1)

• r-9f3b16 6b13589 (claim) — the 43/44 percent crossover is a property of git's -M default and this fixture generator, not a protocol guarantee -- if it moves, decide whether the new value is acceptable rather than editing the number to match

_{Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR.}