@r1z4x/tezgah 1.3.0 → 1.5.0

package/skills/plan-add/render_table.py

@@ -37,8 +37,9 @@ def acceptance(strict):
     count = lambda state: sum(1 for i in report["items"] if i["state"] == state)
     print("plans: %d read, acceptance items: %d read; %d name no command, %d declared unverifiable"
           % (report["plans"], len(report["items"]), count("missing"), count("unverifiable")))
-    open_missing = [i for i in report["items"]
-                    if i["state"] == "missing" and i["plan"].startswith(".tezgah/plans/open/")]
+    # the predicate the phase move refuses on (tezgah-task), so the two agree
+    open_missing = tt.unproven([i for i in report["items"]
+                                if i["plan"].startswith(".tezgah/plans/open/")])
     if strict and open_missing:
         print("strict: %d item(s) under .tezgah/plans/open name no command and declare no "
               "unverifiable; a done plan is reported, never gated" % len(open_missing))

package/skills/plan-status/SKILL.md

@@ -15,7 +15,12 @@ description: >
 1. Resolve the root: `ROOT=$(git rev-parse --show-toplevel)`. If it fails, stop and
    say plans need a git repo. If `$ROOT/.tezgah/plans/open` is missing, say so and stop.
 2. For each `.tezgah/plans/open/*.md`: read the frontmatter (id, title, status, branch, pr)
-   and the first line of the `## Next` section.
+   and the first line of the `## Next` section. Then run
+   `~/.config/tezgah/bin/tezgah-task status`: per open plan it prints the
+   Acceptance boxes ticked, the plans its `after:` still waits on, and a
+   `parallel:` line naming the ready plans that share no `allowed_paths:`
+   prefix; a `FAIL` line (a status outside open|blocked, an `after:` id no plan
+   carries, a phase no reader accepts) goes into the report as it printed.
 3. If `pr:` is set, run
    `gh pr view <pr> --json state,mergedAt,reviewDecision,statusCheckRollup -q '[.state, .reviewDecision, ([.statusCheckRollup[]?.conclusion] | unique | join(","))] | map(select(. != null and . != "")) | join(" | ")'`
    and append the result to that row's `pr` cell, e.g. `#12 (OPEN | APPROVED | SUCCESS)`.
@@ -37,16 +42,19 @@ description: >
    no "Generated with" / "Made with", no robot emoji, no Claude/Anthropic/OpenAI/
    GPT/Codex/Gemini/Cursor/Copilot credit.
 8. Print the table, then one line per plan with `status: blocked` quoting its
-   `BLOCKED: <reason>`, then any gh failures.
+   `BLOCKED: <reason>`, then one line per plan that waits on another (`waits on
+   NNN (open)`), then any gh failures and `FAIL` lines.
 9. End with exactly one recommendation: "Work on NNN <slug> next: <reason>". No menu.
    Prefer plans with an approved PR and green CI, then open plans with no blocker,
-   oldest first.
+   oldest first; never a plan that still waits on another. When the `parallel:`
+   line names it with others, add one sentence: those plans can run at once, one
+   worktree each.
 
 ## Format
 
 Plan file `.tezgah/plans/open/NNN-slug.md` (status open|blocked) or `.tezgah/plans/done/NNN-slug.md`
 (status done|discarded). Frontmatter: id, title, status, branch (`plan/NNN-slug`),
-pr, created, updated, allowed_paths, plus phase/allowed_from/review when set. Sections: `## Goal`, `## Acceptance` (checkboxes), `## State`
+pr, created, updated, allowed_paths, plus after/phase/allowed_from/checkpoint/review/review_round/reviewed_sha and the spike keys when set. Sections: `## Goal`, `## Acceptance` (checkboxes), `## State`
 (evidence), `## Next` (one action or `BLOCKED: <reason>`). README table lives between
 `<!-- status:start -->` and `<!-- status:end -->` with columns
 `| id | title | status | branch | pr | next |`.

