Skip to content

v3.7.3

Choose a tag to compare

@github-actions github-actions released this 16 Nov 11:44
· 112 commits to main since this release

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.