Skip to content

AOCI-CODE v0.2.0-rc2

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 17 Nov 18:04
· 70 commits to main since this release

AOCI-CODE v0.2.0-rc2 is built from 51ca8c2286e7a3eff2fcedc22099951d43264494.

The second 0.2.0 candidate: fixes and host-side findings from two weeks of
v0.2.0-rc1 in use, with no new subsystem. Three of the fixes close loops that
cost a Host rounds without end: an Entry for a file named #... that was
written but never read back, a repeated orphan removal that wedged or was
refused, and handed-back commands that only ran from the repository root.
A repository governed by v0.2.0-rc1 needs no migration. One recovery receipt
changed shape: finish an in-flight aoci_remove_entry with this binary before
going back to an older one.

Changes:

  • An orphan that was removed, recreated, and removed again no longer wedges
    the repository. aoci_remove_entry used the object's own hash as the Ledger
    transaction identity, so the second removal wrote its Volume and Baseline,
    then conflicted with the first removal's Ledger event and left a pending
    receipt that no retry could close, blocking every other governance write
    (#176, present since 0.1.x; fix by yunshihang, #177). Each removal now
    records its own identity in a version-2 receipt; version-1 receipts stay
    readable, and an older binary must not be used to recover a version-2 one.
    The batch route had the same collision in another place: a batch of
    removals alone is identified by its paths, so the earlier removal's
    archived receipt answered the later one with a postimage conflict and no
    write, and Maintain kept listing the orphan. Such a batch now gets its own
    receipt and Ledger identity whenever one of its paths carries an Entry
    again. Scenario B6 walks both routes.
  • A file whose name begins with # (#hash.txt, an editor's #draft#) is
    indexed like any other. Its Entry line begins with #, which every reader
    took for a comment while the writer accepted it: the write was reported
    applied, the Entry was never read back, and every Maintain round issued the
    same candidate again and appended one more copy to the Volume, for as long
    as the Host kept running rounds. Present since 0.1.x; reported by the
    aoci-agent project. Inside a directory section a # line is now a comment
    only when it lacks the Entry shape. A Volume already carrying those copies
    reads as aligned after the upgrade (the last copy is the Entry) and the next
    write removes the rest. A batch whose Entry would not read back from the
    Volume it publishes is refused before any write, naming the object.
  • Built with Go 1.26.11, which fixes GO-2026-6859 (an HTTP/1 server crash in
    net/http). In AOCI only the loopback status page serves HTTP.
  • A host dialog that comes back as decline is status=dismissed, not
    rejected: a Host that cannot show the dialog, or times it out, answers
    decline without the person seeing it, and that used to be recorded as the
    person's refusal. Only the form's own Reject choice is a rejection.
  • aoci check concludes "governance aligned" instead of "ready to commit":
    it proves bookkeeping, not what the Entries say. The aligned line of verify,
    check, and status now adds how many index-role sources carry no Entry by
    rule and why, where "369 Entries cover 379 sources" read as ten uncovered.
  • Docs: a .mcp.json example for Claude Code on Windows with the repository
    in WSL.
  • Saving a Baseline whose content did not change leaves the file untouched,
    updated_at included. The timestamp was re-stamped on every save, so two
    branches holding the same managed set conflicted on that one line when
    merged and a scan that found nothing dirtied the tree (#173).
  • aoci init under a custom index_path no longer writes a Legacy skeleton,
    a layout that has been read-only since 0.2.0 and whose only next step was to
    migrate an empty index. It refuses, writes nothing, and names the fix
    (aoci config set index_path aoci.txt).
  • Harness: the upgrade axis retries transient release downloads (#169), and
    ledger_timings.py skips malformed Ledger rows and exits 0 on --help
    (#170, #171, dayebishouji). internal/cognitionbaseline has package tests
    and a real coverage floor; a reflection test keeps every Guide command field
    in the bound list.
  • Overview delivery rules say what a Host must do about a truncated Chunk:
    request each Chunk in its own tool call, and when the Host truncates one,
    request the same cursor once more and check chunk_sha256 before anything
    else. Lowering overview_delivery.chunk_tokens and restarting is left for a
    single Chunk that is truncated twice. The old rule sent every truncation
    there, which does not cure Chunks merged into one script output and walked
    one repository's team setting down to the 4000 floor (50 round trips per
    read). The attestation prompt now spells the four answer keys.
  • Six host-side findings from the v0.2.0-rc1 adaptation (#168): a cognition
    optimization batch delivered again keeps the explicit_object_ref reason
    it was opened with; one repair_required now carries each candidate's
    field token budget overruns beside its form and length findings, as the
    tool description always said; every Maintain and Apply receipt names its
    Volumes with their paths in delivered_volumes, as Overview did; the Host
    capacity verdict is cleared by a later confirmed complete delivery of a
    scope that large, so a reload the Host itself stopped no longer keeps a
    long-lived server session source-bound; the delivery contract names the
    two cursor-failure tokens (overview_snapshot_changed,
    overview_session_unavailable_restart_required).
  • aoci scope rule add accepts repeated --pattern flags before the first
    scan, for --action exclude --pattern-kind directory only: a project that
    defers several modules adds every exclusion in one validated edit instead of
    one command per directory. The rule ID argument prefixes a stable per-directory
    ID, the batch shares the first scan's lock, and an existing Baseline refuses
    it, so scanned repositories keep the Scope Change workflow. The Locale upgrade
    that rewrites team configuration now saves through CAS, so it cannot
    overwrite a concurrent policy edit. (dayebishouji, #167, refs #54)
  • Every command AOCI hands a Host to run names its repository: next_commands
    from Maintain and Apply, the Guide's commands, onboarding's continuation,
    and the exact command an interaction_required answer prints all carry
    --repo <root> beside the absolute binary. A session that starts above or
    beside the repository, as a multi-repository Host session does, used to get
    commands that resolved the wrong tree, or none, when run from its own shell.
  • Overview continuation checks every governed source through the fingerprint
    cache that scan and Maintain already trust, one stat per unchanged file
    instead of one read, and the Safe Inventory it rebuilds takes untracked
    paths from the status listing it already runs, one git process fewer on
    every governance call. Both matter most on Windows, where a 12-Chunk session
    start spent most of its server time rereading sources (#127, #150). A
    same-size rewrite that also restores the mtime is now unseen by the guard
    exactly as governance would miss it.
  • The starter Meta names the neutral section root: one comment line says that
    /<repository> stands for the checkout holding the index, so a reader that
    has only the index file knows where ===/<repository>/docs/=== points.
  • aoci index relocate gives an older index the same shape: it rewrites the
    recorded section roots to /<repository> and adds that Meta line, as one
    receipted transaction over Meta, Code Volume, and Baseline that running the
    command again resumes after a crash. This repository's own index now reads
    that way.
  • init --agent on a clone no longer rewrites the committed Baseline for a
    host configuration Git ignores; init records only what scan would.
  • scope activate --reviewed-by <identity> records the Observe review the
    activation would otherwise refuse on, over the paths the planner names, so a
    merge that changed both the rules and Observe files no longer waits on two
    commands that each wait for the other.
  • Every governance call resolves the commit it binds from the files git keeps
    (a loose or packed ref, a detached HEAD, a linked worktree) and asks git only
    for a shape it does not understand: one process fewer per call.
  • The capability manifest advertises sqlite_schema_evidence and lists
    Migration rollback and Bootstrap rollback among the terminal-only actions the
    interaction contract already reserved.
  • scripts/blackbox/ledger_timings.py takes the index source count from any
    Ledger event that carries one, not only check.
  • docs/getting-started.md says what a teammate does on a repository that
    already has an index, and docs/mongodb-collection-evidence-profile.md
    records the proposed MongoDB collection profile from #135 (#166).

See docs/install.md and docs/supply-chain.md for asset verification.