package/skills/plan-sync/SKILL.md

@@ -28,16 +28,23 @@ description: >
    - gh returned `[]`: fallback `git branch -r --merged origin/main | grep -q "origin/<branch>"`.
      If it matches, treat as done and append `merged without PR`.
    - otherwise: leave the plan untouched.
-5. For every plan marked done: if `## Acceptance` still has `- [ ]` boxes, still move
-   it but append the line `acceptance boxes unchecked at sync` to `## State`.
+5. For every plan marked done: if `## Acceptance` still has `- [ ]` boxes (the
+   `acceptance N/M checked` count `~/.config/tezgah/bin/tezgah-task status` prints
+   per open plan), still move it but append the line
+   `acceptance boxes unchecked at sync (N/M checked)` to `## State`.
 6. Move each done or discarded plan with
    `~/.config/tezgah/bin/tezgah-task close NNN done|discarded`: it sets `status:` and
    `updated:` and moves the file to `.tezgah/plans/done/`. It refuses `done` unless the
-   plan records `review: <reviewer> approve` - a fresh reviewer (the host's
-   `tezgah-reviewer` subagent) read `git diff <base>..HEAD` and
-   `tezgah-task review NNN <reviewer> approve` wrote the verdict - and it refuses
-   the active task. A refused plan stays open: report it with the refusal, never
-   move it by hand.
+   plan records `review: <reviewer> approve` - fresh reviewers (the host's
+   `tezgah-reviewer` subagent, one per dimension in one message for a large diff)
+   read `git diff <base>..HEAD` and `tezgah-task review NNN <reviewer> approve`
+   wrote the verdict - and it refuses the active task. A refused plan stays open:
+   report it with the refusal, never move it by hand, and never start a review
+   round from here. One review per plan, over its whole diff in the verification
+   phase; at most two rounds - only a confirmed critical or major finding opens
+   round two, a minor or suggestion one is recorded fix-later, and after round two
+   what is left goes to the user or is recorded fix-later, never a third round.
+   A plan refused with a spent budget is the user's decision.
 7. Rewrite the README status table: `~/.config/tezgah/bin/tezgah-render-table` (installed by `bin/tezgah-setup --install`; if it is missing, run that script)
    (one row per open plan, sorted by id; it prints the rows). No `--pr-info` here:
    the row's `pr` cell comes from the plan files, and review/check enrichment
@@ -55,14 +62,17 @@ description: >
    no "Generated with" / "Made with", no robot emoji, no Claude/Anthropic/OpenAI/
    GPT/Codex/Gemini/Cursor/Copilot credit.
 9. Report four lists: moved plans (with done/discarded and the evidence line),
-   plans `close` refused (with its reason), still-open plans, and gh failures. Never delete branches, never edit code outside
+   plans `close` refused (with its reason), still-open plans - each with what
+   `tezgah-task status` says it waits on, so a plan whose `after:` names one just
+   discarded (`waits on NNN (discarded)`) is named for the user to re-plan - and
+   gh failures. Never delete branches, never edit code outside
    `.tezgah/plans/`.
 
 ## Format
 
 Plan file `.tezgah/plans/open/NNN-slug.md` (status open|blocked) or `.tezgah/plans/done/NNN-slug.md`
 (status done|discarded). Frontmatter: id, title, status, branch (`plan/NNN-slug`),
-pr, created, updated, allowed_paths, plus phase/allowed_from/review when set.
+pr, created, updated, allowed_paths, plus after/phase/allowed_from/checkpoint/review/review_round/reviewed_sha and the spike keys when set.
 Sections: `## Goal`, `## Acceptance` (checkboxes), `## State`
 (evidence), `## Next` (one action or `BLOCKED: <reason>`). README table lives between
 `<!-- status:start -->` and `<!-- status:end -->` with columns

package/skills/tezgah-contract/SKILL.md

