Skip to content

Releases

v3.7.5

Choose a tag to compare

@github-actions github-actions released this 16 Nov 21:02

Changed

  • Guards advise instead of refuse. On Pi the adapter runs guards in auto
    mode (or the user's FOUNDATION_GUARDRAIL_MODE): Land and Deliver without
    explicit consent, edits outside a change, shell shapes, and a background
    authority run proceed with a warning on the tool result. In every host,
    an uninstructed main-checkout commit/push during Build or Prove and a
    Deliver outside /deliver run with a warning instead of becoming a
    question; shell-route-guard and no-detached-authority advise unless a
    block mode is set. agent-team starts a worker above the project's
    maxParallelAgents with a warning; maxActiveWorkers still caps.
    Secret redaction is unchanged, and FOUNDATION_GUARDRAIL_MODE=block
    restores every refusal.

Added

  • execution.maxParallelAgents defaults to 64, matching Pi's
    maxActiveWorkers, and accepts 1 to 64; maxParallelProviders and
    maxParallelSetups keep 1 to 16. Existing foundation.json values are
    unchanged.
  • Pi guards background_bash like bash (secrets, phase, shell route,
    Land/Deliver, detached authority) and starts it in the Build workspace;
    authority run through it is refused. Other custom/MCP tools stay outside
    the live boundary but are named once per session while a change phase is
    enforced. Pi now injects the session digest at start and after compaction
    (sessionDigest: live), refuses detached authority run in bash, and
    warns when /dev settles before proof passes.

v3.7.4

Choose a tag to compare

@github-actions github-actions released this 16 Nov 15:27

Added

  • Every scenario of behavior-changing work must name the test file that
    proves it (a testMap row or a test path in its task), and a product task's
    verify must run tests, not only a no-op, lint, format, or typecheck
    command. change start, revise, and amend return one EDIT naming each
    gap. Prove then judges test discrimination per bound test file, so a test
    that passes on the original code cannot hide behind another file that
    fails; regression: true scenarios may pass on base, and a bound file that
    does not exist is a repair.
  • A base-source check with no verdict (timed out or unavailable) is named in
    the Prove outcome and the Land report instead of passing silently, and a
    repository whose product code changed with no test provider is a repair.
  • Land writes verification.md beside the archived proposal: the proof run
    Land accepted and one row per receipt (provider, claims, status, observed
    result, command, duration, receipt SHA-256), advisories, and whether a
    review record exists, so the evidence summary travels with Git. Log paths,
    environment values, and .foundation/ paths are left out, and an
    unreadable receipt is listed as unavailable. Land refuses a packet that
    already contains verification.md; a resumed Land writes the same file
    once and stops on an edited one, keeping it.

Changed

  • Breaking: the CLI is cloop only. Homebrew installs bin/cloop and no
    longer a claude-foundation command; commands, next steps, recovery routes,
    guard messages, Pi, and docs name cloop. init writes the
    .foundation/bin/cloop shim and the Bash(cloop *) and
    Bash(.foundation/bin/cloop *) allowlist rules (earlier rules stay until you
    remove them). Rerun cloop init in projects installed from a source checkout.
    Guards still treat a leftover claude-foundation binary as the same CLI, so
    it is never an unguarded route. The Homebrew formula keeps its name
    (brew upgrade claude-foundation).
  • WORKFLOW.md keeps the lifecycle overview, ownership, the blocking policy,
    and the rules shared by every phase (about 5.7k words, from 21.5k). Each
    phase's full contract moved unchanged to
    .claude/harness/lifecycle/<phase>.md (investigate, change, build,
    prove, land, deliver), which installs with the harness. The phase
    headings in WORKFLOW.md stay, so links such as WORKFLOW.md#land-change
    still open a summary that links on.

Fixed

  • A control root that is not a Git repository but gathers many repositories
    (for example a folder of 821 service checkouts) works without workarounds.
    Change intake scans only the declared repositories (narrowed to the draft's
    selection) instead of exhausting the scan limit on the whole folder. The
    root copy sandbox and its manifests skip every nested Git checkout: a
    declared one has its own sandbox, and Land refuses a file written into an
    undeclared one and asks you to declare it. Copying and hashing those
    checkouts had produced a 17 GB root sandbox and a 115 MB runtime state file
    in one such folder.
  • A Git root that ignores its gathered checkouts, or tracks them as gitlinks,
    also scans the declared repositories' files at change intake.
  • Before a change starts and during Change, the phase guard lets Write and
    Edit create the v5 draft folder (.foundation/drafts/<id>/) and
    openspec/repositories.yaml, so agents no longer fall back to shell writes
    that bypass the guard. Its refusal names the draft folder route.

v3.7.3

Choose a tag to compare

@github-actions github-actions released this 16 Nov 11:44

Added

  • /dev now runs from Investigate (only when the cause or feasibility is
    unknown) through Change, Build, Prove, Land, and Deliver, stopping at
    --through proven|archived|delivered or the request's words ("ทำจนจบ",
    "เปิด PR"). When the target is unstated, the agent asks with the spec
    approval instead of assuming. /dev --through delivered is Deliver
    authority for that /dev run's change only, in Claude Code and Pi.
  • Pi routes plain-language requests into Change Loop. investigate <topic>
    runs /investigate, and short requests such as เปิด PR ให้เลย,
    deliver ได้เลย, or open a PR run /deliver for the session's change,
    as does /deliver without an ID. Questions and refusals are not requests.
  • Pi follows the machine's Change Loop. After brew upgrade, reopening or
    reloading Pi installs the new runtime through the new
    claude-foundation host pi-runtime endpoint; a missing or failing CLI keeps
    the existing runtime and shows a warning. New shared projects follow the
    machine version ("follow": "machine" in .changeloop.json); projects that
    pin a bundle keep it until /changeloop follow (/changeloop pin pins again).
  • Change Loop works in Pi without per-repository setup. In a trusted
    repository without Change Loop settings, the first /change,
    /investigate, /dev, or /feature creates follow-machine settings at the
    project root, reloads Pi, and continues the command. Opening a folder or
    chatting writes nothing; untrusted folders, the home directory, and projects
    with a local installation are refused.

