Skip to content

v3.6.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 15:23
· 76 commits to main since this release
8c9601f

The graph learns your service contracts, and the agent loop leaves receipts.

OpenLore now reads your service contracts — OpenAPI, protobuf, and GraphQL — into the same call
graph as your code, binds handlers and generated clients to the operations they serve and call, and
grades a contract change against its real consumers, including those in sibling repositories. The
agent loop gained receipts that arrive when you can act on them, a session ledger, cross-worktree
coordination, and new verifiable claim kinds. Infrastructure definitions are bound to the code they
run, and onboarding keeps the index current in the background. Everything is additive and behind
existing or opt-in presets; the default tool surface and your configuration are unchanged.

The service-contract graph

  • certify_service_contract grades an OpenAPI 3.x / Swagger 2.0, protobuf (proto3), or GraphQL
    change against the code: two-way parity with the indexed handlers, a closed-table
    breaking/dangerous verdict per changed element, each joined to the in-repo clients it breaks and
    the tests that reach them, and a suggested version bump withheld when compatibility cannot be
    proven. (#639, #659, #687, #688)
  • Declared operations, messages, and named schemas are graph nodes, bound to the handler that
    serves each (implements_endpoint) and the function that calls it (consumes_endpoint), so
    orient, analyze_impact, and get_subgraph cross the API boundary. Matching is literal — an
    ambiguous address binds nothing and says so. (#660, #682, #687, #688)
  • A generated client is bound to the operations it calls by operationId, read from a header
    that names its source spec — never a name match alone. (#680)
  • Consumers in sibling repositories are censused with --federation, so a breaking verdict is
    not read as safe just because this repository has no caller. (#681)
  • orient names the contract of a handler in scope — operation, spec file:line, required
    parameters and body — unasked, and blast_radius briefs a spec-only diff on the elements it
    declares and who serves and consumes them. (#655, #679)
  • A literal request body missing a required property is reported and carried in verify_change.
    (#656, #658)

The agent loop leaves receipts

  • Loop hooks push OpenLore's receipts at the moments a harness offers — after an edit, after a
    compaction, before stopping, at sub-agent start, and before a write — in Claude Code, Codex, and
    Pi. (#637, #649, #650, #651, #652, #654)
  • A session ledger names the symbol that changed under you, tells a background change from your
    own edit, tracks declared operations and resources like code symbols, and counts how the session's
    symbols changed. (#636, #657, #661)
  • Weakened checks, invented references, and hand-edited generated files are reported on a diff —
    deleted or skipped tests and relaxed gates, an import or package that does not exist, an edit a
    regenerate will overwrite. (#629, #632, #634)
  • get_handoff_briefing states the in-flight change so a compaction or a new session does not
    lose it, and lease tokens let any process ask verify_claim whether what it was served still
    holds. (#638, #644)
  • verify_claim gains endpoint-implemented, endpoint-consumed, decision-governed, and
    lease-current
    , and answers unverifiable (naming the disagreement) rather than a confident
    "no". (#642)

Infrastructure bound to the code it runs

  • Function resources are bound to their handlers (deploys_symbol) across Terraform,
    CloudFormation/SAM, and Serverless, and orient names the infrastructure a deployed handler
    depends on
    — the resource that runs it and the sites that set each variable it reads. Serverless
    Framework joins the supported ecosystems (13 in all). (#640, #645, #662)

Coordination across worktrees

  • A shared footprint board across every worktree of a clone shows who is about to write which
    symbols, with hazard-typed conflicts and duplicate-intent detection; peer-change notices fire
    when another agent touches what you read; and plan_parallel_work can plan against the live agents
    on the board. (#641, #646, #647, #648)

Onboarding and the background

  • OpenLore sets itself up and stays current in the background: a cold start builds the index, a
    stale one repairs itself (judged by content, not file mtimes), and the first touch is disclosed
    once rather than read as a broken install. (#630, #631)
  • An OpenSpec propose prompt is grounded in repository structure before drafting, and Claude
    Code gets a color-coded OpenLore status line. (#622, #623)
  • Local semantic vectors build 8–10x faster. (#633)

Breaking and behavior changes

  • Minimum Node.js is now 22.22 (^22.22.0 || >=23.5.0), matching the file watcher's floor
    (chokidar 6); 22.19–22.21 exits with code 78 and asks you to upgrade. (#620)
  • The Pi repository digest is on-demand. The Pi extension no longer appends the architecture
    digest to every turn; call openlore_orient when you have a task, or set
    "pi": { "contextMode": "full" } to restore the previous every-turn injection. (#623)
  • Removed the OpenSpec plugin manifest (plugin-manifest); the host side was never built. (#692)

Fixed

  • A failed command prints one legible line, not a V8 stack trace; install preserves an
    mcpServers.openlore entry it did not write, no longer edits your pre-commit hook, and describes a
    refusal by its cause. (#671, #695)
  • Rust tests are detected from their attributes (#[test], #[tokio::test], …), and orient never
    offers a test function as an insertion point or prescribes a tool the wired preset does not expose.
    (#674)
  • A watcher save no longer drops the projected contract and deploy edges, one unreadable manifest no
    longer erases the whole infrastructure graph, and an infrastructure declaration is never served as
    code (a hub, an entry point, or a term in the fan-in/fan-out averages).
  • Over-budget answers keep a fair share of every list and no longer overwrite a tool's own
    disclosure. (#663)
  • Large composite literals extract in linear time, so a generated .pb.go no longer stalls
    analyze. (#708)
  • analyze's console output is bounded and no longer leaks library warnings. (#700)
  • certify_provenance's in-toto envelope is validated against the Statement v1 shape, with its
    structural-only scope stated plainly. (#707)
  • A Pi daemon left by an older version recovers, and the vocabulary cache is keyed on its content.
    (#621, #653)

The new contract-graph, verification, and coordination capabilities ship behind opt-in presets
(full, verify, coordination, federation); the default tool surface is unchanged. The index
schema version is now 17, so the first run after upgrading rebuilds the graph in the background. The
only compatibility change is the raised Node.js floor noted above.