fix: continue repository-bound flow candidates

[bigboateng]

Summary

• Bind repository-owned inputs after the supervisor selects one parameterized Flow transition.
• Revalidate delegation and resolve again before the existing apply boundary.
• Keep questions, ambiguous candidates, explicit transitions, and existing prescriptions suspended.

Verification

• python3 .github/scripts/run_go_tests.py
• npm ci && npm run build:flow-sdk
• go vet ./... && go build ./...
• python3 -m unittest discover -s .github/tests -p 'test_*.py' -v
• python3 .github/scripts/release_notes.py validate --repo .
• python3 .github/scripts/release_notes.py check-policy --repo . --base origin/main --head HEAD
• Disposable Todo-Test Flow: objective.bind committed, then continuation reached the expected engagement.begin repository-authority boundary.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[github-actions]

Codex automated review

Verdict: patch is correct
Confidence: 0.9

No actionable defect was established. The retry binds only a unique kernel-selected candidate, re-runs delegation and resolution with the bound parameters, and applies only the fresh second prescription. Ambiguous, explicit, human-input-only, stale, or unauthorized paths remain effect-free. Model-level verification is not recommended before merge.