Changed

  • Model-tier routing is on in new installations. The shipped foundation.json
    sets models.routing: true, so Build tasks use the fast, standard, or
    deep tier by kind and risk. Upgrades keep each project's existing value:
    an explicit false is no longer replaced, and a project that never set the
    key gets false, the behavior it already had.

Fixed

  • Several changes can run at once. A copy sandbox no longer claims files it
    copied from another session's uncommitted work and never edited: such a
    file is not part of the change's surface, and sandbox sync fast-forwards it
    instead of reporting a conflict. An edited copy still conflicts.
  • A Land that stops before applying anything returns the session to the
    prove phase, so the main checkout is no longer held under Land rules for the
    12-hour phase window and a user-instructed git commit runs again.
  • change resolve --accept-target-edits is checked per path and bytes: an
    accepted, unchanged blocking path clears the stop even when other sessions'
    dirty files come and go. A later edit to an accepted path is a new question.
  • Pi treats a command as Land only when the Change Loop CLI runs a Land
    subcommand (claude-foundation or foundation.mjs), so git add openspec/changes/archive/... and other commands that mention archive run.
  • Pi natural Land consent also accepts short affirmatives such as land ได้,
    ลง land ได้, and land ได้ครับ; questions and refusals (land ได้ไหม,
    ยังไม่ต้อง land, don't land) still grant nothing.
  • Pi Build shell calls start in the change workspace. Every Pi bash call used
    to start in the project root, so a relative shell write during Build landed
    in the main checkout and Land refused the change. Agent bash calls now start
    in the recorded Build workspace, as Claude Code does after its single cd,
    and the phase guard's shell-mutation warning, previously dropped by the Pi
    adapter, is appended to the tool result.
  • Pi parallel Build workers. A Pi worker session is separate from its
    coordinator, so the phase guard refused every worker write into the change
    workspace. A worker started with FOUNDATION_PARENT_SESSION_ID now resolves
    the coordinating session's phase and may write only inside that workspace.
    Worker sessions refuse /land, /deliver, and natural Land consent.

Internal

  • Behavior-preserving refactors of the largest runtime files: packet
    rendering, amendment record shaping, sandbox setup, and delta-review scope
    now live in their own modules (draft-packet-render.mjs,
    amendment-record.mjs, sandbox-setup.mjs, review-delta-scope.mjs), with
    every moved symbol still exported from its original module.

v3.7.2

Choose a tag to compare

@github-actions github-actions released this 15 Nov 19:58

Added

  • Opt-in merge for Deliver. With deliver.merge: "after-checks" in
    foundation.json, /deliver merges its single-repository pull request after
    every reported check passed, bound to the delivered head commit
    (deliver.mergeMethod: squash default, merge, or rebase), and records
    the merge commit in the delivery receipt. Pending checks return a resumable
    WAIT; failing or missing checks, drafts, and branch protection stop without
    merging; Deliver never uses an admin override. Without the setting Deliver
    still stops at the open pull request.

v3.7.1

Choose a tag to compare

@github-actions github-actions released this 15 Nov 18:54

This is release 3.7.1. Although numbered as a patch by owner decision, it
drops state and commands from before 3.7 and changes 3.7.0 behavior (review
routing, CLI surface); read Changed and Removed before upgrading. A v3.7.0
project upgrades in place.

Added

  • Pi host adapter. cloop init --host pi (or install-pi.sh) installs
    the project-local .pi/extensions/changeloop.ts for Pi >=1.5.2. It registers
    the canonical commands, loads the package-owned agent contract, and bridges
    built-in tool secret/phase guards, lint feedback, session identity, and
    !/!! shell execution. /land <change> grants Land for that change only
    until reload or new user input. Guard coverage is partial: custom/MCP tools
    and other extensions are outside the live boundary, session-digest import is
    unavailable, and no OS sandbox attestation is issued.
  • Shared Pi runtime. cloop init <target> --host pi --shared-runtime keeps
    the runtime, hooks, skills, commands, and OpenSpec schemas in a
    content-addressed bundle under Pi's agent directory. The project holds only
    its .changeloop.json pin, foundation.json, OpenSpec settings and
    artifacts, and .foundation state. A missing or mismatched pin fails closed.
    After the global extension is installed, /changeloop init then /reload
    configures another trusted project. Existing local installations are not
    migrated and remain supported; project settings survive re-initialization.
  • Hotfix regression for its incident. A new hotfix draft must include a
    scenario whose regressionOf equals bugfix.incident.link, in a requirement
    with an executable capability; otherwise change start returns an agent
    EDIT. The change records regressionRequired: true and change revise
    enforces it only for marked changes, so hotfixes created before the upgrade
    are never blocked. The compiled spec shows "Regression of: "; evidence
    claims and protocol pins are unchanged.
  • Project incident records and lessons. Install and upgrade seed
    openspec/incidents/README.md, openspec/incidents/_template.md, and
    openspec/lessons.md only when missing, and never overwrite them.
  • Lessons as grounding. When openspec/lessons.md exists, investigation and
    change intake read it as a grounding source.
  • Advisory project review rules. The AI reviewer packet (review packet schema
    7) now carries the project's REVIEW.md as reviewRules, shown to the
    reviewer as advisory guidance that never changes pass or fail. Review receipts
    record review.reviewRulesHash; editing, deleting, or creating REVIEW.md
    after a review makes it stale (review-rules-changed), while receipts recorded
    before this release stay valid. A missing or empty REVIEW.md keeps the
    previous behavior. Install and upgrade seed a starter REVIEW.md only when
    the project has none, and never overwrite one.
  • test-design skill, vendored unchanged from hashtagf/skills 0.16.0. It
    designs and documents what to verify: test cases, test plans, UAT, coverage
    audits, bug reports, and release go/no-go. testing-fundamentals still owns
    writing automated tests; the router splits the two.

Changed

  • Internal: the advance, change-lifecycle, proof-readiness, and agent-planner
    runtime factories now require the collaborators the composition root always
    supplies and fail at construction naming a missing one; the null guards for
    those impossible states are gone. Never-passed parameters became constants,
    and target-edit and atomic-start rollback logic moved out of foundation.mjs
    into their workflow modules. No output, CLI, or protocol change.
  • Breaking (CLI surface): primitives that advance already performs are
    now internal: proof readiness, proof advance, proof run,
    proof collect, evidence detect, evidence init, evidence doctor, and
    budget checkpoint. They are hidden from help, the default describe
    listing, and the public CLI tables, but still dispatch (and answer
    --help/describe <name>), so existing scripts keep working. Every runtime
    next/resume/recovery route that named one (receipt validity recovery,
    readiness verify/retry choices, wiring actions, waiver output, Build
    completion, verification plans, update advisories, budget and blocker
    recovery, the moved-target Land option) now names
    advance <change> --through proven|archived or advance <change> --inspect.
    The public command golden fixture drops from 76 to 68 commands.
  • The deterministic suite now has two tiers (repository-only). Plain
    .claude/tests/run-all.sh is the fast local gate before commit (about three
    minutes): every suite except the SLOW tier of real-Git end-to-end,
    mutation, installer, and topology suites and the exclusive benchmark.
    --quick is the same gate. New run-all.sh --full runs the complete set
    (the former default); CI runs it as --release on every push and pull
    request, and it must be green before merge or release. --affected still
    selects slow suites whose owned files change.
  • Each harness command asks Git less: repeated git status, git ls-files -s, and git rev-parse HEAD listings of an unchanged workspace within one
    process are answered from a per-process memo instead of a new spawn. The
    memo is forgotten on any file write the process makes into that workspace
    (or into a .git directory), on any child process other than a read-only
    Git query, on a lock wait, and on every clearSnapshotCache. In one
    build→prove→land→sync flow, advance --through proven went from 22 to 10
    Git spawns, Land from 48 to 29, and the whole flow from 134 to 89.
  • Installation copies each managed directory's files in one batch instead of
    forking dirname, mkdir, and cp per file (about 1,450 processes down to
    about 320). A fresh install is roughly twice as fast; the installed tree is
    byte-identical.
  • The deterministic test gate is faster and steadier: one pool worker per core,
    the slowest suites start first, the workload suite runs once (inside the
    sentinel), end-to-end fixtures copy one installed consumer instead of
    reinstalling, and run-all.sh --quick skips only the slowest suites for the
    inner loop. Six test files that no runner named now run in the gate, and a
    registration check keeps new ones from going unrun.
  • run-all.sh clears every host-exported FOUNDATION_* variable and
    CLAUDE_FOUNDATION_PROJECT before running suites, so a run started from an
    agent session (Claude or Pi) tests its fixtures instead of the caller's
    project and guardrail mode. The affected-suite selector also works when the
    checkout sits under a symlinked directory such as macOS /tmp.
  • The default run-all.sh gate no longer runs the release-only openspec native sentinel, which reran the whole workload suite alone after the pool
    (about six minutes). run-all.sh --release runs it with the full gate; the
    release workflow, CI, and --affected for benchmark edits still run it, and
    npm run release:preflight checks that the release workflow uses
    --release. The multi-repository topology contracts and the concurrent
    repositories seam are split into parallel rows and files with every
    assertion kept, so neither holds the tail of the gate.
  • The AI reviewer now checks scope discipline in the changed hunks:
    unrequested abstraction, dead or unused code, speculative options, guards or
    retries that hide a symptom, and untraceable or unrelated edits. These are
    minor findings, major only when they leave a scoped claim false or unproven;
    root-cause fixes and behavior-preserving preparatory refactors are not
    flagged. Packet schema, receipts, and protocol pins are unchanged.
  • ux-ui-principles is now the unchanged upstream hashtagf/skills 0.16.0
    copy instead of the adapted bundle, including its runtime assets/ (about
    13 MB) and scripts/; upstream evals/ is not shipped. Upgrade removes the
    adapted bundle's files, including references/upstream.md and
    references/change-loop-handoff.md. Each vendored skill records its source
    in VENDORED.md.
  • Every non-lifecycle skill now works on its own: guidance that needs
    OpenSpec or Change Loop is a conditional "With OpenSpec/Change Loop …
    otherwise …" section, links to other skills are optional reading, and dead
    references are removed; references and scripts follow the rewritten
    SKILL.md files. Skill descriptions name sharper English and Thai triggers
    and the neighboring skill to use instead. coding-discipline is rewritten:
    fix the root cause where the first wrong state appears, treat a
    behavior-preserving preparatory refactor as its own in-scope slice, record
    unrelated issues as follow-ups instead of fixing them, validate inputs before
    irreversible effects, and verify each outcome on the real artifact. The
    router loads it for a bug fix or Build edit whose scope, assumptions, or diff
    size the always-on digest does not settle.

Removed

  • Breaking: state from releases before 3.7 is no longer read. Finish or
    abandon a change with the release that started it before upgrading.
    • migrate and the .workflow/ reader are gone.
    • evidence upgrade and evidence schema 1 are gone (protocol pin
      evidenceSchema is now ["2"]); an evidence v1 packet is refused with
      that route.
    • The retired commit-based multi-repository Land saga is gone, with its
      land record and land pointers commands. Land always delivers uncommitted
      workspaces; land resume only reports the current plan. A change 3.7.0 or
      earlier left inside that saga is refused instead of replayed: advance
      asks the legacy-land-saga decision (finish it with 3.7.0, then upgrade,
      or change abandon it), naming .foundation/runtime/<change>.json and the
      saga fields; changes, doctor, and the upgrade report name it too.
    • A single-number execution.packetBytes is refused at runtime; the
      ...
Read more

v3.7.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 13:56

Added

  • cloop command. Homebrew installs cloop as the short command next to
    claude-foundation, and the tap resolves brew install cloop. Both names
    run the same program; agents, permission allowlists, runtime routes, and the
    .foundation/bin/claude-foundation shim keep the original name.
  • Principles page and SEO metadata. The docs gain a Principles page (English
    and Thai) naming Proof-Driven Development and seven related principles; the
    landing page gains canonical, social, and structured metadata plus
    robots.txt.

Changed

  • Project home moved to https://github.com/hashtagf/changeloop and the site to
    https://changeloop.ai. The update advisory reads releases from the new
    repository, and the release workflow rewrites the formula's full source URL.
    Installed state paths and file names are unchanged.