Skip to content

Releases

Keystone 0.9.40

Choose a tag to compare

@sattva2020 sattva2020 released this 21 Nov 15:43

Changed

  • One sweep beside the judge on L. The first /keystone:verify run of an L plan whose checks are green runs review
    (an Opus finder plus the review validator) and /keystone:security once, in the same message as the verifier; all
    findings land in one verify.md (## Sweep) and one /keystone:fix verify pass. Only critical review items block;
    suggestions are Advisory. The sweep repeats only on --full or for tasks added after it; a failed build, test or
    agent leaves it due for the next run. The judge and the sweep never see each other's output.
  • No second review after the sweep. A plan that had its sweep gets no Review the diff / Security check options,
    no /keystone:review in Next: and no built-in /code-review; running them by hand still works.
  • Late non-critical findings go to Advisory. The judge adds Impact: critical | non-critical to every wrong and
    missing line. After the first PASS / PASS-UNPROVEN a late non-critical one is Late: <id> (advisory), outside the
    verdict; the chat shows only Late advisory: <k>.
  • BLOCKED waits for you without a judge. A BLOCKED row whose evidence cell, task tail and files are unchanged is
    carried (carried: … — BLOCKED — waiting for you …); with nothing else to judge the verifier is not called.
  • A ceiling of three judged FAILs. From the third judged FAIL run (failed builds and accept commits do not count)
    the verifier is not called until every open finding is decided — accept, debt or back to the plan
    (Accepted finding by …, ## Debt … deferred). A plan edit or --full lifts it for one run. It replaces the trend menu.
  • --full brings back the old behaviour for one run: full judge, sweep due, late rule off, no ceiling, no carried
    BLOCKED.
  • Sweep findings stay in their run. A critical review item and a Security gate: fail of the sweep belong to the
    verify.md whose ## Sweep has them; /keystone:fix verify takes them from there, and a later run does not carry
    them. A sweep that failed on unchanged code runs again on --full. The nothing to judge stop prints
    open findings: (findings of the last judged run that are not rows, failed gates — its ## Sweep included); when
    there are any, Next: is /keystone:fix verify, not accept.
  • Parked rows. A late row routed to Late: … (advisory) and a row accepted at the ceiling are carried without the
    judge (carried: … — advisory | accepted) until their files, their plan text or a cited row change. An accepted row
    id covers only the runs up to its accept: judged again, it is a finding again.

Keystone 0.9.39

Choose a tag to compare

@sattva2020 sattva2020 released this 20 Nov 07:51

Added

  • Feedback summary: coverage. /keystone:feedback now has a Coverage section: per chain skill, in how many sessions that started with feedback on the skill ran, and in how many of those its self-report was written — a skipped report no longer looks like "the skill did not run". Read from the transcripts on this machine (<config>/projects), nothing is stored. The instruction of the SessionStart hook carries a plugin: <version> line, so --since X.Y.Z counts only the sessions of that version and later; sessions of 0.9.37 and 0.9.38 have no such line and drop out under any --since.

Keystone 0.9.38

Choose a tag to compare

@sattva2020 sattva2020 released this 19 Nov 07:13

Fixed

  • The band no longer disappears mid-task (mod). A session's binding to its plan is also kept in the mod's store by session id, so an app restart or update no longer leaves the session without status, buttons and cost. The band (plan and context bars, the next-command button) now stays after every turn while the session has a plan — also after a plain prompt or an answer to the agent's question. A session that starts in a repo with a plan in view it has not worked with gets one dim row naming that plan, with its next command as a button; the row leaves with the first prompt.

v0.9.37

Choose a tag to compare

@sattva2020 sattva2020 released this 17 Nov 10:19

Added

  • Agent feedback (off by default). The plugin option feedback (or KEYSTONE_FEEDBACK=on; KEYSTONE_FEEDBACK=off
    switches it off for good, the benchmarks set it) makes a SessionStart hook put a short instruction into the context.
    The chain skills — start, intent, plan, check, implement, verify, fix, review — then end with a self-report of at most
    10 lines about the skill text (unclear / deviated / guessed / extra, each skill § section), in the language of the
    conversation; the chat gets one line. Records are appended to ~/.claude/keystone-feedback/<project>/feedback.jsonl
    (all worktrees of a repo share one folder; KEYSTONE_FEEDBACK_DIR moves it) — only on this machine, never sent
    anywhere, by rule no project code, file contents or secrets (known secret patterns are masked — best effort), no automatic cleanup.
  • /keystone:feedback. summary [--since X.Y.Z] folds the records of all projects into repeated problems with a
    count; judge <plan path> / judge runs the new read-only keystone:feedback-judge agent on the signals of the work
    (tool errors, repeats, interrupts, verify rounds, user corrections — counted by feedback.mjs, no model): it confirms
    or doubts each claim of the reports and adds what was left unsaid, with cause and class; auto <plan path> is called by
    verify on M/L — once per task, only when the signals call for it. Feedback never blocks work, is not a gate and does
    not touch the verdict.

Keystone 0.9.36

Choose a tag to compare

@sattva2020 sattva2020 released this 15 Nov 13:49

Fixed

  • The push gate says what it closes. Its deny text read "push/PR is closed" for every case, while in a cloud
    session a push of the work branch passes — agents in two live cloud runs reported the message as wrong. It now
    names the case: "this push carries commits of <task folder> and is closed while …" or "a PR carrying commits of
    <task folder> is closed while …" (gh pr create and the GitHub MCP tools alike), and in a cloud session adds that a
    push of the work branch itself stays open.

Keystone 0.9.35

Choose a tag to compare

@sattva2020 sattva2020 released this 15 Nov 13:38

Fixed

  • Push gate covers the GitHub MCP tools. The gate watched only Bash and PowerShell, so in a cloud session a PR made
    through the GitHub MCP tools skipped it while the plan was a draft (found live, 0.9.33). A second PreToolUse group
    now sends create_pull_request, merge_pull_request, push_files, create_or_update_file and delete_file from any
    MCP server to the gate: a PR or a merge is judged like gh pr create (its head against its base), a write straight to
    the default branch is closed while a plan is active, a write to another branch and every read tool pass. The first
    group's matcher stays a list of exact names, so TodoWrite and other tools do not wake the gate.

v0.9.34

Choose a tag to compare

@sattva2020 sattva2020 released this 15 Nov 13:36

Added

  • One session per plan. /keystone:implement and /keystone:fix take the plan before their first edit, so a
    second session (another worktree, another machine, the cloud) cannot run the same plan at the same time. The owner
    record — place (worktree folder or cloud session), branch, stage, time; no machine name, no path — lives on the
    service branch keystone/owners and is pushed to origin by skills/implement/scripts/owner.mjs (plumbing only: the
    work tree, HEAD, main and the plan folder are untouched, the push gate is unchanged). A second session stops with
    who runs the plan and asks Стоп / Забрать план; without AskUserQuestion it stops, and --force is only a human's
    pick. The owner beats before each task and commit; no beat for 2 h = stale, and taking over becomes the recommended
    answer. A taken-over session stops at its next beat. The end of a run, verified and abandoned (verify, accept,
    start, fix) drop the record. Of two takes on one tip exactly one wins (push without force + one retry; on the local
    branch a CAS on the decision's snapshot). Offline or without origin the mark stays local with one warning.
    /keystone:sessions does not wake a child whose plan another live session runs. KEYSTONE_GATES=off turns it off.

Keystone 0.9.33

Choose a tag to compare

@sattva2020 sattva2020 released this 15 Nov 13:05

Fixed

  • Push gate: a pushed work branch no longer hides the plan's commits. The gate counted a push as carrying the plan
    only when it shipped commits not yet on any remote branch. In a cloud session, where the work branch may be pushed
    before verify (0.9.30), that made a later git push origin HEAD:main and gh pr create look empty, and both passed
    while the plan was still a draft — found live on a sandbox repository with 0.9.31. What a push ships is now measured
    against the branch it lands on (origin/<dst>; for a PR, the default branch); a new branch, --all or a repository
    without origin keep the old "not on any remote" rule. Commits already on the default branch count as landed, and
    merge commits are still skipped, so main merged into a work branch keeps its push open (0.9.32).

Keystone 0.9.32

Choose a tag to compare

@sattva2020 sattva2020 released this 15 Nov 12:39

Fixed

  • Push gate: a merge that only combines plan-folder commits already on a remote (main merged into a task branch) no
    longer closes git push; the gate counts non-merge commits not on any remote (git log --no-merges). A plan's own
    unpushed commit still closes it.
  • Verify: merging main into the task branch no longer forces delta: full. The base is found on the first-parent line
    (an older merged-in commit no longer moves it), merge since the last verify is gone, and files only a merge brought
    are not counted — delta: since <sha> — <k> files changed …; <m> more came in by merge (not counted). Rows whose
    evidence names such a file are still judged.
  • Verify: paths written to verify.md (the files: list, rules scope:, Architecture gate, accepted violations:
    and the Accepted violation by … line, changed files in the build / lint command and the check output, the
    verifier's file:line) are in backticks, so Prettier via lint-staged no longer turns __tests__ into **tests**;
    findings and accepted violations read the same with or without backticks. /keystone:setup proposes docs/keystone/** in
    .prettierignore when the project runs Prettier.
  • Verify: a check over the time limit says how to raise it — not run (timeout after 600 s — raise KEYSTONE_CHECK_TIMEOUT_MS).

Keystone 0.9.31

Choose a tag to compare

@sattva2020 sattva2020 released this 15 Nov 11:07

Fixed

  • The plugin passes claude.ai validation again. claude.ai now rejects a skill whose description holds
    <placeholder> text ("SKILL.md description cannot contain XML tags"), and one such skill blocks the whole plugin: the
    account marketplace kept serving 0.9.29 to cloud sessions, so 0.9.30's cloud push-gate fix never reached them. Nine
    descriptions (docs, evolve, fix, plan, qa, qa-check, reference, roadmap, security) now write placeholders as
    [placeholder]; a test keeps every skill and agent description free of <…>.