Skip to content

Releases

v0.30.0

Choose a tag to compare

@lutzseverino lutzseverino released this 18 Nov 12:32
e456c8a

Standard: Contextual update: the run asks for contextual work on comments, github-repository-configuration, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.
Questions reported by the update: scope:comments, scope:documentation, scope:github-repository-configuration, assessment:comments, assessment:github-repository-configuration. Remote setup: both GitHub remote setup fixes deferred; no remote-setup question was asked.

Factory: Contextual update: the run asks for contextual work on comments, factory-workflow, github-repository-configuration, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.
Questions reported by the update: scope:comments, scope:documentation, scope:factory-workflow, scope:github-repository-configuration, assessment:comments, assessment:factory-workflow, assessment:github-repository-configuration. Remote setup: both GitHub remote setup fixes deferred; no remote-setup question was asked.

Workbench: Exact update: nothing is needed beyond reviewing and committing the update.
Questions reported by the update: none. Remote setup: no remote setup; no remote-setup question applies.

These action lines and question IDs are the disposable verification fixtures’ actual results; each adopting repository reports its own scope, assessment and setup questions.

Requires Repository Standards CLI 10.0.0 or newer; use the newest published CLI for updates. Node.js 24 or 26 remains required by installed executables. The branch-update proof requires Git 2.38 or newer (merge-tree --write-tree); the separate ownership collector's higher Git prerequisite remains tracked by #998.

