Shipped and released
Now
Page 13 of 14. Every release ever published is still here — across these pages, in theAtom feed, and at its own permanent link. Nothing is dropped as it ages.
Released highlights, page 13
- Agents now cut unnecessary work before adding code or process. Core's portable Razor ladder stops at the first sufficient option—skip, reuse, standard library, platform, installed dependency, one line, or the minimum working code—while preserving security, validation, accessibility, and explicit requirements.
- Repository work now enters through one clear intent and delivery path. Neutral intake routes to
intake-intentfor a minimum repo-owned intent,author-delivery-brief create|continuefor multi-spec coordination, ornew-specfor one independently shippable feature.
- Delivery work can now close without losing the reasons and promises that code and tests cannot explain.
close-workverifies repository-specific durable outputs, whole-document semantic freshness, obligations, dependencies, and authority before recommending a disposition. - Immediate disposal is safe by construction and never automatic. Every file removal needs a fresh human confirmation bound to the exact current target, fingerprint, disposition, evidence, authority, and session; any drift expires it.
- Delivery work can now close without losing the reasons and promises that code and tests cannot explain.
- Agents can now frame, create, update, review, and optimize portable agent skills through progressive, least-authority workflows. The foundation includes activation and behavior evaluations, deterministic compiled reference knowledge, and bounded failure contracts.
- Compatible organization or framework knowledge can inform skill work without coupling packs to another corpus. Workflows detect declared provider capabilities, invoke an eligible provider explicitly, and retain their complete baseline when no provider is available.
- Pack-owned OKF routers can now expose a bounded, explicit-only knowledge provider capability for compatible workflows. Raw OKF remains governed build-time input, while generated provider metadata supports deterministic discovery without implicit corpus traversal.
- Newly sectionless specs say why without retroactively gating adopters. The work-loop linter requires an explicit reason when a new spec omits its Acceptance-Criteria section or an existing spec removes that section, while grandfathering sectionless specs already present in an adopter's base ref.
- Maintainers can identify every unsupported legacy workspace record from a cold status read. Findings now retain a safe object slug instead of collapsing unrelated records under
workspace.toml. - Deferring an acceptance criterion no longer forces a legacy workspace record. A
(deferred: …)anchor now resolves from a canonical{path, kind}entry as well as a legacy{slug}one, so a new deferral can be recorded in the canonical shape.
- Maintainers can identify every unsupported legacy workspace record from a cold status read. Findings now retain a safe object slug instead of collapsing unrelated records under
- Generated OKF routers now keep hostile concept metadata inside its intended index entry. Titles, statuses, and concept types are bounded and escaped before they reach compiler-owned Markdown indexes, preventing metadata from fabricating links or additional entries.
- The shipped architect pack is discoverable again. Its architecture-lenses source now declares the required content licence, so
agentbundle show architectresolves it, and it accurately describes authored source versus generated router projections.
- The shipped architect pack is discoverable again. Its architecture-lenses source now declares the required content licence, so
- Adjudicators can settle a cited repository-file claim without an avoidable stop. A finding may now point to the current, confined file needed to test its own predicate, while review artifacts and all other scope boundaries remain excluded.
- Catalogue maintainers can now build portable Agent Plugins 1.0.0 packages offline. The normal build emits deterministic, schema-valid root manifests and canonical skill trees for every skills-only pack, with complete reasons for packs the route excludes.
- Catalogue maintainers now have an end-to-end guide for shipping pack-owned OKF knowledge. The documented path covers declaration, canonical concept authoring, deterministic compilation, drift and ownership recovery, normal catalogue verification, and inspection through
agentbundle show.
- Catalogue maintainers now have an end-to-end guide for shipping pack-owned OKF knowledge. The documented path covers declaration, canonical concept authoring, deterministic compilation, drift and ownership recovery, normal catalogue verification, and inspection through
- Machine-checkable reviewer claims can now be adjudicated without giving the adjudicator execution tools. The work loop may supply evidence from one predeclared, confined read-only gate; the attempt consumes the existing review retry budget and produces a complete independent replacement report.
- A bad proposed fix no longer obscures a real defect. The adjudicator now distinguishes an ineffective remedy from an effective but over-broad one while staying inside the supplied finding and repository-established repair seams.
- Architecture designs, current-state architecture, and decision records can now follow each adopter's own repository or external destinations. Explicit destinations, policy, established conventions, and optional configuration are resolved by semantic role; catalogue paths remain fallback offers.
- Architect stays useful as an independent user pack. It can remain chat-only, save to an exactly confirmed personal workspace, consume Core's repository resolution when compatible, or produce a truthful repository handoff when Core is absent.
- Codex agents with read-only source permissions can read and search local files again. The design reviewer, both desk-research agents, experience reviewer, frontend reviewer, and both discovery reviewers retain Codex's command-backed file access inside a read-only sandbox without gaining write authority.
- Review loops now verify reviewer findings before asking you to repair them. An independent, read-only adjudicator checks each claim against the current target and governing rules. False positives stay in an audit instead of consuming repair rounds, while missing evidence stops for your decision.
- A confirmed product discovery can now hand bounded delivery context to Core intake without losing its source or skipping delivery approvals. One independently shippable feature enters as a delivery contract; multi-spec or cross-repository work enters as a delivery brief. Older or absent Core installations receive the same content as a portable rendered handoff.
- Work-loop reviews now explain readiness without asking you to trust a generic “clean” verdict. Reviewers trace non-local impact and rollout safety when warranted, then hand off an evidence-bearing verdict —
BLOCKED,CHANGES_REQUIRED,READY_WITH_RESIDUAL_RISK, orREADY— so every residual risk is named, not hidden.
- Work-loop reviews now explain readiness without asking you to trust a generic “clean” verdict. Reviewers trace non-local impact and rollout safety when warranted, then hand off an evidence-bearing verdict —
- Core workflows can resolve a semantic destination using each repository's own paths, policy, established conventions, optional configuration, or external locator. Results preserve bounded provenance and independent authority facts, while unsafe local paths and ambiguous evidence fail closed.
- You can migrate a legacy workspace entry through a reviewed, reversible path.
workspace-statusshows the exact retained representation and candidate routes, plans only from a human-authored selection, applies only with fresh repository-authorized confirmation, and records a durable ledger that can restore the old workspace bytes without deleting the canonical artifact. - Starting, deferring, checking, refreshing, and migrating work now follow one documented route. The shared guides distinguish source evidence, canonical artifacts, lifecycle membership, processors, local refresh decisions, and separately confirmed tracker coordination.
- You can migrate a legacy workspace entry through a reviewed, reversible path.
- Installed workspace-status engines now understand reviewed legacy work-intake migrations. The bundled engine recognizes exact legacy workspace slices, validates human-selected target routes and durable migration ledgers, and keeps planning deterministic and non-mutating. Repository status refuses linked or aliased workspace input before projecting legacy bytes, and ledger validation rejects any operation whose immutable material no longer matches its digest.