/flow creates and refreshes the tracker for every feature

Parent

/flow creates and refreshes the tracker for every feature that reaches implementation, so each flow has its graph without anyone asking.

When /flow reports a feature in implementation or finishing and the spec has no tracker, it runs init, then render, and adds a Tracker: line with the page link (or path) to its report.
When a tracker exists, /flow runs sync and marks each ticket the flow state records as landed merged before rendering.
refresh --spec <ref> runs init when no state exists, otherwise sync plus the landed tickets as merged, then render, and prints the page path; /flow calls it. Tests drive refresh through the command interface with a fake tracker and assert the state and page it leaves.
/flow never reads the build tracker's state file to rebuild flow state; flow state and the issue tracker stay its only sources.
/flow finish renders the tracker one last time once the gate passes.
/flow no-critique builds get the tracker too.
The /flow skill text documents the Tracker: line and is covered by its existing validators.