Changes since v0.29.0

  • Re-record already-approved readiness when a requested companion label was missing. (PR #1171, #1083).
  • Repo Canon self-adopts v0.29.0 with CLI 11.0.1; publication of v0.30.0 does not perform its next self-adoption. (PR #1177, #1028, #1059).
  • Permit the first branch update, then at most two further non-overlapping updates in the same delivery attempt; preserve completed reviews only with verified unchanged-patch evidence. (PR #1123, #1084, #1113).
  • Leave a named step to an environment that explicitly says it performs it; preserve the required-check condition for merges. (PR #1124, #1114).
  • Add direct-contract footprints and refuse new specification readiness until superseded open issues have a recorded fate. (PR #1179, #1063).
  • Answer a factory stop by applying its exact next state or closing it; add the canonical state:carried label for requests already carried by a recorded outcome. (PR #1180, #1015, #1085, #1115).
  • Order renamed workflow states by their label history, preserving the latest person's decision. (PR #1170, #1060).
  • Stop requiring prettier-plugin-astro in confirmed shared TypeScript packages. (PR #1068, #915).
  • Refuse merges that retain a closing contract's resolvable declared deletion or edit a surface another open issue declares deleted. (PR #1183, #1064).
  • Record the decision to show one-way changes as animatics; the future animatic skill/toolchain work remains separately owned. (PR #1108, part of #1103).
  • Read review fields as rendered Markdown so examples, quotations and unrelated fenced content cannot masquerade as standing assessments. (PR #1016, #815).
  • Factory triage reviews direct body contracts without writing an Agent Brief, and reports an exact-revision stop for a person to route. (PR #1186, #1145).
  • Ship #1146: Repo Canon owns producing/verifying factory direct-contract review attestations, and the validator can accept the configured factory triage author's readiness for the exact independently reviewed revision (ADR 0053). (PR #1187, #1146, part of #1144).
  • Allow a contract-review verdict as a comment occasion. (PR #1189, #1151).
  • Clarify that merge holds come from Scriptorium configuration; absent configuration or keys add no hold. (PR #1191, #1154).
  • Align GitHub adoption guidance with the proven private-plan freshness path. (PR #1190, #1153).
  • Pin code-review comparisons to the merge-base for both review axes. (PR #1193, #1158).
  • Name the enforced Wayfinder map sections in the issue-tracker setup. (PR #1192, #1157).
  • Explain that naming a user-invoked skill in a prompt or brief invokes it, while retaining the invocation flag. (PR #1195, #1159).

Breaking standards change

Breaking standards change. This release changes readiness and delivery workflows that previously conformed on v0.29.0. It therefore uses a pre-1.0 minor bump and feat!.

Impact: new readiness grants to directly authored specifications and implementation tickets require substantive Supersedes:, Adds: and Deletes: fields. Durable surfaces, rather than file paths, belong in those footprints; none is allowed with its applicable meaning. A superseding specification is refused while an affected open issue has no recorded Fate: linking that specification. Already-recorded approvals remain valid; this release does not require a mass contract rewrite. Recording missing companions or refreshing a stale parent can still stop before writes on a legacy invalid footprint (known #1188).

Impact: babysit now refuses delivery (exit 3) for a resolvable declared deletion still present in the reviewed head, a resolvable surface touched by the PR that another open issue declares deleted, or otherwise unreadable required deletion evidence; a forbidden or unauthenticated read of that evidence exits 1 instead, like other permission refusals. Skills, skill references and rule sections are resolved; unsupported surfaces are reported as unchecked. Existing hold and owner gates remain independent. Answering a factory stop now uses the exact next state it names, or closure. Removing a label or posting an answer alone grants no continuation. The new state:carried is a holding state, not readiness; its host support is a known limit (#1181).

Migration: (1) All profiles: update with the newest published CLI, selecting v0.30.0 through one ordinary adoption run. Review its actual scope, assessment and deferred remote-setup questions. (2) Wherever the installed issue-contract workflow or ready.mjs grants readiness: before new direct-contract readiness, write the three footprint fields using owned surfaces. For a superseding specification, identify affected issues, record their fates and resolve required cross-repository access; then obtain the current validator notice and authorized exact-revision acceptance. A revised accepted contract loses readiness and needs renewed review. Leave unchanged recorded approvals intact. (3) All profiles, when delivering with the installed merge helper: actually remove the resolvable surfaces declared in the closing contract; route collisions with other tickets' deletions through their normal ownership path. Where factory stops occur, answer each using its stated next state. (4) Standard and factory only (workbench has no remote setup): complete the canonical-label remote setup w...

Read more

v0.29.0

Choose a tag to compare

@lutzseverino lutzseverino released this 17 Nov 10:33
v0.29.0
37c1f2c

Standard: Contextual update: the run asks for no contextual work. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.
Questions in the update from v0.28.0: scope:documentation.

Factory: Contextual update: the run asks for contextual work on factory-workflow, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.
Questions in the update from v0.28.0: scope:documentation, scope:factory-workflow, assessment:factory-workflow.

Workbench: Exact update: nothing is needed beyond reviewing and committing the update.
Questions in the update from v0.28.0: none.

These lines and questions are the authenticated prepublication release:check-update output. CLI 10.0.0 adopted v0.28.0 and CLI 11.0.1 updated each profile to v0.29.0; every update completed and was ready to commit. Standard and factory retained both deferred GitHub remote setup fixes; workbench had no remote setup. Actual adopter questions also depend on its own scopes and pending setup. Authenticated published-release verification passed all ten checks; see the verification record below.

Requires Repository Standards CLI 10.0.0 or newer; use the newest published CLI for updates.

Changes since v0.28.0

  • Owner gates in direct merges (#863, #1149): babysit's merge helper checks current gate: labels on the pull request and every closing issue before slow validation and again immediately before the merge. A gate prevents the merge with existing exit 3. Review and merge share the owner-gate reader. Named issue numbers and complete relationship/label reads retain their existing limits.
  • Hold labels belong to each holding item (#1020, #1141): babysit verifies each listed issue or PR's own labels before treating it as a repository or release hold. An unrelated issue with the same number as a holding PR no longer creates a false hold. Verified holds still return exit 9 when every listed item's own labels confirm its hold; the release PR still exempts itself.
  • Factory model-policy ownership (#1062, #1126): Scriptorium owns the model-policy schema, resolution, fallback and provider-diversity mechanics. Repo Canon removes its duplicate policy reader and adoption check. Existing repository-owned .github/factory-model-policy.json bytes stay intact and are validated by Scriptorium, not repaired by adoption. The choosing rule is now “fit first, then narrower, then cheaper,” using host guidance. The codebase-design ownership example and orchestration fallback guidance follow that ownership split.
  • Maintainer read-set budget (#1058, #1169): Canon computes each entry point's transitive declared read set and compares bytes with its pinned base. The required Read set check replaces line caps with measured growth; a growing PR needs a Read set: reason in Merge Danger. This repository's workflow and measurement script are maintainer tooling, not a new installed adopter check. The installed PR metadata validator exports its existing meaningful-text helper for this maintainer check; its validation behavior is unchanged.

Migration

Breaking standards change.

Impact: Factory-profile work must choose fitting models by the revised “fit first, then narrower, then cheaper” rule rather than choosing only by fit and cost. Factory adoption no longer validates the repository model-policy schema itself. Direct babysit merges in every profile, including standard, now refuse any gate:-prefixed label on the PR or a closing issue with exit 3; standard adopters using that prefix for unrelated purposes must account for the refusal. Incomplete owner-gate evidence also refuses with exit 3. Standard and workbench adopters do not gain a model-policy file or a new hosted read-set check. Existing application code is unaffected; adopters that cannot migrate remain on v0.28.0.

Migration: (1) Update with the newest published CLI and select v0.29.0. (2) Factory adopters reassess factory-workflow, use any narrower-model relationships the host already declares (otherwise choose by fit and cost), and follow Scriptorium's model-selection documentation for policy validation/resolution; preserve their own policy values. This release deploys no host change. (3) Repositories with callers or fakes for babysit/review must keep their repository/remote context and trusted default-branch reads, provide complete current owner-gate and per-holding-item labels, and assert exit 3 for owner gates and exit 9 for verified holds without treating either as a merge. Transport fakes must answer the two additional OwnerGates GraphQL reads per merge invocation. round.mjs now reads the PR's own labels and its closing issues through that same OwnerGates query, replacing its ReviewRoundIssues query and its use of the REST pull labels, so its fakes must return complete PR and closing-issue labels connections (pageInfo.hasNextPage: false, nonblank names); it exits 1 for incomplete or unreadable label evidence, including a named issue's label array. An item returned by the hold filter with missing or nonmatching own labels refuses with exit 3 rather than exit 9, even alongside verified holds (matching is case-sensitive). Tests importing the removed model-policy check or helper must move that validation to Scriptorium. Babysit and review command arguments and exports remain as before; owner-gates.mjs is an installed shared dependency, so copy/install whole skill directories. Run the repository's caller fixtures against the installed files. (4) Review the update and its checks before committing. Repo Canon's own self-adoption is separately tracked by #1059; this release carries #1149 but does not perform that adoption.

See adoption and caller-compatibility preparation, release versioning, and babysit merge contracts.

Known limits

Two additional non-security source findings are reported unfiled in lutzseverino/repo-canon, because this release's authorized scope excludes editing other issues:

  • Stale factory model-selection guide pin (rules/factory-workflow.md:142): the installed link points to Scriptorium v4.1.0, whose guide still says Canon validates model policy and cannot declare narrower models. The narrowerThan facility and corrected ownership documentation first ship in Scriptorium v4.2.0. The source pin is unchanged here; the Scriptorium-side stale sentence is tracked by scriptorium#257. No host upgrade is performed by this release.
  • Unsettled guidance fallback (rules/factory-workflow.md:134): the previous instruction to use the configured host default and disclose that guidance did not settle the choice was deleted without an installed replacement. No new fallback is inferred here. This needs an owner decision alongside #1031, whose grill also covers removed hand-launch quota guidance and choosing examples.

The owner's standing delegation, 2026-11-13, says: “known non-security defects ship named as known limits in the notes rather than holding the release.” These defects are not corrected here; fixes follow their normal routes and reach adopters through a later update. The dispositions are recorded on the public issues, not in private planning records:

  • #1142: pull_request_target workflow enforcement changes on 2026-12-02 can prevent public adopters' required PR metadata check from reporting; the fix remains due before that date.
  • #1132: GitHub App installation credentials cannot satisfy the shared GET /user read; README/About comparison can be skipped with a note and canonical-label setup can be blocked. Confirm the comparison with an already-authorized signed-in user where applicable.
  • #1136: a successful merge with an unreadable response can report stale base, exit 4. Read the PR state before acting on exit 4.
  • #1097, also #1055: the ownership collector can exit 0 without output through a symbolic-link path. Invoke its real path.
  • #1060: a readiness label renamed in place can still lose readiness when its raw live timeline name is compared.
  • #915: Astro discovery/...
Read more

v0.28.0

Choose a tag to compare

@lutzseverino lutzseverino released this 17 Nov 01:47
v0.28.0
8e67e2d

Standard: Contextual update: the run asks for contextual work on comments, git-attributes, github-repository-configuration, repository-readme, typescript-vite-stack, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.
Questions in the update from v0.27.0: scope:comments, scope:documentation, scope:github-repository-configuration, remote-setup, then the assessments comments, git-attributes, github-repository-configuration, repository-readme and typescript-vite-stack.

Factory: Contextual update: the run asks for contextual work on comments, factory-workflow, git-attributes, github-repository-configuration, repository-readme, typescript-vite-stack, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.
Questions in the update from v0.27.0: scope:comments, scope:documentation, scope:factory-workflow, scope:github-repository-configuration, remote-setup, then the assessments comments, factory-workflow, git-attributes, github-repository-configuration, repository-readme and typescript-vite-stack.

Workbench: Exact update: nothing is needed beyond reviewing and committing the update.
Questions in the update from v0.27.0: none.

These lines come from release:check-update, which updated a v0.27.0 fixture of each profile to this release with the newest public CLI. A real adopter's questions also depend on its own scopes and remote setup.

Requires Repository Standards CLI 10.0.0 or newer, unchanged. Use the newest published CLI for updates. See the adoption guide and standalone skill installation.

README description and the GitHub About description

Breaking standards change. The Repository README rules now require the repository's GitHub About description to be the README description, word for word, and a project that has an icon (an image it already uses as its own mark, such as its site icon, favicon or app avatar) to start its README header block with that icon. The repository-readme-structure check compares the two descriptions, ignoring surrounding and repeated whitespace. Ships #892 through #1131.

Impact: a repository whose GitHub About description is empty or differs from its README description no longer conforms; once it updates, repository-readme-structure fails with a correction that quotes both texts. A project with an icon that its README header does not show no longer conforms; the adoption's contextual assessment reports it, the check does not. When the GitHub read is unavailable (no or signed-out gh, no single github.com remote, a refused or failed request), the check adds a note that the description was not compared and keeps its other results. Repositories that stay on v0.27.0 keep the earlier rules.

Migration: (1) Make the GitHub About description the README's one-sentence description, for example with gh repo edit --description "<README description>", or change the README sentence to the About text. (2) If the project has an icon, add it as the first item of the README's centered header block; a project without one changes nothing and creates no icon. (3) Run the adopt update, complete the repository-readme assessment, and confirm with repo-standards check that repository-readme-structure passes and reports that the descriptions match. Under a GitHub App installation token, the shared read's GET /user is refused, so in the factory the comparison is skipped with a note; run the check once with a signed-in user gh to confirm the match.

Factory triage result labels

Factory profile: .scriptorium/config.json now declares runKinds.triage.resultLabels ["type:", "model:", "priority:", "factory:skip"], so a factory triage run can request those label families and the exact factory:skip label with its result instead of leaving them to a hand step (#1088, #1100; adopters' gap tracked in #1133). The file is installed exactly. A repository that changed its copy locally, such as Scriptorium's own advanced $schema pin, sees that edit as a confirmation-required overwrite on each update; confirm keeping the local edit or accept the canonical bytes. Owner, 2026-11-16: Scriptorium keeps confirming its own pin.

The factory rules and triage skill also change how triage works: an accept mode for brief review (#976, #984, #1128); stage inputs in the canonical stages table (#983, #1118); no type: label requested for directly authored specifications and tickets (#1109, #1111); triage's ready.mjs creating a missing factory:skip label before applying readiness, from label metadata it shares with label setup (#796, #1000); label setup checked against the canonical policy tables (#882, #1038); and the factory skill choosing a ticket's model under the installed Model selection rule (#989, #1130). The factory host-compatibility and hold-continuity guidance is corrected (#957, #990).

Delivery, review and orchestration

  • Babysit counts edits to a reviewer's comment as responses (#969, #1090), accepts a GitHub App's "Resource not accessible by integration" refusal on the private-plan protection probe (#839/#952, #1101), and its delivery rules resolve keep-both reconstruction conflicts (#1086, #1096).
  • Review reassesses settled contract findings on an unchanged head instead of stopping again (#864, #1025).
  • Workbench profile: a new retro skill writes a plan's retrospective, and orchestrate's close, intake and launch references use it (#982, #1094). Orchestrate reserves owner chores for work that needs the owner (#961, #1008), verifies a worker's retirement before replacing it (#836, #1024), and its wait wakes when a pull request link is removed (#784, #999).
  • The issue-contract validator matches factory triage logins without case sensitivity (#951, #1070), and keeps approvals and Seams exemptions stored under former readiness label names such as ready-for-agent, writing the canonical names (#996, #1138). Label setup and the validator share the new canonical label metadata operations/lib/canonical-labels.mjs, an exact file in every profile.
  • The Vite stack assessment no longer runs Astro checks (#955, #1071).
  • The Git attributes rules mark the code-review skill and the installed label metadata operations/lib/factory-labels.mjs and operations/lib/canonical-labels.mjs as vendored (#994, #1137); downstream adopters' git check-attr linguist-vendored -- operations/lib/factory-labels.mjs operations/lib/canonical-labels.mjs should report set for both. Repo Canon's own self-adoption leaves its own code unvendored.
  • Contribution guide and rules: links to installed rules and issue forms, and continuing past refused reads the work does not need (#813, #881, [#993](https://github.com/lutzseverino/repo-...
Read more

v0.27.0

Choose a tag to compare

@lutzseverino lutzseverino released this 12 Nov 00:49
v0.27.0
eb5a5d7

standard: Contextual update: the run asks for contextual work on github-repository-configuration, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Questions observed: scope:documentation, scope:github-repository-configuration, assessment:github-repository-configuration. Remote-setup questions: none newly asked. Both GitHub setup fixes remain deferred in the no-remote update fixture.

factory: Contextual update: the run asks for contextual work on factory-sandbox-image, factory-workflow, github-repository-configuration, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Questions observed: scope:documentation, scope:factory-workflow, scope:github-repository-configuration, assessment:factory-sandbox-image, assessment:factory-workflow, assessment:github-repository-configuration. Remote-setup questions: none newly asked. Both GitHub setup fixes remain deferred in the no-remote update fixture.

workbench: Exact update: nothing is needed beyond reviewing and committing the update.

Questions observed: none. Remote-setup questions: none newly asked. No remote setup is needed.

Observed questions/status come from disposable update fixtures; adopters validate their own scopes, contextual assessments and actual remote readiness before committing.

Requires Repository Standards CLI 10.0.0 or newer, unchanged. Use the newest published CLI for updates (11.0.1 at preparation). Adoption guide and standalone skill installation.

Factory inputs move to .scriptorium/

Breaking standards change. Factory-profile repository inputs and their readers now use .scriptorium/config.json and .scriptorium/Dockerfile, with a version-3 configuration linked to Scriptorium's published v4.1.0 schema. Declaration/profile identities, configured labels, the factory skill and the factory-workflow rules retain their names. This ships #884 through #968.

Impact: factory adopters using .factory/ must migrate their repository inputs and coordinate with a Scriptorium v4 host. Scriptorium v3.0.1 reads .factory/; do not update such adopters ahead of their v4 switch window. Readers of canonical configuration have no legacy fallback. A missing canonical file follows each reader's existing missing-config behavior, including no merge-hold configuration in babysit; malformed canonical configuration still fails. Standard-only and workbench profiles install no factory configuration. Repositories remaining on v0.26.0 keep its earlier layout and contracts.

Migration: (1) Before a factory/adopter migration PR merges, read its legacy configuration and confirm no open issue or PR carries its labels.hold or labels.releaseHold; new readers cannot discover holds from a legacy-only trusted base. (2) In the coordinated Scriptorium v4 switch window, run one normal repo-standards adopt update and complete its contextual assessments and ordinary canonical-config confirmation. The update targets canonical config; preserve an existing canonical Dockerfile, otherwise move the legacy Dockerfile byte for byte. Remove only the two known legacy files and their empty directory; unknown legacy content blocks the assessment and must be resolved explicitly without discarding it. (3) Update repository-owned scripts and fixtures that read the two old paths, then validate the newly installed files, canonical schema/configuration, sandbox workflow Dockerfile path, normal repository checks and ready-to-commit adoption status before committing. (4) Deliver the adoption PR through its normal gates, then verify pickup on the separately managed v4 host. An adopter unable to migrate stays on v0.26.0. This release run publishes only; it performs none of those adopter or host operations.

Repo Canon's own source already moved in #968; its CLI-owned adoption records remain unchanged by that source change or this publication. The downstream migration instructions apply to adopting repositories, with canonical Dockerfile bytes preserved rather than standardized. Factory image rules and configuration guidance.

Installed runtime callers and review timing

Babysit merge-hold reads, triage readiness's factory model-label policy and issue-contract validation's triage-result lookup now read .scriptorium/config.json. Their exported entry points, ordinary command arguments and exit-code meanings remain intact; the validator's factoryTriageResult(path) still accepts an explicit path, with a canonical default. Trusted readers still select the pinned destination-default-branch snapshot. Existing Git remote/context and repository-selection requirements remain in force.

When the configured reviewer has request.onOpen: true, babysit request/wait now read the complete paginated ready-for-review timeline. The latest ready transition adjusts response/review bounds and push freshness, including after returning to draft, while current-head completion and unavailability retain opening/explicit-request evidence cutoffs. Ready does not count against or replenish the request budget. Explicit-only review settings and app-author policy skips keep their prior behavior. This fixes the premature timeout after a long draft in #971.

Repository-owned callers/fakes must supply the issues timeline endpoint and valid ready_for_review timestamps where automatic-opening review applies, including pagination and failed-history reads. reviewRequestedAt accepts optional readyAt; reviewerState and wait's decide accept optional evidenceRequestedAt (defaulting to requestedAt); platform.mjs exports readyForReviewTime. Check current-head completion, draft/ready/re-draft timing, explicit-only requests, unavailable history and exempt-author paths. Direct CLI versus module invocation and existing policy-skip exit meanings are unchanged. Prepare caller compatibility explains prerequisite compatibility fixes and final adoption validation; this release cannot know every adopter's private callers.

Orchestration records and hand launches

Breaking standards change. The workbench/standalone orchestrate status reader now validates In flight Waiting on values: owner, factory, launch, orchestrator, third party: <name> or date: <UTC date or time>, with optional detail for the first four. Orchestrator-owned rows appear first as your move, in their original relative order; finished reports and owner actions retain precedence.

Impact: existing free-text values such as CI make status refuse the row with its item and invalid value until repaired. The table headers, watches and budget projection remain unchanged. Migration: before using the new reader, map each existing row to the actual responsible party/category, keep its concrete detail and next check, then run wait.mjs --status --from <now.md> and confirm correct rendering. Updates act on each your move row or turn it into an evidenced wait. Repositories unable to update records retain the prior release's skill bytes.

Hand launches select their skill from the shared Canonical stages table, use stage: item names and the stage as their Running launches Kind, invoke the named skill, and record the launch and gap together. Missing hand skills remain reported gaps rather than invented coverage. Launch questions first become report/incoming evidence; the orchestrator reuses dated settled answers, lists permitted inferences for veto and routes remaining owner questions through its inbox. General contribution guidance retains neutral inference, readiness and authorization gates. Factory workflow and orchestrate. Ships #966, #972 and #978.

Maintainer release verification also accepts CLI 11's published update reports alongside CLI 10, preserving all existing outcome, answer, selection, readiness and deferred-setup gates (#974). This does not ship #962 or raise the minimum CLI.

Known deferred defect

#915 remains unfixed: standard/factory Astro discovery and manifest checks can falsely reject a conforming plain shared TypeScript package when its formatter is declared only by the consuming Site. Workbench has no web-stack checks. The affected helper is unchanged from v0.26.0; earlier issue evidence also confirms v0.24.0 and v0.25.0, while earlier affected versions remain uncertain. No correction is implemented or validated in this release.

Owner, 2026-11-11T22:1xZ: “Let's go with recommended actions.” The recorded disposition explicitly authorizes v0.27.0 without the fix, with this known-defect notice, and sends the correction through the normal route to the next ordinary release. Publication does not fix installed adopters.

Other inherited known limits

These limits are inherited from v0.26.0 an...

Read more

v0.26.0

Choose a tag to compare

@lutzseverino lutzseverino released this 11 Nov 05:09
v0.26.0
59969a4

standard: Contextual update: the run asks for contextual work on comments, git-attributes, github-repository-configuration, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Scope questions: scope:comments, scope:documentation, scope:github-repository-configuration. Remote-setup questions: none; both github-repository-configuration/canonical-labels and github-repository-configuration/pull-request-integration remain deferred. Contextual assessment questions: assessment:comments, assessment:git-attributes, assessment:github-repository-configuration.

factory: Contextual update: the run asks for contextual work on comments, factory-workflow, git-attributes, github-repository-configuration, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Scope questions: scope:comments, scope:documentation, scope:factory-workflow, scope:github-repository-configuration. Remote-setup questions: none; both github-repository-configuration/canonical-labels and github-repository-configuration/pull-request-integration remain deferred. Contextual assessment questions: assessment:comments, assessment:factory-workflow, assessment:git-attributes, assessment:github-repository-configuration.

workbench: Exact update: nothing is needed beyond reviewing and committing the update.

Scope questions: none. Remote-setup questions: none; no remote setup applies. Contextual assessment questions: none.

Requires Repository Standards CLI 10.0.0 or newer (unchanged). Use the newest published CLI for the single-run update from v0.25.0.

This release ships Seams on new Agent Brief revisions, trusted required-check enforcement, explicitly activated body-contract tooling, the validator namespace migration, the shared Ownership check, canonical planning stages, host-aware model choice and the orchestrate rewrite. It is the first Seams release; it does not include #884's later .scriptorium/ migration.

Breaking standards change. New and actually revised triaged Agent Briefs must include a meaningful Seams section describing applicable triggers, value ownership, consumers, reversibility, cost and chosen/deferred seams.

Impact: a new or revised brief without Seams cannot receive readiness. Exact pre-cutover approved revisions remain eligible without bulk renewal while unchanged; their next actual revision requires Seams. Current readiness and authorization rules continue to apply. The first shipping boundary is the immutable annotated v0.26.0 tag, its source commit and the ordinary release's first publication time. Until it resolves, the validator leaves labels and feedback untouched with an unresolved-boundary diagnostic.

Migration: 1. Before adoption, prepare downstream result readers for repo-canon/issue-contract-state/v3, its baseFormat and exemption evidence while retaining supported v1/v2 handling. 2. Adopt the release and update brief writers/reviewers to include Seams. 3. Retain unchanged eligible earlier approvals; add Seams when a brief is actually revised, then obtain its notice and independent readiness normally. Do not bulk renew or invent an adopter cutover tag/configuration. Offline caller fixtures must inject fixed authenticated boundary facts or substitute the resolver; platform fakes must cover the additional annotated-tag and release reads.

See the Seams/result contract.

Breaking standards change. Delivery requires a repository-owned .github/required-checks.json on the trusted destination default branch.

Impact: wait and merge require positive current-head success for every exact declared check name. Missing, pending, failed, skipped or neutral required checks cannot pass. The old five-minute no-check success is removed. The declaration must be readable and valid; a proposed/local file is not authority. First remote project adoption must establish this policy separately after the README-only founding commit, and retain the owner-delivery stop while the trusted metadata workflow is absent.

Migration: 1. Establish the repository-chosen version-1 declaration and exact required names through the destination's owner correction route before delivering with the new helpers. 2. Confirm the named workflows/statuses run and succeed on the current head. 3. Adopt, then exercise repository-owned callers and fakes against the newly installed helpers. Fakes must supply trusted default-branch declarations, status timestamps, complete workflow/attempt facts and configured-reviewer thread reads. Wait retains its 0–7 classes, including policy skip 6 and malformed trusted configuration 7. Merge adds exit 6 for unresolved configured-reviewer threads; current-head/check races use 2, owner handoff 3, stale base 4 and holds 9. Check operations report semantic failure as JSON at exit 0 and malformed invocation at exit 1; callers must interpret the protocol. Existing authenticated Postern transport, Git repository context and destination selection remain required. Test invalid/missing declarations and missing check names as refusals, and test unresolved threads before a successful merge.

See trusted check and delivery guidance and PR integration.

Breaking standards change. The standard-owned validator entry points move from scripts/validate*.mjs to vendor/repo-canon/validate*.mjs.

Impact: repository-owned tests/scripts that execute or import the old paths must migrate. The neutral command remains executable with one JSON input path and POSTERN_TOKEN; the trusted GitHub trigger remains .github/scripts/validate.mjs <kind> with GitHub event input and GITHUB_TOKEN. The core issue-contract module remains import-only: directly executing it does not validate anything. Its import-only property and platform transport predate this release; the changed paths and new resolver/source interfaces require caller review.

Migration: 1. Prepare prerequisite caller changes using compatibility preparation. 2. Adopt once and update imports/execution to vendor/repo-canon/validate.mjs and vendor/repo-canon/validate-issue-contract.mjs. Core callers invoke the exported runIssueContractValidation or decideIssueContract; neutral callers use validate with the added boundary resolver seam. 3. Run the repository's own caller tests and prove invalid input still fails and intended feedback/label outcomes occur. Downstream adopters update exact linguist-vendored entries for relocated validators and new source/store/cutoff helpers, preserving repository-owned attributes; git check-attr linguist-vendored -- vendor/repo-canon/validate.mjs should report set. Repo Canon's self-adoption keeps its authored code unvendored (unspecified); it must not add downstream vendoring for its own source.

Breaking standards change. orchestrate is now selected only by the workbench profile, with canonical-stage routing and structured launches.

Impact: standard/factory project adoption no longer installs orchestrate. Normal updates retire unchanged obsolete installations and preserve locally edited authoritative files under the CLI's ordinary protection. Workbench and standalone users receive new launch coverage, owner relay and record requirements; private workbench state is not automatically rewritten by adoption.

Migration: 1. Adopt workflow skills in a separate workbench, or install the tagged standalone bundle. Keep project and workbench ownership distinct. 2. Review existing index.md, now.md, inbox, plan and launch records against the candidate templates; keep the exact Item | Running | Waiting on owner | Since (UTC) | Next check status header and structured watch/launch records. Do not put status: done on an in-progress report; append it only after the full current-turn report is written. 3. Route canonical stages through configured factory coverage, logging gaps and preserving independent contract/implementation review. wait --status --from <records> may take --budget <status.json>; budget display preserves host data and grants no launch admission. Existing timeout exit 0 means reconcile and rearm, not task success. 4. Reconcile open owner questions, executable owner chores, expedited pauses, provenance and findings-based closure. Canon self-adoption preserves its authoritative locally edited orchestrate directory through normal update evidence rather than a manual restore or state edit.

Compatible additions include optional explicit body-contract activation with durable cutoff/ledger/source proof. Installing this release does not activate body mode or authorize host publication/cutoff. Prepare compatible readers and dual-route writers, freeze publication and use the body-contract protocol only under the separate activation decision. Prepared mode continues its latest-comment route; active mode retains only exact unchanged inventoried legacy contracts until their actual revision. The installed issue workflow needs its declared Contents/Issues permissions and named reevaluation dispatch. No blanke...

Read more

v0.25.0

Choose a tag to compare

@lutzseverino lutzseverino released this 09 Nov 02:50
v0.25.0
4cc6a32

standard/factory: Contextual update: the run asks for no contextual work. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Questions reported: scope:documentation for both profiles. No new remote-setup question was asked; status retains both GitHub setup fixes as deferred.

workbench: Exact update: nothing is needed beyond reviewing and committing the update.

Questions reported: none; no contextual assessment or remote setup.

Outside adoption, orchestrate users must migrate existing workbench records and wait callers using the ordered Migration below.

Requires Repository Standards CLI 10.0.0 or newer (unchanged).

Breaking standards change. Orchestration now watches durable workbench records and renders status from those same records.

Impact: workbenches using the earlier now.md tables, launch records or wait-timeout exit contract need migration. The current tables require explicit linked Item identities, Watches JSON, UTC timing, evidence and current-turn report paths. A report completes a turn only when its complete content ends with status: done, including a turn that stops on an owner step. Timeout now returns exit 0 (previously 2); exit 0 means reconcile and re-arm, not that the task succeeded. Usage, read and platform errors remain exit 1. This workflow change reaches the installed orchestrate skill in every profile; it does not rewrite an adopter's private workbench automatically. Adopters remaining on v0.24.0 retain its earlier contract.

Migration: (1) inventory repository-owned wait wrappers, imports, transport fakes and workbench records before committing adoption, following caller compatibility preparation; deliver any prerequisite caller fix separately; (2) run the newest public CLI's adopt and select v0.25.0, reviewing its actual scopes, contextual assessments and remote setup questions; (3) migrate each workbench's now.md to the released templates, preserving owner decisions and unfinished rows, and give every launch its current-turn Report path; clear an earlier final marker before resuming or use a fresh report; (4) update wait callers to reconcile and re-arm after events or timeout exit 0, retain explicit positive --interval and --max-duration, use --from now.md to reload record-owned watches, and keep incoming/harness/owner coverage; (5) run plain-Node installed-script caller fixtures and node .agents/skills/orchestrate/wait.mjs --status --from <workbench>/now.md, verify final-marker handling and owner-only rows, then deliver the adoption. If migration cannot be completed, remain on v0.24.0. These record/caller steps apply wherever the orchestration workflow is used; downstream repository-owned callers need verification against installed files. Repo Canon's release fixtures exercise its own callers, without claiming coverage of private adopter suites. No executable entry point was removed: wait.mjs remains executable and importable, and records.mjs is its new installed helper. The wait fetches upstream observations without pulling, and status mode reads only records/report files without platform access. Repository-owned transport fakes must cover any raw PR head/check/status observations they use, preserving repository context and current recorded expectations.

The workbench profile adds create-repository and create-adopted-repo, also available in the tagged standalone skill bundle. The general entry point confirms repository choices, makes a README-only founding commit, optionally delegates standards adoption, and routes small/large/skipped vision work. The wrapper keeps adoption on and skips that interview question. Install the separately distributed adopt-repository-standards dependency before adopting; selected vision routes have their own listed dependencies. Standard and factory profiles install neither creation entry point. See create a repository and tagged skill installation.

This release also records the grill G2 decisions about check location, implementation-contract home and planning terminology in domain/development documentation. It includes merged #894, #893 and #874.

Known issue: #915: the inherited Astro manifest check can incorrectly require prettier-plugin-astro in a plain shared TypeScript package or workspace root even when its consuming Site declares the formatter. Confirmed in v0.24.0 and this candidate; earlier affected versions are unknown. No correction is included. The owner's patch-now versus next-ordinary-release disposition for a future correction is routed separately.

Adopter rollout remains held for the later switch window. Publishing this release updates no adopting repository. Live create-and-adopt acceptance remains #891.

Adoption guide · Versioning

Verified publication: annotated origin tag v0.25.0 peels to release commit 4cc6a329fa95a8152aa8ffd88193b4742d1ebcfe, delivered by release PR #921; the GitHub release is neither draft nor prerelease. Authenticated public CLI 10.0.0 inspected and fixture-adopted standard (62 declarations), factory (67) and workbench (36), each complete and ready to commit. Previous v0.24.0 fixture adoptions made with CLI 10.0.0 updated in one run using newest CLI 10.0.1 to this release in all three profiles, complete and ready: standard/factory asked scope:documentation and retained both GitHub setup deferrals; workbench asked no questions and needs no remote setup. Public source/document version agreement passed with the unchanged minimum 10.0.0. No tracked adopter was updated.

v0.24.0

Choose a tag to compare

@lutzseverino lutzseverino released this 08 Nov 20:41
v0.24.0
d5f7a80

standard: Contextual update: the run asks for contextual work on comments, github-repository-configuration, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Update-check questions: scope:comments, scope:documentation, scope:github-repository-configuration, assessment:comments, assessment:github-repository-configuration.

factory: Contextual update: the run asks for contextual work on comments, factory-workflow, github-repository-configuration, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Update-check questions: scope:comments, scope:documentation, scope:factory-workflow, scope:github-repository-configuration, assessment:comments, assessment:factory-workflow, assessment:github-repository-configuration.

workbench: Exact update: nothing is needed beyond reviewing and committing the update.

Update-check questions: none.

The standard/factory fixture updates retained the two existing remote-setup deferrals; neither asked a new remote-setup question. Actual adopter setup is reviewed in its adoption run.

Requires Repository Standards CLI 10.0.0 or newer (unchanged).

Breaking standards change. Phase A replaces the factory's workflow contract with configuration version 3, triage/implement/review run kinds, state:, gate:, type:bug/type:enhancement and priority: label families, revision-bound readiness, one review per head per round, and one run/action comment per occasion. implement hands a validated draft PR to the separate review agent when a review run is configured; factory repositories without one retain delivery through babysit. Factory triage can accept its own brief only under its explicit role and result constraints; ordinary research writers still cannot accept their own briefs. Comment rules become a repository-wide contextual declaration.

Impact: repositories following the earlier workflow must migrate their labels, readiness automation, contribution guidance and factory host together. Configuration version 3 requires a compatible Scriptorium host; publication does not upgrade that host. Existing repositories remain on v0.23.1 until their planned switch window. This release remains held from adopters; no adopter updates are authorized by this release run.

Migration: (1) prepare a compatible Scriptorium host and schedule the adopter switch; (2) run the public CLI's adopt to select this release, review the newly discovered comments scope and contextual assessment, and confirm label setup changes or explicitly defer unavailable remote setup; (3) validate repository-owned automation and caller fixtures against the newly installed files; (4) deliver the completed adoption and confirm revision-bound readiness, triage-to-draft and independent review-to-merge behavior. Adopters unable to migrate stay on v0.23.1. The workbench profile installs skills and their support runtimes and license notices, with no repository rules or GitHub setup.

Breaking standards change. Runtime integration contracts change alongside the workflow.

Impact: callers importing operations/lib/pull-request-reviewer.mjs or operations/lib/review-policy.mjs must use the babysit-owned modules selected by the new declarations. The issue validator's exported readiness labels and state handling use the new families; factory-result validation reads .factory/config.json's triageResult. Babysit's app-author policy gate now accepts a complete current-head PR review, rather than an issue-comment review outcome; merge exit 5 means that review evidence is missing. The review outcome module exports reviewTemplate, completeReview, and holdingReview in place of the old reviewOutcomeTemplate, completeReviewOutcome, and externalReviewSentence outcome-comment exports; it also exposes reviewedHead and reviewsSection. Required-check, expected-head, trusted default-branch reads and hold gates remain enforced. Repository-owned fakes must cover the pinned file reader and PR review transport and provide version-3 configuration and the correct Git repository context. Direct execution of import-only scripts/validate-issue-contract.mjs still does not run validation; callers use its exported runIssueContractValidation through the trusted entry point.

Migration: change readiness wrappers from ready.mjs <issue> <ready-for-agent|ready-for-human> <revision> ... to ready.mjs <issue> <revision> [companions...]. The command always applies state:ready and rejects state:* companions; use the tracker client for state:owner. After label renames, obtain the current revision notice, review that exact contract independently and reapply readiness; an old readiness association does not survive the rename. Inventory repository-owned imports, executable wrappers and transport fakes before committing adoption; update them to the new installed paths, exports, review record shape and expected exits; run those callers against the installed files and prove invalid input and missing current-head reviews fail. Follow caller compatibility preparation, separating prerequisite fixes from completed adoption. This applies to downstream-owned callers; it does not assert that every private adopter test suite was exercised.

Repository model policy is optional, repository-owned JSON; selection and fallback stay within host capabilities and credentials. Missing policy retains host defaults. Adoption validates but never repairs or owns that file. The private orchestration workbench rule keeps plans, decision inboxes and session-only artifacts outside project repositories; the orchestrate skill reconciles approved decisions and owner-only steps before closing a plan. Public repository contracts must be self-contained: copy relied-on dated decisions into the issue, brief or comment rather than requiring private workbench paths or URLs as inputs or provenance.

Adoption guide · Skill installation · Versioning

Verification: authenticated release:verify passed for release commit d5f7a8054ad79dc5c4e1d355fe99a95065eff4a8 from release PR #886. The annotated origin tag resolves to that commit and the GitHub release is ordinary (not draft/prerelease). Minimum CLI 10.0.0 inspected and adopted standard, factory and workbench fixtures, all ready to commit. Updates from v0.23.1 adopted with CLI 10.0.0 and updated with newest CLI 10.0.1 completed for all three profiles, with the questions and derived actions above; standard/factory retained both GitHub setup deferrals, workbench none. Version agreement also passed. No tracked adopter was updated.

v0.23.1

Choose a tag to compare

@lutzseverino lutzseverino released this 04 Nov 16:42
v0.23.1
08f3371

standard: Exact update: the run asks for no contextual work. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Questions reported by the verified update: scope:documentation. Both GitHub remote setup fixes remained deferred in the disposable fixture.

factory: Exact update: the run asks for no contextual work. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Questions reported by the verified update: scope:documentation. Both GitHub remote setup fixes remained deferred in the disposable fixture.

workbench: Exact update: nothing is needed beyond reviewing and committing the update.

Questions reported by the verified update: none.

Fix research/triage composition (#833, closes #831): research investigates in the assigned run and publishes its assigned artifact. Triage research publishes an Agent Brief plus triage notes for code-bound work, and decision facts without a premature brief for intent-bound work. Standalone research retains its cited Markdown publication and documentation-placement fallback. Neither triage research path requires recursive delegation or repository findings/index edits.

#832 records glossary terms and ADRs 0030–0031. Its future factory changes are not implemented by this patch.

Requires public Repository Standards CLI 10.0.0 or newer; the minimum is unchanged. This compatible correction requires no workflow migration or repository-owned runtime caller changes. Existing adopters receive it through their ordinary adoption update; publication alone changes no adopter.

Adoption guide · Owned skill installation · Versioning

Verification: authenticated release:verify v0.23.1 08f3371be50f9930f8a9272212c7796f6b10776c passed after release PR #838 merged. The annotated origin tag peels to that commit and the GitHub release is neither draft nor prerelease. Public CLI 10.0.0 inspected and freshly adopted all three profiles; updates from v0.23.0 using minimum CLI 10.0.0 to newest public CLI 10.0.0 completed and were ready to commit. Standard/factory asked only scope:documentation and retained both GitHub remote setup fixes deferred; workbench asked no questions, had no deferrals, and installed no rules or .github files. Document-version agreement passed.

v0.23.0

Choose a tag to compare

@lutzseverino lutzseverino released this 04 Nov 02:25
v0.23.0
3820834

standard: Contextual update: the run asks for no contextual work. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Questions reported by the verified update: scope:documentation. Both GitHub remote setup fixes remained deferred in the disposable fixture.

factory: Contextual update: the run asks for contextual work on factory-workflow, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Questions reported by the verified update: scope:documentation, scope:factory-workflow, assessment:factory-workflow. Both GitHub remote setup fixes remained deferred in the disposable fixture.

workbench: Exact update: nothing is needed beyond reviewing and committing the update.

Questions reported by the verified update: none. No remote setup was offered or deferred.

What changed

  • Factory profile gains the owned factory operations skill, configured repository holds, label provisioning and an independent babysit hold guard (#821).
  • orchestrate becomes a short core with three references (#822); sessions send messages through workbench incoming/, and wait can watch a directory on disk and fetch its upstream (#825).
  • The owner's “do this now” request records an expedited change and pauses the orchestrating agent's own launches and merges until that change merges (#826).
  • Contracts keep progress in linked PRs, comments and sub-issue states. Source delivery and live acceptance have separate tickets; one orchestrating agent owns a shared time-bounded host grant (#827).

Compatibility and migration

Breaking standards change.

Impact: workflows that record progress by editing ready contracts, close live acceptance by source merge, or let individual workers terminate shared grants must change to remain conforming. Earlier pins remain conforming to v0.22.1. Factory-profile repositories also receive the new operations skill and repository-hold configuration. This is v0.23.0 under the pre-1.0 middle-number bump rule.

Migration:

  1. Factory adopters must first upgrade the serving Scriptorium host to v3.0.0 or later, before adopting the new configuration. Older hosts pause a repository that declares the unknown labels.hold key. Standard/workbench adopters skip this host prerequisite.
  2. Run the newest public Repository Standards CLI adopt once, selecting v0.23.0; validate and submit the contextual scopes/assessments it asks for, then check ready-to-commit status and repository validation. Required CLI remains 10.0.0.
  3. For factory adopters, reconcile repository-owned tests/callers of babysit merge with hold exit 9: another held issue or PR prevents merge; the PR's own hold is exempt. Node.js 24 or 26, trusted default-branch configuration, GitHub CLI transport and existing positional merge arguments remain required. Factory label setup now provisions factory:hold as the third factory label; repository-owned exact-set/count fixtures and transport fakes must include it and verify the resulting label. Standard-profile labels and the operation invocation/result contract are unchanged.
  4. For affected workflows, stop editing implementation contracts after readiness to record progress; put progress in comments/PRs/sub-issue states. Split work requiring live proof into source and blocked live-acceptance tickets, and link source PRs with Part of the live ticket. Only recorded live acceptance closes that ticket. The orchestrating agent that requests a host grant owns it, lists all users before launch and ends it after the last report or at its bound; workers do not end it.
  5. For orchestrate workbenches, receive messages through incoming/; read and delete each only after taking it into the log or decision inbox. Existing file/tracker wait items remain supported. New dir:<path> watches direct children, fetches a configured branch upstream and exits 1 on failed fetch; verify repository-owned transport fakes and tests against the installed script. A branch without an upstream is watched locally only. Keep the three reference files beside the skill core. An expedited request pauses only work the orchestrating agent owns; running sessions continue.

Adopters unable to make these workflow changes stay on v0.22.1. Repository-owned runtime callers should follow compatibility preparation. Standalone installation uses the tagged skills bundle.

Verification

Verified release commit 3820834b333aca159adee5b5ba4fe38c9cf45b03 from release PR #830. Full authenticated release:verify exited 0: the annotated origin tag peels to this commit and the GitHub release is neither draft nor prerelease. Public CLI 10.0.0 inspections and fresh answers-file fixture adoptions passed for standard, factory and workbench, including ready-to-commit status. Updates from v0.22.1 using its minimum CLI and the newest published CLI passed for all three profiles; each exact CLI pair and result is recorded below. Document-version agreement passed.

  • CLI 10.0.0 adopted v0.22.1; CLI 10.0.0 updated to v0.23.0 with the standard profile; questions scope:documentation; outcome complete, ready to commit with both GitHub remote setup fixes deferred. Adopter action: Contextual update: the run asks for no contextual work. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.
  • CLI 10.0.0 adopted v0.22.1; CLI 10.0.0 updated to v0.23.0 with the factory profile; questions scope:documentation, scope:factory-workflow, assessment:factory-workflow; outcome complete, ready to commit with both GitHub remote setup fixes deferred. Adopter action: Contextual update: the run asks for contextual work on factory-workflow, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.
  • CLI 10.0.0 adopted v0.22.1; CLI 10.0.0 updated to v0.23.0 with the workbench profile; questions none; outcome complete, ready to commit with no remote setup. Adopter action: Exact update: nothing is needed beyond reviewing and committing the update.

Standalone published-bundle installation also passed with skills CLI 1.5.25 and the tagged .agents/skills/ URL: all 20 owned skills plus the bundled repository-standards helper installed as copies, every file matched this tag byte for byte, every lockfile ref was v0.23.0, and no Repo Canon adoption, rules, resource or .github files were present. This establishes installation without adoption; helper execution continues to follow each skill's Reads section.

Findings: #829, the stale factory declaration count, was corrected in the release PR. The existing pre-PR Direct-change factory hold gap remains tracked in #824.

v0.22.1

Choose a tag to compare

@lutzseverino lutzseverino released this 02 Nov 17:07
v0.22.1
66ba115

standard: Contextual update: the run asks for contextual work on github-repository-configuration, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Update questions: scope:documentation, scope:github-repository-configuration, assessment:github-repository-configuration.

factory: Contextual update: the run asks for contextual work on github-repository-configuration, which needs review before it is committed. Remote setup was deferred for github-repository-configuration/canonical-labels, github-repository-configuration/pull-request-integration: resolve it and run adopt again to apply it.

Update questions: scope:documentation, scope:github-repository-configuration, assessment:github-repository-configuration.

workbench: Exact update: nothing is needed beyond reviewing and committing the update.

Update questions: none.

Repo Canon v0.22.1 is a compatible patch to v0.22.0. Babysit can now merge on private GitHub Free repositories when both classic protection and rulesets positively report plan unavailability. Immediately before the expected-head merge it independently verifies the live default destination, unchanged validated/reviewed head, successful applicable validation on that head, and current-default-tip ancestry. Strict non-bypassable GitHub enforcement remains required wherever available. Ordinary permission failures still stop the run.

The owner accepted the residual concurrent-base race on the proven plan-limited path: another writer can advance the base between the final reads and the merge. These checks narrow that window but do not provide GitHub's atomic protection. A stale base follows the existing single branch-update recovery; a changed head requires renewed wait and review. No credential, ownership, reviewer, release-hold or explicit squash-message gate is relaxed.

Required Repository Standards CLI remains 10.0.0. No migration is required. Repository-owned tests or scripts that execute babysit's merge helper or fake GitHub responses should cover the precise dual plan-limit responses and final fresh-head check evidence, and expect stale-base exit 4, changed/unvalidated-head exit 2 and ordinary permission refusal to stop. Existing arguments, executable invocation, trusted configuration reads and expected-head squash contract are unchanged. The PR-integration setup message and adoption guidance now describe this supported delivery path.

See adoption, caller compatibility preparation, and babysit merge contract. Fix: #817, resolving #814.

Verification: authenticated release:verify v0.22.1 66ba1151327ae494336a9da9c75fd16d20cb2ef9 passed for release PR #819. The annotated origin tag peels to that release commit and the GitHub release is stable, neither draft nor prerelease. Public CLI 10.0.0 inspected and freshly adopted standard (60 declarations), factory (64), and workbench (33), resolving the release commit and reaching ready-to-commit status. Updates from v0.22.0 using baseline CLI 10.0.0 and newest public CLI 10.0.0 completed for all three profiles; the exact derived action lines and observed question coverage appear above. Standard/factory retained both GitHub remote setup fixes deferred; workbench asked no questions, deferred nothing, and installed no rules or .github files. Document version agreement passed. Factory's completed fixture assessment does not waive an adopter's own contextual review.