Repository navigation
Releases
v0.7.1
On the built-in Node coordinator, a strict-mode session whose copy of a file went stale can read the file again after one deny and keep working, the stale-copy deny texts now say so, and an opted-in pre-edit with a malformed subagent id is refused with HTTP 400.
Upgrade note:
- Restart the Node coordinator. A Node coordinator that an earlier plugin started keeps serving its workspace after the update, with the old behavior, until it stops. From the workspace root, check that
ps -p "$(head -n 1 .coherence/server.pid)" -o command=namesdist/coordinator.js, runkill "$(head -n 1 .coherence/server.pid)", then start a new session. - Python-backend workspaces. The recovery and the new deny texts come from
agent-coherencereleases after 0.16.0, which make the same change in the Python coordinator; 0.16.0 and earlier keep denying every Read. Upgrade the library with the plugin. - Deny texts. A script or prompt that matches the strict-mode deny texts byte for byte must accept the new wording (see Changed).
Fixed
- On the built-in Node coordinator, a strict-mode session whose copy of a file went stale can read the file again and keep working (Cohexa-ai/agent-coherence#514). The session's first stale Read or Edit of the file is still denied. Every Read after it was denied too, for the rest of the session, whether a peer had committed, a peer had taken the file and stopped without committing, the session's grant had been reclaimed, or its own subagent had committed; only a Bash read run twice, a new session or a new subagent got the file back. Now the session's next Read of the file is allowed when the bytes it reads are the version the coordinator recorded, or the record holds no content: it is granted that version and answered
{"status": "fresh", "version": <n>}, with any queued notices and no stale warning, and the session's Edits of the file are allowed after it. A commit that lands between the deny and that Read costs no second deny: the Read gets the newer version. AnEditorWritesent before that Read is still denied, so a write built from the old copy does not land. A Read of other bytes, or with no hash because the file is gone, stays denied (see Changed). The session's next allowed Read or Edit of the file uses the recovery up, so the next time the copy goes stale starts from a deny again. A Bash or Grep read that re-grants the file also uses up the record of the deny, so when the session's copy next goes stale, its first Read or Edit of the file is denied again. The hook clients do not change. The Python coordinator does the same inagent-coherencereleases after 0.16.0; 0.16.0 and earlier keep denying every Read. A Node coordinator started by an earlier plugin keeps the old behavior until it restarts. Limits:- the coordinator keeps the record of the deny in memory, so after a restart the session is denied once more before its Read is allowed;
- a Read and a Write sent in one message, or a Read of part of the file, can still let a whole-file write from the old copy through (Cohexa-ai/agent-coherence#624);
- only the Claude Code hooks get the recovery. A pre-read that carries
want_owner_generation,verify_onlyorname_kind, as aCoherentVolume, the MCP server, the substrate adapter, an effect fence's verification read and the raw HTTP capture send, keeps the deny and neither starts nor uses up the recovery; the Node coordinator now readsverify_onlyfor this. ACoherentVolumefromagent-coherence0.16.0 or earlier marks none of its plain reads, so through this coordinator its second read heals a stale copy (Cohexa-ai/agent-coherence#629); use a release after 0.16.0; - the
agent-coherencehook client's opt-in denial of an edit of a strict file another agent holds (echo refuse > .coherence/hook_on_held) stays off by default.
Changed
-
On the built-in Node coordinator, the strict-mode deny texts for a stale copy now say that reading the file again returns the current version (Cohexa-ai/agent-coherence#514). The text for a peer's commit and the text for a revoked grant keep their first sentence, and the rest now reads
Read <path> again with the Read tool: the next Read returns the current version, and edits of <path> are denied until you have read it., where it told the agent to re-read the file and said that retrying the same operation would produce the same denial. Pre-read, pre-edit, pre-bash and pre-grep send these two texts. A stale Read whose bytes are not the recorded version, or that carries no hash, and a Read by a session that never read the file whose bytes differ from the record, now get one of two texts that never promise a Read:Stale read denied: <path> on disk does not match v<n>, the last version committed through the coordinator, and no session committed the change, so it was made outside the coordinator. ..., which keeps the same-denial sentence, or, while another session holds an uncommitted write of the file,Stale read denied: another agent is writing <path> and has not committed it yet, so <path> on disk does not match v<n>, the last version committed through the coordinator. Wait for that write to be committed, then Read <path> again with the Read tool.A session that never read the file got the commit text before, which named the last committer, oragent <unknown>when nobody had committed, as the writer of bytes no session committed. The out-of-band text for a reader that still holds the file is unchanged. Each text is the same bytes for a given file and event, and the Python coordinator sends the same bytes inagent-coherencereleases after 0.16.0. -
On the built-in Node coordinator, a pre-edit that opts in to acquire-or-fail with a malformed subagent id is now refused with
HTTP 400(Cohexa-ai/agent-coherence#519). A pre-edit that sends"if_unheld": trueasks whether the caller's own agent identity may take the file. When itsagent_idwas present but not 1 to 64 characters of[A-Za-z0-9_-], such as"bad id!", a 65-character string, a number or a list, the Node coordinator read it as the parent session and answered for the parent, so a subagent whose parent held the file was admitted as the parent's own repeat. Now such a request answersHTTP 400with{"error": "agent_id must be 1-64 chars of [A-Za-z0-9_-]"}, the wording the Python coordinator uses for the same fault, and changes nothing. The check runs before the tracked-path check, so an untracked path answers the same. An empty ornullagent_idstill means no subagent id, a well-formed one, including aCoherentVolume's 32-hex attempt id, is unchanged, and a pre-edit that does not opt in still reads a malformed id as the parent. The plugin's own hooks do not sendif_unheld. -
The plugin and marketplace manifests name a contact email, and the plugin ships a listing icon,
.claude-plugin/icon.png(#276).claude plugin validatewarned that no icon was present. Nothing changes at run time.
v0.7.0
On the built-in Node coordinator, a workspace now runs one coordinator, at the repository root, that stops once no client can reach it; a session keeps a read of each file it releases, so it can edit that file again on its next turn; every spelling a disk treats as one file reaches one record; an opted-in pre-edit is refused while another agent holds the file; and /status serves the operator view, so a CoherentVolume with managed globs attaches. On either backend, a session start refuses a .coherence that is or holds a symlink and tells the model, and the plugin's hook client and commands send nothing to a coordinator that has exited. Each entry names the agent-coherence release that brings a change to a Python-backend workspace.
Upgrade note:
- Restart the Node coordinator. A Node coordinator that plugin 0.6.0 or earlier started keeps serving its workspace after the update, and new sessions join it, so none of the Node coordinator changes below apply until it stops, and it does not stop by itself. From the workspace root, check that
ps -p "$(head -n 1 .coherence/server.pid)" -o command=namesdist/coordinator.js, runkill "$(head -n 1 .coherence/server.pid)", then start a new session. Do the same with the.coherence/server.pidof any subdirectory or linked worktree an earlier session started a coordinator in (see Fixed). - Links in
.coherence. A session start now refuses a workspace whose.coherenceis a symlink, or holds a symlink, a FIFO, a socket or a device directly inside it, on either backend, and the Node coordinator refuses one too (see Fixed). On the Node backend these links worked before and stop working now:.coherenceitself;state.dband its-waland-shm;hook.secret;strict_mode.yaml;coordinator_backend;tracked.yaml, which worked only until the first track replaced the link with a regular file; andignored.yaml, likewise until the first untrack. On a Python-backend workspace the session start refuses any such link as well, whicheveragent-coherencerelease is installed, with one exception: a.coherencethe session start cannot list, such as one an archive unpacks without read permission, passes for the coordinator to decide.agent-coherence0.15.0 then makes it listable and reads and writes through any link inside it. Releases after 0.15.0 make it listable and refuse it. To keep the state on another disk, mount a directory at.coherence. Otherwise replace each link with a copy of the file it names, and movestate.dbtogether with its-waland-shm: a copy ofstate.dbalone loses its history without a message. Do this with no coordinator running for the workspace, stopping any as above: one an earlier release started through a link goes on writing where the link pointed while your copy falls behind. - Policy patterns. On the Node coordinator a pattern without
**intracked.yaml,ignored.yamlorstrict_mode.yamlnow matches as on the Python coordinator and may reach more files: a tracked*.mdnow tracks every.mdfile in the workspace (see Changed). Anignored.yamlentry no longer takes a strict path out of strict mode, and an untrack that covers a strict path is refused (exit 3): a workspace that switched strict mode off for a path that way finds it enforced again (see Fixed). server.pidandserver.port. A Node coordinator that stops now leaves.coherence/server.pidholding only its pid line, where it deleted the file before, unless it ran without its lock. Do not delete the file yourself. A script that took the file's presence to mean a coordinator runs should look for the port on its second line, and a script that read.coherence/server.portshould read that line too: the Node coordinator no longer writesserver.port(see Changed). Aserver.pidwritten by hand for a process that holds no lock and has nobackend=nodeline no longer counts as a running coordinator, and the status, track and untrack commands exit 2 when the coordinatorserver.pidnames has exited. A Node coordinator now stops within 5 seconds once itsserver.pidis gone or rewritten, for example when you delete.coherence, and nothing starts another until the next session start, resume,/clearor compaction.- Links in tool paths. A Read, Edit or Write through a link that points outside the workspace, or does not resolve, is no longer coordinated, and one through a link inside the workspace is coordinated under the path of the file the link names, so a pattern written against the link's path no longer matches it (see Changed). This is in the plugin's Node hook client, which the hooks run on either backend once a Node-backend session has built it on this machine.
- Noticeable without action (see each entry):
- In strict mode a session that holds a file for writing is now denied a read of it after a change made outside the coordinator.
- A session keeps SHARED on files it released, so
/agent-coherence:statuslists it there. A session already denied its own file stays denied until it re-reads with a Bash command or a new session starts. - On a disk that folds names, the first start merges records an older build split for one file, and an agent that lost its write grant there must read the file again before it commits.
/statusgainspre_edit_if_unheld,fold_profile,fold_table_unicodeandpolicy_summary.strict_mode_pattern_count, counts a broken policy file as one rejected entry, and answers?detail=fullwith 403 or the operator view instead of 501.- A store failure on a hook route answers HTTP 200
{"ok": false, "reason": "internal: <ErrorType>"}where some routes answered HTTP 500.
Backend scope: unless an entry says otherwise, a coordinator change below is in the plugin's built-in Node coordinator. A workspace the Python coordinator serves gets its coordinator behavior from the agent-coherence library, whichever plugin version is installed: where an entry says the Python coordinator does the same in agent-coherence releases after 0.15.0, 0.15.0 and earlier keep the old behavior. The session start's .coherence check runs on either backend, and so does the plugin's Node hook client wherever it is installed.
Added
-
On the built-in Node coordinator, a pre-edit that opts in to acquire-or-fail is now refused while another agent holds the file, as on the Python coordinator in
agent-coherencereleases after 0.15.0 (Cohexa-ai/agent-coherence#246). A pre-edit that sends"if_unheld": trueasks for the file only if no other agent holds it. The Node coordinator ignored the field and answered as for any pre-edit: it took the file from its holder, queued the holder a notice and admitted the caller with a collision warning. Now, on a tracked path another agent holds EXCLUSIVE or MODIFIED, it answers{"ok": false, "reason": "other_holder", "holder_agent_id": "<32 lowercase hex>"}, keys in that order, and changes nothing: the holder keeps its grant, and the caller keeps its queued notices. Any agent identity other than the caller's own counts as another agent, so sibling subagents refuse each other, and so do a parent and its subagent; the caller's own repeat is admitted, and a SHARED reader is not a holder. The holder check and the grant run in one SQLite transaction, so no other grant can land between them. An opted-in admit never carries a collision warning. The plugin's own hooks do not send the field. Only a JSONtrueopts in:- a pre-edit that sends no
if_unheld, or any other value, answers exactly as before, unless it delivers a reclaim notice (below), and still takes the file from any holder, including one that opted in; - on an untracked path, or a held path untracked afterwards, an opted-in pre-edit is admitted with
{"ok": true}unchecked, and a stale strict-mode editor still gets the strict deny first; - the request needs no caller principal, because the Node coordinator issues none, so a caller that sends the holder's own session id is admitted as the holder's repeat; the Python coordinator in
agent-coherencereleases after 0.15.0 answersHTTP 400to an opted-in request without a principal; - when
.coherence/state.dbis busy before the grant, the answer stays{"ok": false, "reason": "internal: SqliteError"}and nothing is granted; when only the delivery of the caller's queued notices after the grant finds it busy, the request is admitted without them and they stay queued.
An opted-in pre-edit also reclaims a grant another agent has held for 30 minutes or more, counted from that agent's first grant in its continuous hold, even if that agent is still working. The Python coordinator's background sweep reclaims such a grant; the Node coordinator has no sweep, so the opted-in request does. The holder's grant is revoked, the caller is admitted,
coordinator.logrecords oneagent-coherence: reclaimed artifact=…line, and the holder's next admitted Read, Edit, Write, Bash or Grep, or its re-grounding after compaction, tells it the grant was reclaimed after being held 30 minutes or more while another agent asked for it, and to read the file again before editing it. The 30 minutes are fixed. Without the reclaim, one crashed or interrupted session could keep a file from opted-in callers indefinitely. The reclaimed holder's next commit of the file is refused withcommit_not_allowed. The Python coordinator's refusal starts the same way and also carriesreclaimed: true(agent-coherence0.15.0). The README's Known limitations list what the check does not cover. - a pre-edit that sends no
Changed
- **On the built-in Node coordinator,
/statusserves the operator view and advertises the acquire-or-fail refusal, so aCoherentVolumewithmanagedglobs attaches, and a fresh read carries its version (#249)...
v0.6.0
On the built-in Node coordinator, strict mode no longer lets a session write a file it was just refused a read of, /status and hook messages stop publishing raw session ids and your absolute workspace path, and tracking a * glob can no longer empty a policy file; a Python-backend workspace gets these from agent-coherence releases after 0.14.1. The track and untrack commands escape what the coordinator sends and say why it refused a request, the status, track and untrack commands report refusals by exit code, and the hook client is ready for the caller principal that agent-coherence releases after 0.14.1 issue.
Upgrade note: on the Node backend, GET /status now reports every session's agent_name as null; key on agent_id instead. agent-coherence-untrack now exits 3 when a Python coordinator from a release after 0.14.1 refuses to untrack a strict path, and agent-coherence-status exits 2 when the coordinator's registry is busy; scripts that read these exit codes may need updating. On the Node backend, and on the Python backend with agent-coherence releases after 0.14.1, hook texts that name a peer by id now say agent where they said session (see Changed), so a script or test that matches them literally needs updating. The Node coordinator, and the Python coordinator in agent-coherence releases after 0.14.1, now refuse a track or untrack with HTTP 400 (exit 2) when the policy file is one an earlier unquoted write broke or is not a plain list. Plugin releases 0.3.0 to 0.5.0 (Node backend) wrote, and agent-coherence 0.8.0 through 0.14.1 (Python backend) write, a pattern that starts with * unquoted, which makes the whole file load as no entries: check .coherence/tracked.yaml and ignored.yaml and quote any such entry (- "*.md"). On a Python-backend workspace, agent-coherence 0.14.1 and earlier keep writing such entries, so check again after each track or untrack until you upgrade the library past 0.14.1.
Backend scope: unless an entry says otherwise, a coordinator change below is in the plugin's built-in Node coordinator. A workspace the Python coordinator serves gets its coordinator behavior from the agent-coherence library, whichever plugin version is installed: where an entry says the Python coordinator does the same in agent-coherence releases after 0.14.1, 0.14.1 and earlier keep the old behavior.
Added
- On a Python-backend workspace the hook client now claims a caller principal and sends it with every hook, so a coordinator that issues principals (
agent-coherencereleases after 0.14.1) can refuse a request for that session from a client that never claimed it. In those releases the Python coordinator binds a caller principal to a session the first time a client claims it (POST /principal/claim). From then on it refuses a request naming that session without the principal on the routes where an unbound caller could do harm (pre-edit, post-edit and session-stop among them), and refuses a wrong principal on every route. The plugin's Node hook client now takes part. On a session's first hook it writes a random claim nonce to.coherence/caller-principal-<agent id>.nonce, claims the principal with it, stores the principal beside it in a.principalfile (both mode0600), and sends it on every later hook in aCoherence-Caller-Principalheader. The file names and formats are the Python hook client's, so both clients share one binding per session. Neither file is removed automatically. The coordinator may refuse the principal, for example after losing its bindings becausestate.dbwas removed or restored, or because a claim's answer never arrived. The client then claims again with the same stored nonce, stores what comes back and retries the refused hook once. It never makes a new nonce, so it cannot take over a session another client has claimed. If an interrupted write (a killed client, a full disk) leaves the nonce file empty or incomplete for more than 2 seconds, the client does not overwrite it: it names the file on stderr, and the session runs without a principal until you remove that file by hand while no hook of the session is running. A hook it cannot recover fails open with{}and says why on stderr, and nothing it prints contains the principal, the nonce or the coordinator's own error text. This is not a boundary between local processes: anything running as your OS user can read.coherence/. The Node coordinator issues no principals and ignores the header. The client readsbackend=nodefromserver.pidand does not claim, so a Node workspace sends exactly the requests it did before. Againstagent-coherence0.14.1 or earlier, which has no claim route, the client still writes the nonce file, and each hook makes one extra local request that the coordinator answers with 404, then proceeds without the header.
Changed
-
/statusno longer publishes a raw session identifier. Each session row carriedagent_nameasclaude-session-<session id>, beside the non-reversibleagent_id. The Node coordinator serves nodetail=fulltier, so the default tier, which rendered it, is the only tier that lists sessions;agent_nameis nownull, andagent_idand the per-artifact states are unchanged. Inagent-coherencereleases after 0.14.1, the Python coordinator redacts the same field below its operator tier, so with those releases both backends returnnullforagent_namebelow the operator tier; 0.14.1 and earlier still publish it on the Python coordinator's default tier. -
A hook response names a peer by agent id, and a denial or warning no longer reports a write that did not happen. The last-writer field on stale responses and strict denies carried a peer's raw session id (a subagent's raw id, for a subagent writer), reversed out of the agent id by a lookup that has been removed rather than left unused. The texts that name a peer now say
agentwhere they saidsession: the strict-mode deny readswas updated by agent <id>, the stale-read warningupdated by agent <id>, the edit-collision warninganother agent (<id>)and each preemption bulletpreempted by agent <id>. When a peer merely took the grant, a denial claimed the artifact "was updated", naming a timestamp for a write that never occurred, and the warn-mode stale-read warning made the same claim. Both now have their own message: the grant was revoked, no new version was committed, and the file is still at the version the session last saw. The deny texts, the stale-read warnings and the edit-collision warning are byte-identical to the Python coordinator's inagent-coherencereleases after 0.14.1; the preemption bullets sayagentthere too, but each backend words them differently. 0.14.1 and earlier keep thesessionwording. -
agent-coherence-trackand-untracknow say why the coordinator refused a request. A non-2xx answer printsHTTP <status>: <error>, orHTTP <status>when the answer carries no error text, the form the Python console scripts use; a 2xx answer that is not JSON printscoordinator returned a non-JSON response. Both used to printcoordinator rejected the request, and both still exit 2. The one exception is the strict-path refusal described under Fixed, whichagent-coherence-untrackreports in its own lines and exits 3. -
The Node coordinator's
uuiddependency is updated from 14.0.1 to 14.0.2. The first session after the upgrade installs it together with js-yaml 4.3.2 (see Security).
Fixed
-
A warning that cannot name the other agent no longer prints a broken
<unknownplaceholder. The stale-read warning, the edit-collision warning and the preemption-notice bullets shortened every identity to eight characters, the<unknown>placeholder included, so it reached the model with its closing bracket cut off:another session (<unknown) has been editing docs/plan.md. In 0.5.0 this happened after every coordinator restart, because those texts printed a session id from a lookup that starts empty in each coordinator process. They now name the peer by agent id, which is stored with the artifact and survives a restart (see the agent-id entry under Changed). The placeholder, still used when no writer is on record, is printed whole, as strict-mode denials already did. The Python coordinator makes the same change inagent-coherencereleases after 0.14.1; with 0.14.1 and earlier, a Python-backend workspace still prints<unknown. -
Stale-read warnings and strict denies now use the version the session actually last read. They inferred it as the current version minus one. After two commits by a peer (v1 to v3), a warning's "you previously saw vN" named v2, a version the session never saw; when a peer only took the grant, the guess made an unchanged file look changed, which is what produced the false "was updated" texts described under Changed. They now use the version recorded when the session last read the file, and fall back to the old guess only when no read is on record: a grant recorded by plugin 0.4.0 or earlier, or a first grant that came from a denied Bash or Grep command. The Python coordinator does the same in
agent-coherencereleases after 0.14.1. -
/agent-coherence:statusno longer asks for the operator view when it falls back to the Python console script. The command ranagent-coherence-statuswith no arguments. The shim runs the plugin's Node CLI, which asks for the default tier, but with nonodeor no builtdist/cli_status.js(a Python-backend marketplace install, for one) it runs the library's console script, whose default inagent-coherence0.14.1 and earlier is the operator tier, requested with theCoherence-Local-Operator: trueheader; that path printed every session's name, which embeds the raw session id, into the transcript. The command now runsagent-coherence-status --detail minimal, which everyagent-coherencerelease from 0...
v0.5.0
What's Changed
- chore: merge manifest version-sync guard into dev by @hipvlady in #98
- docs(release): restore docs/RELEASE.md as a tracked operator runbook by @hipvlady in #100
- fix(install): gate Node backend on prebuilt better-sqlite3 ABIs by @hipvlady in #103
- fix(coordinator): read version from package.json, not drifted constant by @hipvlady in #99
- chore(ci): auto-approve and auto-merge safe dependabot bumps by @hipvlady in #105
- fix(release): fail preflight on required-status-context drift vs ci.yml by @hipvlady in #104
- fix(release): pin release workflow to a supported Node major by @hipvlady in #106
- chore(release): bump to v0.4.0 by @hipvlady in #107
- chore: forward-merge main into dev (js-yaml + brace-expansion bumps) by @hipvlady in #109
- docs(release): replace unworkable rebase merge with admin merge commit by @hipvlady in #110
- fix(ci): dependabot auto-merge failed on approval and merge method by @hipvlady in #111
- chore(actions)(deps): bump actions/checkout from 7.0.0 to 7.0.1 by @dependabot[bot] in #89
- chore(deps)(deps-dev): bump @typescript-eslint/eslint-plugin from 8.63.0 to 8.67.0 by @dependabot[bot] in #92
- chore(deps)(deps-dev): bump prettier from 3.9.5 to 3.9.6 by @dependabot[bot] in #90
- chore: reconcile dev with main after the squash-merged v0.4.0 release by @hipvlady in #112
- docs(release): document the protect-main ruleset and its merge-method trap by @hipvlady in #113
- fix(bootstrap): key provisioning on the Node ABI, not just package.json by @hipvlady in #114
- feat(release): fail preflight on a release-blocking branch ruleset by @hipvlady in #121
- feat(hooks): SB-10 compaction-aware re-grounding (Node half) by @hipvlady in #122
- chore(release): v0.5.0 — compaction-aware re-grounding, release-preflight ruleset check, provisioning hardening by @hipvlady in #123
- fix(release): treat a redacted bypass_actors field as unverifiable, not absent by @hipvlady in #124
Full Changelog: v0.4.0...v0.5.0
v0.4.0
What's Changed
- chore(deps): bump js-yaml to 4.3.1 and brace-expansion to 5.0.9 by @hipvlady in #102
- release: v0.4.0 by @hipvlady in #108
Full Changelog: v0.3.1...v0.4.0
v0.3.1
What's Changed
- feat(dispatch): default fresh workspaces to the Node backend (SB-2 Phase 1, option x) by @hipvlady in #94
- release: v0.3.1 — fix silently-ignored CLI flags + documentation accuracy by @hipvlady in #95
Full Changelog: v0.3.0...v0.3.1
v0.3.0
What's Changed
- chore(actions)(deps): bump actions/setup-node from 4 to 6 by @dependabot[bot] in #34
- chore(actions)(deps): bump actions/download-artifact from 4 to 8 by @dependabot[bot] in #35
- chore(actions)(deps): bump actions/checkout from 4 to 6 by @dependabot[bot] in #36
- chore(deps)(deps-dev): bump @types/node from 25.9.0 to 25.9.1 by @dependabot[bot] in #37
- chore(deps)(deps-dev): bump eslint from 9.39.4 to 10.4.0 by @dependabot[bot] in #39
- chore(deps)(deps-dev): bump @typescript-eslint/eslint-plugin from 8.59.4 to 8.60.0 by @dependabot[bot] in #38
- docs(demos): strict-mode permissionDecision:"deny" screenshot script by @hipvlady in #32
- docs(readme): fix library version references from v0.9.0 to v0.8.0 by @hipvlady in #45
- fix: README console-script accuracy + marketplace version sync by @hipvlady in #54
- chore(actions)(deps): bump softprops/action-gh-release from 2 to 3 by @dependabot[bot] in #46
- chore(actions)(deps): bump actions/upload-artifact from 4 to 7 by @dependabot[bot] in #47
- chore(deps)(deps): bump js-yaml from 4.1.1 to 4.2.0 by @dependabot[bot] in #52
- chore(deps)(deps-dev): bump @typescript-eslint/parser from 8.60.0 to 8.60.1 by @dependabot[bot] in #51
- chore(deps)(deps): bump @types/uuid from 10.0.0 to 11.0.0 by @dependabot[bot] in #49
- chore(deps)(deps-dev): bump eslint from 10.4.0 to 10.5.0 by @dependabot[bot] in #50
- chore(deps)(deps-dev): bump @typescript-eslint/eslint-plugin from 8.60.0 to 8.61.0 by @dependabot[bot] in #48
- fix(migrations): fail closed on a foreign Python-ledger state.db (#55) by @hipvlady in #56
- chore(actions)(deps): bump actions/checkout from 6 to 7 by @dependabot[bot] in #60
- chore(deps)(deps): bump better-sqlite3 from 12.10.0 to 12.11.1 by @dependabot[bot] in #63
- chore(deps)(deps-dev): bump @types/node from 25.9.1 to 26.1.1 by @dependabot[bot] in #65
- chore(deps)(deps-dev): bump prettier from 3.8.3 to 3.9.5 by @dependabot[bot] in #66
- chore(deps)(deps-dev): bump @typescript-eslint/eslint-plugin from 8.61.0 to 8.63.0 by @dependabot[bot] in #67
- chore: point repo references at the Cohexa-ai org by @hipvlady in #69
- feat: Node coordinator self-sufficiency + subagent identity (hook/CLI/strict parity without Python) by @hipvlady in #77
- docs: post-merge README refresh (zero-Python install, subagent identity, R6 confirmation) by @hipvlady in #78
- chore: converge dev into main (single trunk) + lint-clean the newer toolchain by @hipvlady in #79
- chore: record dev lineage in main (no-op merge; fixes #79's missing second parent) by @hipvlady in #80
- chore(deps): take the safe bumps + point Dependabot at the default branch by @hipvlady in #81
- chore(actions)(deps): bump actions/checkout from 4.3.1 to 7.0.0 by @dependabot[bot] in #83
- chore(actions)(deps): bump actions/setup-node from 4.4.0 to 7.0.0 by @dependabot[bot] in #82
- fix(marketplace): point owner/author URLs at the canonical /plugin/ landing page by @hipvlady in #84
- chore(release): v0.3.0 by @hipvlady in #88
New Contributors
- @dependabot[bot] made their first contribution in #34
Full Changelog: v0.2.2...v0.3.0
v0.2.2
What's Changed
Full Changelog: v0.2.1...v0.2.2
v0.2.1
What's Changed
- docs(license): add Apache-2.0 LICENSE file (back manifest claims) by @hipvlady in #30
- docs(license): back-port Apache-2.0 LICENSE from main → dev by @hipvlady in #31
- fix(bin): ship PATH-resolver shims for operator-facing console scripts (Bug 10) by @hipvlady in #43
- docs(readme): allowlist troubleshooting for plugin permission prompts (Bug 8 workaround) by @hipvlady in #42
- release: v0.2.1 — Phase E patch (bin/ shims + permissions troubleshooting + LICENSE backfill) by @hipvlady in #44
Full Changelog: v0.2.0...v0.2.1
v0.2.0
What's Changed
- docs(readme): depth-parity overhaul matching EveryInc reference shape (v0.2 Unit 8) by @hipvlady in #24
- docs: broad-beta launch gating package (v0.2 Unit 9) by @hipvlady in #25
- docs: public-feedback intake hardening (v0.2 Unit 10) by @hipvlady in #26
- docs: v0.2.0 broad-beta launch announcement (single source of truth) by @hipvlady in #28
- docs(changelog): finalize [0.2.0] date as 2026-05-24 (BB7) by @hipvlady in #29
- release: v0.2.0 (broad-beta — DO NOT MERGE until BB1-BB8 green) by @hipvlady in #27
Full Changelog: v0.1.1...v0.2.0