You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
plugin-packaging ships a README standard and checklist (references/readme.md): the sections in order, required and conditional, the facts a README takes from the repository, and checkable items for structure, badges, counts, hosts and install commands, descriptions, license, images, links and placeholders. readme_check.py checks the mechanical items offline and lists external links to open; it is advisory. A repository may adapt headings, aliases and a house style in .github/readme-standard.json. versioning and the plugin-packaging release checks now run the checklist before a release.
Changed
The README gains a short Privacy section linking PRIVACY.md, and the repository's own marketplace entry now carries the manifests' description.
Breaking: ## Agent roles in the host config is no longer read (owner decision, 13/11/2026). The assignment matrix is the only source of review roles (code review, security review, navigator, advisor) and the judge: a user with only ## Agent roles loses those roles and the Jev judge (reviews follow the capability order, the judge is the host model) until running /setup add delegation, which converts the section with matrix_setup.py migrate and asks consent again. /setup check reports that case as roles: missing, names an ## Agent roles left beside a matrix in legacy host settings, /setup add roles records roles and the judge in the matrix, and /update lists the step. The judge-call rule in CLAUDE.md and the judge section of PRIVACY.md now name only the matrix. ## Review posting and ## Agent levels are unchanged.
The README opens as a landing page: the icon, the tagline and subhead, badges for the release, licence and the three hosts, the banner, a "What you get" block, the install commands for each host and the request-to-merge diagram. "For engineers" (release notes, compaction steward, diagrams, Bricks) moves below the reference sections; nothing is removed. The banner (assets/banner.png) is also the new GitHub social preview, generated from .github/social-preview.json.
The setup beginner path asks only the essentials: the Delegation mode and Routing questions in user scope, and the workflow and Agent skills block questions in project scope. Moving the data root, the agent scan, the notes read-back, hiding local files, companions, extras and the instructions offer wait for a later run or add <feature>, each still with its own question. User scope ends with one line on how to adopt the review gate in a repository. A feature that needs the agent scan reuses the answer given earlier in the same run instead of asking it again.
afk.py check answers a missing, expired, stopped or exhausted lease with one fixed end line in its JSON telling the agent to stop any loop or wakeup it started for the lease and report to the user, so a host /loop started under /afk is told to end at its first check after the lease ends, without the user typing /afk stop (advisory: the agent stops the loop; no script kills it). A lease whose runs or runtime minutes are spent now answers exhausted instead of limit; limit is left for the rolling-hour action cap, which frees up. Breaking for scripts that match limit; match exhausted instead.
Breaking for away flows that log a merge: run the allowed gh pr merge <number> --match-head-commit <sha> check first. afk.py log --kind merge --pr <number> --head <sha> is refused unless an allowed gh pr merge <number> --match-head-commit <sha> check of the live lease pinned that number and head, so the head that lets the merge gate's cleanup remove a worktree is bound to an allowed merge check (not to proof that GitHub merged it); an allowed merge check records the pair in the private afk log. A check whose repository identity cannot be validated keeps its own folder, so the work-tree gate never falls back to the process's working directory.
Fixed
readme_check.py reads a hosts list in .github/readme-standard.json, so a plugin for Claude Cowork only, whose manifest is .claude-plugin, is no longer asked for a Claude Code badge, header mention and install section. A code fence that opens inside an unclosed HTML comment no longer hides the rest of the README.
While an away lease is live, agents no longer stop to wait for the user: afk "Decide" now names every hand-off it covers (a question tool or text question, a wrap-up question, an open decision in a plan, a skill step where the owner decides such as review-gate's stop after two rework rounds) and says never to end a turn waiting for an answer. The away question gate's denial and the session-start away line say the same: never ask or wait for the user; only stop work parks.
afk.py check lets one exact <!-- fnl-router depth=... trigger=... --> line through in pull request and commit text, so an away flow can open the pull requests that merge_check.py accepts; every other <!-- fnl- marker, a second router line and a malformed one stay forbidden.
/setup add afk asks fewer, clearer questions. Inside a repository it first asks whether the rules are for your account (every repository) or only this repository. After the account rules it asks once whether this repository should differ and then only the ticked keys, instead of asking the five repository keys again; the repository's stored object is shown first, a No previews its removal behind the save question, and project_progress.py settings ... --dry-run now returns current (the stored object) and changed (the effective values the change would move). The five limits are one question with the suggested values, asked as numbers in one round only on No. The table of what waits for you starts with "Keep the table as shown?", and only on No lists the seven changeable rows as two multi-selects (ticked kinds the agents may decide; unticked or unanswered ones wait for you), then confirms each row moved to decide. Each permission keeps its own question. The repository part lives in setupreferences/afk-project.md.
readme_check.py no longer hides README text between a <!-- and a --> written inside code spans or blocks: comments are blanked only outside code. The README reference states which override errors exit 2.
afk.py check lets an install that is the main checkout (a -dev install read from it) remove a merged linked worktree, as afk "Merge gate" says: git worktree no longer counts as a command that changes the install's own work tree, since its only Tier 1 form removes another worktree and still refuses the main checkout, a forced removal and any worktree holding the install (owner, 13/11/2026). The worktree rule docs name log --kind merge --pr <number> --head.
afk.py check: a merge check's number takes the ASCII grammar of log --pr.