v0.4.2 — flow authoring loop fixed + second dogfood flow page

The flow authoring loop, fixed end-to-end

templates/flow.md, references/flow.md, and the vendored AGENTS.md all promise that wiki-stamp.mjs writes every inline flow *_sha — but the shipped script only stamped covers:. So a freshly authored flow page failed wiki-flow-check on every WRITTEN-BY-wiki-stamp placeholder (anchor_sha / call_anchor_sha / cite_sha). Caught by two independent dogfood runs (repolore-on-repolore and repolore-on-pipao), each forced to hand-fill the SHAs.

Fix: wiki-stamp.mjs gained a stampFlowShas pass that fills each *_sha from its sibling *_path in the same list item, reset at every - boundary so a SHA can never adopt a neighbouring step's path. New tests/wiki-stamp.test.mjs pins own-sibling correctness (no cross-bleed), idempotency, and the orphan-sha case.

Second dogfood flow page

flows/update-classification — how update classifies every tracked file from its (recorded, current, master) SHA triplet into one safe action (never overwriting a local edit by default). 9 steps, 1 verified directional edge + 6 cited branches, tier branch-audited. Proves flow-meta generalises past the near-linear bootstrap flow to a branchy decision tree.

---

To pick it up in an existing repo: refresh the plugin/skill channel, then run the update workflow (repolore:update) — the vendored wiki-stamp.mjs is pristine-but-outdated, so it regenerates cleanly.