feat(framework): read action files before running, across all skills

[blafourcade]

What

Every router skill now tells the host to read an action's file before running it, and the brainstorm finalize step is reordered so it persists before pointing to the next move.

Why

On hosts that don't follow the SKILL.md router into the actions/ files (codex, copilot), skills were improvising steps from SKILL.md alone. The clearest symptom: brainstorm finalize never offered to persist (file/ticket/session) because that detail lives only in actions/04-finalize.md, which those hosts never opened. Two fixes:

1. Read the action file — a uniform routing line added to all 38 router skills' SKILL.md and the skill-generate template:

   Before running an action, read its file in actions/, not only the table or assets.

2. Persist before next move — brainstorm finalize reordered so the persist offer runs before the next-move pointer, making the truncatable closing beat the guidance, never the durable artifact.

Testing (headless, codex + Claude)

• Codex: rebuilt + installed the native tree, drove each skill with a realistic intent. ~32/38 skills now open their action file(s), including every multi-action flow (bootstrap, plan, user-stories, pull-request, sdlc, audit 7/7, review 3/3, generate family). Validated flow, step-entry, fallback, menu-all, and menu-subset paths.
• Claude: plan and brainstorm read their action files and their assets (plan-template, phase-template) — the not only the table or assets wording does not make Claude skip assets. No regression.

Known limits (out of scope here)

• ~6 single-shot / interactive skills (commit, spec, fact-check, skill-generate, challenge, brainstorm) still improvise on trivial one-shot tasks on codex: the host answers directly without framing it as "running action X", so the trigger doesn't arm. A stronger wording fixed some but broke precise subset control, so it was reverted. The important multi-action flows all follow.
• aidd-orchestrator/00-async-dev uses nested actions/setup/ + actions/run/ dirs; the generic line was not applied there.

Future skills

The line is baked into skill-generate's template, so newly generated skills carry it automatically.