[dudupii]

Post-v0.5.0 documentation sync. The release shipped the state projection across two PRs (#19, #20, #22), but the docs only reflected the first two — this catches them up. No skill, eval, or manifest changes; all three manifests already read 0.5.0 and the README pi pins already point at v0.5.0 (#21).

README.md + README.zh-Hans.md

• Closing receipt (evals: fix suite wedges (case.yaml, ReDoS trace graders); handover receipt contract #22) had no mention anywhere: handover's closing reply doubles as a receipt — note path, the metadata chain it wrote (deferring to the note's own frontmatter rules), and the CURRENT.md outcome one line per change, with a bootstrap leading on the entry count and listing every added entry. New bullet in both languages.
• The Current-state file bullet described the shape but not the change contract: add newly durable facts, supersede in place (entry states the new fact only; the old value lives in git and the source note), delete refuted ones, never rewrite untouched entries — and the bootstrap walks the history oldest-first so facts buried by age are not crowded out. Expanded in both languages.
• The handover row in both arrows tables now surfaces CURRENT.md at first glance — it's the release headline and was invisible in the table.

docs/release-smoke.md

Item 2 gains the operational facts the v0.5.0 release train paid to learn:

• suite size and cost (currently 27 cases, ~1 h serial);
• wrap invocations in timeout -k 15 720 — a wedged grade pass spins at full CPU and ignores SIGTERM;
• every case dir needs case.yaml + a seed script (a dir without one hangs the loader);
• trace-target lookahead chains must start with ^ — unanchored, they go quadratic over multi-MB traces.

Both wedge classes are fixed in-tree (#22); the signatures stay in the checklist so the next release runner recognizes a recurrence.

[pullfrog]

✅ No new issues found.

Reviewed changes

• README.md + README.zh-Hans.md — handover arrows-table row now surfaces CURRENT.md; the Current-state-file bullet gains the update contract (add / supersede-in-place / delete refuted / never edit untouched) and bootstrap ordering; a new Closing-receipt bullet documents the receipt contract. Both languages mirror section-for-section.
• docs/release-smoke.md — item 2 now records suite size (27 cases, ~1 h serial), the timeout -k 15 720 wrap, the case.yaml + seed-script requirement, and the ^-anchored trace-target lookahead rule.

Verified against the source of truth: the README phrasing matches skills/handover/SKILL.md (update contract, bootstrap oldest-first, closing receipt), evals/ holds exactly 27 case dirs each with case.yaml and scripts/seed.sh, and all three trace-target lookahead chains (handover-focus-only, handover-focus-lang, relay-ignites/command-trace) start with ^. Docs-only, no behavioral surface.

---

Important

Pullfrog covered this run's model usage. DeepSeek Flash is fast and cheap — expect lighter work than a frontier model. This model allowance is temporary and separate from your Pullfrog plan. Connect a model-provider subscription or API key →

  ^{｜ View workflow run ｜ Using DeepSeek Flash (model usage covered by Pullfrog) ｜ 𝕏}