Per-lane effort config, configure-models skill, worktree/review/token-efficiency policies (0.9.0) #3

Merged
ksamaschke merged 1 commit from feat/effort-config-review-economics into main 2026-08-13 05:45:28 +00:00
Owner

Adds the [effort=...] lane contract with generated engine enumeration, role-pin validation, scope-correct sync --global digests, and effective-effort footnotes (67 smoke assertions bash+dash, 25 renderer tests); a new configure-models questionnaire wrapping configure-codex-roles; and the full policy set: atomic per-lane worktrees, done-means-merged-and-deployed with deploy-lane close-after-verify, vertical slices, cheapest-tier + lowest-effort routing with frontier guard, explicit dispatch models, progress lines, detached supervision with liveness-based stall detection, mandatory tmux dispatch with session cleanup, facet-panel review economics (implement-issues, pr-and-merge, commit-and-push), and a self-maintaining rule-9 freshness marker list. Verified by requirements-check and cross-family PI adversarial review; all findings adjudicated and fixed.

Adds the [effort=...] lane contract with generated engine enumeration, role-pin validation, scope-correct sync --global digests, and effective-effort footnotes (67 smoke assertions bash+dash, 25 renderer tests); a new configure-models questionnaire wrapping configure-codex-roles; and the full policy set: atomic per-lane worktrees, done-means-merged-and-deployed with deploy-lane close-after-verify, vertical slices, cheapest-tier + lowest-effort routing with frontier guard, explicit dispatch models, progress lines, detached supervision with liveness-based stall detection, mandatory tmux dispatch with session cleanup, facet-panel review economics (implement-issues, pr-and-merge, commit-and-push), and a self-maintaining rule-9 freshness marker list. Verified by requirements-check and cross-family PI adversarial review; all findings adjudicated and fixed.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ksamaschke/implementation-skills-codex!3
No description provided.