@@ -221,9 +221,11 @@ a list, several files or areas, todo entries that share nothing - go to one
 subagent each, and every writing slice gets its own branch and checkout (see
 below), never the main checkout. The
 orchestrator is the main thread itself: it does not wait idle on a slice while
-independent work remains. Fan out only when the subtasks share no mutable file and no interface: if two of them would edit the same file, or one's answer decides the other's, keep them in one context or sequence them. The shared artifact is the coordination channel, not chatter - naming a lead coordinates nothing by itself. If the work
-cannot be split - one file, one bounded change, a strictly serial chain - do it
-directly. Never spawn a subagent whose briefing is bigger than the work.
+independent work remains. Fan out only when the subtasks share no mutable file and no interface: if two of them would edit the same file, or one's answer decides the other's, keep them in one context or sequence them. The shared artifact is the coordination channel, not chatter - naming a lead coordinates nothing by itself. Only a single item - one file, one
+bounded change, a strictly serial chain - is done directly; a list of
+independent items is never worked one by one on the main thread, however small
+each item is, and that holds at every phase: a plan's tasks, its acceptance
+commands and the sources of a survey fan out the same way.
 A slice that needs its own checkout: inside Orca (the session-start `Orca:`
 line) create it with `orca worktree create --name <slug> --parent-worktree
 active --json` and track it with `orca worktree ps --json` or `tezgah-status
@@ -272,7 +274,8 @@ guards against.
 
 ### The gate, for anything either tier produces
 Read the diff yourself. Then tests, lint and type check must pass, and anything
-non-trivial gets an independent review before it lands. A delegate's output is
+non-trivial gets an independent review before it lands - once per plan, not
+per task or commit. A delegate's output is
 a draft until the router has evidence; "the agent said it works" is not
 evidence.
 
@@ -519,12 +522,20 @@ rewrite it plainly.
 on a merge. Review first with a FRESH reviewer (never my own read of my own
 code), run the full suite, and if the review is clean and every test passes,
 merge, move the plan to `.tezgah/plans/done/`, and report the outcome. Bring it back
-to the user only on a critical or high-severity finding, or a failing test.
-
-**Review population: a change with an executable oracle.** The single FRESH
-reviewer above stays the rule for every change except one whose correctness can
+to the user only on a critical or major finding left after round two, or a
+failing test. One review per plan, over its whole diff in the verification
+phase; at most two rounds - only a confirmed critical or major finding opens
+round two, a minor or suggestion one is recorded fix-later, and after round two
+what is left goes to the user or is recorded fix-later, never a third round.
+A round spawns its reviewers in ONE message, one per dimension (correctness
+and contract, security, tests and performance) or file group; a diff under 300
+changed lines gets one reviewer. Per-task work gets tests, not a reviewer, and
+`tezgah-task review` refuses a third round.
+
+**Review population: a change with an executable oracle.** The fresh review
+above stays the rule for every change except one whose correctness can
 be executed - a checker, a gate rule, a parser - where each claim can be built as
-a fixture. There the fresh-review step becomes a population:
+a fixture. There round one becomes a population:
 1. One agent that has seen no known defect writes four failure directions from
    the code alone.
 2. Four reviewers, one direction each, run at once; every claim names an exact
@@ -534,9 +545,11 @@ a fixture. There the fresh-review step becomes a population:
    kind - a false accept and a false refusal alike. Only a confirmed claim counts.
 4. Confirmed claims are grouped by root mechanism, and each group gets a
    failing-first test.
-5. A population round reviews one revision and does not replace re-review of
-   the fix: every round that confirms a defect is followed by a round over that
-   fix's delta, until a round confirms none.
+5. The population is round one and spends the same two-round budget: a fix
+   for a confirmed critical or major claim carries its failing-first test, and
+   round two reads that fix's delta, the round-one hunks and the direct callers
+   of what it touches. After round two what is left goes to the user or is
+   recorded fix-later, never a third round.
 
 Status: a tentative default, measured on two changes. E1
 (an internal prove-verify experiment): directed reviewers found 3 of 3 ground-truth defects,