release: promote dev to main by tomdps · Pull Request #715 · the-open-engine/zeroshot

tomdps · 2026-07-17T18:34:34Z

Summary

Promote the current, dependency-reconciled dev snapshot to main for Zeroshot 6.7.0.

This is the complete release candidate, including the Open Engine Cluster Protocol / strict-native work currently landed on dev and the atomic resume recovery repair from #714 (closing #712 and #713). It is intentionally not a cherry-pick release.

Release candidate

dev SHA: 5dc1639476ea320cae8e8a9ccb45e50104ba0379
current npm release: @the-open-engine/zeroshot@6.6.0
delta from main: 285 commits, 357 files
release title uses the repository's release: minor rule, targeting 6.7.0

Verification

Fresh detached checkout of origin/dev:

focused resume reconstruction regression: 15 passing
npm run lint (0 errors)
npm run typecheck
npm run test:unit (1840 passing, 36 pending)
npm run test:e2e (22 passing)
npm run test:slow (143 passing, 18 pending)
npm run protocol:check
npm run rust:check
opcore check --changed
npm run release:preflight configuration validation passes

The PR and main merge queue must additionally pass check, install-matrix, and release preflight on the synthetic main candidate before merge.

Closes #181

Closes #183 --------- Co-authored-by: Eivind Meyer <eiv.meyer@gmail.com> Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: Eivind Meyer <eivind.meyer@ksat.no> Co-authored-by: Michael Eichelbeck <141341133+mkceichelbeck@users.noreply.github.com> Co-authored-by: Michael Eichelbeck <michael.eichelbeck.ext@wtsde.onmicrosoft.de>

## Summary - add typed command registry + dispatch wiring for TUI slash commands - add CLI compatibility helpers for list/status output - add tests for registry and dispatcher updates ## Testing - npm test (via pre-commit) - npm run lint (warnings only) Fixes #185

## Summary - add reusable start-cluster helper for TUI (text/issue/file) - add TUI service wrapper for starting clusters - add unit tests for helper ## Testing - npm test (via pre-commit) - npm run lint (warnings only) Fixes #187

## Summary - wire Launcher submit to start cluster from text - treat numeric input as plain text - optimistic cluster id + navigate to Cluster view - tests for launcher behavior ## Testing - npm test (via pre-commit) - npm run lint (warnings only) Fixes #189

## Summary - implement /issue command to launch an issue cluster and move to Cluster view - add issue launch wiring + deps in dispatcher/context - add cluster launch helper and tests ## Testing - not run (eslint reports pre-existing issues in repo)

## Summary - exclude generated lib/tui output from linting ## Testing - npm run lint (warnings only) - tsc --noEmit (pre-push)

## Summary - add a cluster log streaming helper that polls the ledger and emits normalized log lines - render live logs with timestamps and agent attribution in Cluster view (bounded to last N lines) - add unit coverage for db path resolution and stream readiness - stabilize /status detection under parallel tests by honoring env home paths and adding a task/cluster fallback ## Testing - `npm test` Closes #194.

## Summary - add a cluster registry helper to read orchestrator cluster summaries - render a selectable Monitor view list with refresh + keyboard navigation - wire Monitor view into app/router and open selected cluster - add unit coverage for cluster sorting and cwd resolution ## Testing - `npx mocha tests/unit/tui-cluster-registry.test.js` Closes #196.

## Summary - add cluster metrics aggregation using pidusage - render CPU/memory columns in Monitor view - extend cluster registry tests for metrics handling ## Testing - npx mocha tests/unit/tui-cluster-registry.test.js Closes #198

## Summary - start TUI in Monitor view when using `zeroshot watch` - keep default Launcher view for `zeroshot tui` ## Testing - NODE_PATH=/Users/tom/code/covibes/external/zeroshot/node_modules /Users/tom/code/covibes/external/zeroshot/node_modules/.bin/mocha tests/cli-rendering.test.js Closes #201

## Summary - add cluster topology model from config (agents + topic wiring) - render topology section in Cluster view (agents + adjacency list) - add unit coverage for topology model parsing ## Testing - NODE_PATH=/Users/tom/code/covibes/external/zeroshot/node_modules /Users/tom/code/covibes/external/zeroshot/node_modules/.bin/tsc -p tsconfig.tui.json - NODE_PATH=/Users/tom/code/covibes/external/zeroshot/node_modules /Users/tom/code/covibes/external/zeroshot/node_modules/.bin/mocha tests/unit/tui-cluster-topology.test.js Closes #203

## Summary - add ledger-backed workflow timeline stream for key topics - render timeline section in Cluster view - add unit coverage for timeline service ## Testing - NODE_PATH=/Users/tom/code/covibes/external/zeroshot/node_modules /Users/tom/code/covibes/external/zeroshot/node_modules/.bin/tsc -p tsconfig.tui.json - NODE_PATH=/Users/tom/code/covibes/external/zeroshot/node_modules /Users/tom/code/covibes/external/zeroshot/node_modules/.bin/mocha tests/unit/tui-cluster-timeline.test.js Closes #205

## Summary - add agent selection in Cluster view with Enter to open Agent view - tail logs for a specific agent using filtered cluster log stream - add agent log filtering coverage ## Testing - NODE_PATH=/Users/tom/code/covibes/external/zeroshot/node_modules /Users/tom/code/covibes/external/zeroshot/node_modules/.bin/tsc -p tsconfig.tui.json - NODE_PATH=/Users/tom/code/covibes/external/zeroshot/node_modules /Users/tom/code/covibes/external/zeroshot/node_modules/.bin/mocha tests/unit/tui-cluster-logs.test.js Closes #207

## Summary - add agent message queue helper utilities - render message input + queued list in Agent view - queue pending messages in app state for Agent view ## Testing - NODE_PATH=/Users/tom/code/covibes/external/zeroshot/node_modules /Users/tom/code/covibes/external/zeroshot/node_modules/.bin/tsc -p tsconfig.tui.json - NODE_PATH=/Users/tom/code/covibes/external/zeroshot/node_modules /Users/tom/code/covibes/external/zeroshot/node_modules/.bin/mocha tests/unit/tui-agent-messages.test.js Closes #209

## Summary - add guidance topics module and ledger mailbox query helper - map target_agent_id to receiver on ledger writes - expose guidance mailbox via message bus and add tests ## Testing - NODE_PATH=/Users/tom/code/covibes/external/zeroshot/node_modules /Users/tom/code/covibes/external/zeroshot/node_modules/.bin/mocha tests/unit/guidance-mailbox.test.js Closes #211

## Summary When Claude CLI returns an error result without actual agent output, the extraction pipeline was falling through to `extractDirectJson` which blindly accepted any JSON object - including raw CLI metadata like: ```json {"type":"result","subtype":"error","duration_ms":1234,"session_id":"abc",...} ``` This caused schema validation to run against the wrong data structure, generating confusing warnings: ``` Agent worker output failed JSON schema validation: #/required must have required property 'summary'; #/required must have required property 'completionStatus' ``` ## Fix Add `isCliMetadata()` check to reject objects that have: - `type:result` (CLI wrapper format) - 2+ CLI-specific metadata fields (duration_ms, session_id, total_cost_usd, etc.) This ensures `parseResultOutput` returns `null` for error cases, triggering proper error handling rather than schema validation against wrong data. ## Test plan - [x] Added unit tests for CLI metadata rejection - [x] Added regression test for error result scenario - [x] All 70 output extraction tests pass Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

## Summary - Add `extractCliError()` for Claude, Codex, Gemini, Opencode error formats - Check CLI errors FIRST before JSON extraction in `parseResultOutput()` - Surface real error messages instead of useless schema validation errors ## Before/After **Before:** ``` Agent worker output failed JSON schema validation: must have required property 'summary' ``` **After:** ``` CLI error (claude): Permission denied for tool Write ``` ## Provider Error Formats | Provider | Error Event Format | |----------|-------------------| | Claude | `{type:"result", is_error:true, errors:[...]}` | | Codex | `{type:"turn.failed", error:{message:...}}` | | Gemini | `{type:"result", success:false, error:...}` | | Opencode | `{type:"session.error", error:{...}}` | ## Test Coverage 14 tests covering all providers, error variants, and edge cases. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude <noreply@anthropic.com>

## Summary - add live guidance injection via attach stdin - persist guidance delivery metadata on guidance messages - add tests for attach stdin + guidance delivery ## Testing - npm test -- tests/unit/attach-stdin.test.js tests/unit/guidance-delivery.test.js - npm run lint - npm run typecheck

Closes #219

Closes #221

Closes #223

Closes #225

## Summary\n- add CLI entrypoints for codex/claude/gemini/opencode that launch the TUI\n- keep invalid-command handling aware of new entrypoints\n- add unit coverage for entrypoint provider overrides\n\n## Testing\n- npm test -- tests/unit/cli-invalid-command.test.js\n- npm test -- tests/unit/cli-tui-entrypoints.test.js\n\nCloses #227

## Summary\n- remove legacy dashboard doc and scrub TUI v2 docs of old blessed/watch references\n- update CLI/docs to describe Ink TUI entrypoints and Monitor view\n- refresh CHANGELOG/AGENTS/CLAUDE/CONTRIBUTING with Ink TUI terminology\n\n## Testing\n- N/A (doc/cleanup)\n\nCloses #229

## Summary\n- add testable helpers for app input handling and monitor list formatting\n- expand command parser coverage and add Esc-back + monitor render unit tests\n- note guidance mailbox status and manual checklist items for Issue 8.4\n\n## Testing\n- npm test -- tests/unit/tui-command-parser.test.js tests/unit/tui-router-esc-back.test.js tests/unit/tui-monitor-list-render.test.js\n\nCloses #231

## Summary Store the issue number from `inputData` in cluster state and expose it in `listClusters()` output. This enables heroshot and other external tools to reliably identify which issue a cluster is working on **without parsing logs**. ## Changes - Store `cluster.issue` when fetching issue from provider - Persist to `clusters.json` alongside `autoPr`, `modelOverride` - Include in `listClusters()` response - Load on cluster resume ## Before/After **Before (fragile):** ```typescript // heroshot parses logs to find issue number const out = runZeroshot(['logs', clusterId, '-n', '200']); const m = out.match(/# GitHub Issue #(\d+)/); ``` **After (reliable):** ```typescript // Direct lookup from cluster state const clusters = JSON.parse(runZeroshot(['list', '--json'])); const issue = clusters.find(c => c.id === clusterId)?.issue; ``` ## Test plan - [x] All 1109 tests pass - [x] TypeScript passes - [x] ESLint passes (warnings only, no new ones) Fixes #233 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude <noreply@anthropic.com>

## Summary Two changes: ### 1. Repo-local settings for GitHub PR and worktree config Add `.zeroshot/settings.json` for per-repository configuration: ```json { "github": { "prBase": "dev", "useMergeQueue": true, "closeIssue": "auto" }, "worktree": { "baseRef": "origin/dev" } } ``` **Features:** - `github.prBase` - Target branch for PRs (default: repo default) - `github.useMergeQueue` - Use GitHub merge queue instead of direct merge - `github.closeIssue` - When to close issue: `auto`/`always`/`never` - `worktree.baseRef` - Base ref for worktree branches (default: HEAD) **Environment variables** override repo settings for one-off runs: - `ZEROSHOT_GH_PR_BASE` - `ZEROSHOT_GH_USE_MERGE_QUEUE` - `ZEROSHOT_GH_CLOSE_ISSUE` ### 2. Fix: fail-safe restart when task not found When `zeroshot status` returns "ID not found", immediately fail with restart error instead of retrying 30 times. **POSTMORTEM:** Agent worker polling failed 30 times when task completed and was cleaned up before worker could detect it. Wasted 30+ seconds. **Fix:** Detect "ID not found" immediately → return error → trigger restart ## Test plan - [x] All 1114 tests pass - [x] TypeScript passes - [x] ESLint passes (warnings only, no new ones) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude <noreply@anthropic.com>

## Summary This PR adds support for GitHub PR configuration via CLI args and repo settings: ### CLI Arguments (New) - `--pr-base <branch>` - Target branch for PRs (default: repo default branch) - `--merge-queue` - Use GitHub merge queue instead of direct merge - `--close-issue <mode>` - When to close issue after merge: auto|always|never ### Repo Settings (.zeroshot/settings.json) ```json { "github": { "prBase": "dev", "useMergeQueue": true, "closeIssue": "auto" } } ``` ### Priority Order CLI args > repo settings > defaults ### Other Changes - Bug fix: "ID not found" now fails immediately instead of retrying 30x - Persists prOptions in cluster state for resume capability - Removed environment variables (ZEROSHOT_GH_PR_BASE, etc.) in favor of CLI args ## Breaking Change Removed env vars ZEROSHOT_GH_PR_BASE, ZEROSHOT_GH_USE_MERGE_QUEUE, ZEROSHOT_GH_CLOSE_ISSUE - use CLI args instead. ## Test Plan - [x] Unit tests pass (1114 passing) - [x] Pre-commit hooks pass - [ ] Manual test: `zeroshot run 123 --ship --pr-base dev --merge-queue` --------- Co-authored-by: Claude <noreply@anthropic.com>

Updates the TUI v2 implementation plan and PRD.

## Summary - add semantic-release config under `package.json#release` - package config is discovered before `.releaserc.json`, so release publishes with npm/GitHub only even if the divergent main/dev merge keeps resolving `.releaserc.json` to the stale branch-writing version ## Why The merge queue repeatedly leaves `main:.releaserc.json` with `@semantic-release/changelog` and `@semantic-release/git`; semantic-release then computes `6.5.0` but fails when `@semantic-release/git` tries to push generated commits to protected `main`. This moves the effective release contract to the first config source semantic-release reads. ## Verification - package release plugin list: `commit-analyzer, release-notes-generator, npm, github` - simulated `git merge-tree origin/main HEAD` preserves `package.json#release` with no changelog/git plugins even though `.releaserc.json` resolves stale Co-authored-by: Eivind <eivindcovibes.ai@Eivinds-MacBook-Pro.local>

## Summary - add a release preflight that validates the effective semantic-release config and release-worthy promotion signal - run the preflight on main promotion PRs/merge queue and in the release workflow - assert after release that npm latest and the git tag both point at the released HEAD ## Verification - node -c scripts/release-preflight.js && node -c scripts/assert-release-published.js - node tests/run-tests.js tests/release-preflight.test.js - npx eslint scripts/release-preflight.js scripts/assert-release-published.js tests/release-preflight.test.js - npx prettier --check .github/workflows/ci.yml .github/workflows/release.yml package.json scripts/release-preflight.js scripts/assert-release-published.js tests/release-preflight.test.js - npm run release:preflight Co-authored-by: Eivind <eivindcovibes.ai@Eivinds-MacBook-Pro.local>

## Summary - merge current main back into dev to repair the divergent squash ancestry - preserve the protected-branch-safe release config; do not reintroduce @semantic-release/git or changelog into the effective release path - keep the new release preflight job from #631 ## Verification - node -c scripts/release-preflight.js && node -c scripts/assert-release-published.js - node tests/run-tests.js tests/release-preflight.test.js - npx prettier --check .github/workflows/ci.yml .releaserc.json package.json scripts/release-preflight.js scripts/assert-release-published.js tests/release-preflight.test.js - commit hook: typecheck passed - push hook: lint warnings only, typecheck passed --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: Eivind Meyer <eivind.meyer@ksat.no> Co-authored-by: Michael Eichelbeck <141341133+mkceichelbeck@users.noreply.github.com> Co-authored-by: tomdps <tom.dupuis24@gmail.com> Co-authored-by: tomdps <60640908+tomdps@users.noreply.github.com> Co-authored-by: Michael Eichelbeck <michael.eichelbeck.ext@wtsde.onmicrosoft.de> Co-authored-by: Ubuntu <ubuntu@ip-172-31-38-53.eu-north-1.compute.internal> Co-authored-by: Eivind <eivind@covibes.ai> Co-authored-by: CI Test <ci-test@covibes.ai> Co-authored-by: Codex <codex@example.com> Co-authored-by: Atharv Singh <132380045+atharvwasthere@users.noreply.github.com> Co-authored-by: Sense_wang <167664334+haosenwang1018@users.noreply.github.com> Co-authored-by: haosenwang1018 <haosenwang1018@users.noreply.github.com> Co-authored-by: Eivind <eivindcovibes.ai@Eivinds-MacBook-Pro.local> Co-authored-by: Zeroshot Agent <agent@covibes.ai>

## Summary - move the release-preflight CI job to the end of the workflow to avoid the old dev/main merge-base conflict hunk - preserve the same release preflight behavior ## Verification - npx prettier --check .github/workflows/ci.yml - commit hook: typecheck passed - local merge test: origin/main merges codex/relocate-release-preflight without conflicts - push hook: lint warnings only, typecheck passed Co-authored-by: Eivind <eivindcovibes.ai@Eivinds-MacBook-Pro.local>

## Summary - make post-release verification use the git tag on HEAD as the expected version - poll npm latest until the registry dist-tag catches up instead of failing on propagation lag - add focused unit coverage for release-tag selection ## Verification - node -c scripts/assert-release-published.js - node tests/run-tests.js tests/assert-release-published.test.js - npx eslint scripts/assert-release-published.js tests/assert-release-published.test.js - npx prettier --check scripts/assert-release-published.js tests/assert-release-published.test.js - commit hook: typecheck passed - push hook: lint warnings only, typecheck passed Co-authored-by: Eivind <eivindcovibes.ai@Eivinds-MacBook-Pro.local>

…#639) Closes #637 Co-authored-by: Eivind <eivindcovibes.ai@Eivinds-MacBook-Pro.local>

## What Reconciles the diverged `main` and `dev` histories by merging `origin/main` into `dev`. Heals the divergence root cause behind #640 and unblocks releasing the `resume --detach` zombie fix (#639, #637). ## Why `main` and `dev` last shared history on 2026-07-09 and could not fast-forward: - `main` carried 6 release/promotion commits (incl. `#591`, `#617`, `#632`) plus the `@semantic-release/changelog` + `@semantic-release/git` plugins in `.releaserc.json` that never flowed back to `dev`. - `dev` carried 59 commits including the `resume --detach` fix (#639). A plain merge hit 4 conflicts. This PR resolves them **without losing anything from either side**. ## Conflict resolution (both sides preserved) | File | Resolution | Rationale | |---|---|---| | `src/orchestrator.js`, `lib/detached-startup.js` | dev | dev's shared `process-liveness` predicate supersedes main's inline pre-fix duplicates. Taking main would **revert #639**. | | `scripts/assert-release-published.js` | dev | dev's `#635` npm-propagation-wait version supersedes main's older `#632` snapshot. | | `tests/e2e/helpers/e2e-harness.js` | dev | dev's `buildEnv` export. | | `.releaserc.json` | main (auto-merge) | main's semantic-release plugins are genuinely main-unique; kept. | **Net delta vs `dev` = 8 lines in `.releaserc.json`, zero deletions vs `dev`** (fix fully intact). All of main's real feature content (`run-plan.js`, `setup-plan.js`, `release-preflight.js`, etc.) was already present on `dev` via prior promotions. ## Verification - `npm install` + build clean. - 34 unit tests green: fix suites (`process-liveness` 3, `detached-startup` 27) **and** main's release tooling (`release-preflight`, `assert-release-published`). - 2 real-daemon e2e cases green: zombie recovery without manual `stop`, and single-daemon win on concurrent `resume --detach`. ## Merge instructions **Merge as a merge commit, NOT squash.** A squash flattens the two parents and leaves `main` un-ancestored, so the branches would immediately re-diverge. The merge commit is what actually reconciles them. Follow-up: adopt the trunk + Changesets pipeline in #640 so this drift cannot recur. --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: Eivind Meyer <eivind.meyer@ksat.no> Co-authored-by: Michael Eichelbeck <141341133+mkceichelbeck@users.noreply.github.com> Co-authored-by: tomdps <tom.dupuis24@gmail.com> Co-authored-by: tomdps <60640908+tomdps@users.noreply.github.com> Co-authored-by: Michael Eichelbeck <michael.eichelbeck.ext@wtsde.onmicrosoft.de> Co-authored-by: Ubuntu <ubuntu@ip-172-31-38-53.eu-north-1.compute.internal> Co-authored-by: Eivind <eivind@covibes.ai> Co-authored-by: CI Test <ci-test@covibes.ai> Co-authored-by: Codex <codex@example.com> Co-authored-by: Atharv Singh <132380045+atharvwasthere@users.noreply.github.com> Co-authored-by: Sense_wang <167664334+haosenwang1018@users.noreply.github.com> Co-authored-by: haosenwang1018 <haosenwang1018@users.noreply.github.com> Co-authored-by: Eivind <eivindcovibes.ai@Eivinds-MacBook-Pro.local> Co-authored-by: Zeroshot Agent <agent@covibes.ai>

…657) Closes #644

… algebra (#659) Closes #645

…ntics (#662) Closes #646

…y, and artifact profiles (#663) Closes #649

…664) Closes #648

… backend seam (#701) Closes #666

…ability (#702) Closes #684

…r contracts (#703) Implements #694. ## What changed - Adds separate bounded `IssueProvider` and `SourceCodeProvider` contracts, registries, identities, capabilities, and evidence types. - Enforces inspect-before-repeat and merge-receipt binding to the requested base/head. - Adds deterministic contract, bounds, architecture, and compile-fail coverage. - Isolates the existing Node unit-test environment so the full repository gate remains reliable. - Documents the new product-private provider boundaries in `AGENTS.md`. ## Validation - `cargo build -p zeroshot-rust --all-targets` - `cargo test -p zeroshot-rust --test provider_contracts` - `cargo test -p zeroshot-rust --test provider_bounds` - `cargo test -p zeroshot-rust --test backend_boundary` - `cargo test -p zeroshot-rust --test architecture` - `cargo test -p zeroshot-rust --doc` - `cargo fmt --all -- --check` - `cargo clippy --workspace --all-targets -- -D warnings` - `cargo test --workspace` - `npm run protocol:check` - `npm run lint` - `npm run test:unit` - `opcore check --changed` Both Zeroshot validation agents approved the final commit.

…705) Closes #699

…d worker (#708) Closes #652

…v1 graph verifier (#706) Closes #667

## Summary - plan resume recovery before starting agents or mutating the ledger - selectively resume missing/interrupted validators and preserve completed validation evidence - recover durable issue context from complete history, with structured no-mutation diagnostics when reconstruction is unsafe - make foreground and detached resume behavior equivalent ## Related Issues Fixes #712 Fixes #713 ## Changes Made - add an internal preflight resume plan with explicit target precedence and registered-vs-eligible handler diagnostics - cross-check lifecycle, persisted execution, iteration, and task ID state before considering work interrupted - clear transient execution state only after a valid plan while preserving worktree and iteration history - prevent snapshot/ledger mutation for impossible recovery and persist registry-only `resume_reconstruction` failure information - add unit and daemon E2E coverage for partial validation, stale context, atomic failure, and foreground/detached parity ## Testing - focused resume tests: 15 passing - state snapshot tests: 7 passing - `npm run lint` (0 errors) - `npm run typecheck` - `npm run test:unit` (1646 passing, 18 pending) - `npm run test:e2e` (22 passing) - `npm run test:slow` (143 passing, 18 pending) - `npm run protocol:check` - `npm run rust:check` - `opcore check --changed` - independent direct-file review: `APPROVED` ## Checklist - [x] Tests pass - [x] Documentation updated (not needed; no public interface change) - [x] Follows commit guidelines

greptile-apps · 2026-07-17T18:34:40Z

Too many files changed for review. (357 files found, 100 file limit)

Bypass the limit by tagging @greptile-apps to review.

# Conflicts: # AGENTS.md # lib/detached-startup.js # lib/start-cluster.js # scripts/assert-release-published.js # src/orchestrator.js # tests/e2e/helpers/e2e-harness.js

…-6-7 chore(release): preserve main ancestry for 6.7 promotion

github-actions · 2026-07-17T21:28:18Z

🎉 This PR is included in version 6.7.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

tomdps and others added 30 commits January 27, 2026 15:45

feat: TUI v2 2.1: Implement view router + Esc back navigation (#182)

853ca08

Closes #181

feat: TUI v2 3.1: start-cluster helper (#188)

d3f4276

## Summary - add reusable start-cluster helper for TUI (text/issue/file) - add TUI service wrapper for starting clusters - add unit tests for helper ## Testing - npm test (via pre-commit) - npm run lint (warnings only) Fixes #187

feat: implement /issue command (#192)

130ff64

## Summary - implement /issue command to launch an issue cluster and move to Cluster view - add issue launch wiring + deps in dispatcher/context - add cluster launch helper and tests ## Testing - not run (eslint reports pre-existing issues in repo)

chore: ignore generated tui output in eslint (#193)

765854b

## Summary - exclude generated lib/tui output from linting ## Testing - npm run lint (warnings only) - tsc --noEmit (pre-push)

Add monitor metrics to TUI monitor view (#200)

736fa5e

## Summary - add cluster metrics aggregation using pidusage - render CPU/memory columns in Monitor view - extend cluster registry tests for metrics handling ## Testing - npx mocha tests/unit/tui-cluster-registry.test.js Closes #198

feat: implement #219 guidance queue fallback (#220)

67fb66b

Closes #219

feat: implement #221 cluster guidance broadcast (#222)

1b1197e

Closes #221

feat: wire TUI guidance messaging (#224)

a52a46c

Closes #223

feat: default to TUI when no args (#226)

c02ba9b

Closes #225

docs(tui-v2): update plan and prd (#239)

ff6cb9d

Updates the TUI v2 implementation plan and PRD.

EivMeyer and others added 19 commits July 11, 2026 14:58

fix: resume --detach runs agents in caller and leaves zombie clusters (…

cca54d4

…#639) Closes #637 Co-authored-by: Eivind <eivindcovibes.ai@Eivinds-MacBook-Pro.local>

feat: feat(cluster-protocol): bootstrap v1 and prove initialize/get (#…

8b21347

…657) Closes #644

feat: feat(cluster-protocol): define the graph AST and decidable type…

620c3ed

… algebra (#659) Closes #645

feat: feat(cluster-protocol): implement plan/apply/get admission sema…

a3d6bd8

…ntics (#662) Closes #646

feat: feat(cluster-protocol): define worker registry, autonomy, polic…

05f8dd1

…y, and artifact profiles (#663) Closes #649

feat: feat(cluster-protocol): add update and stop lifecycle controls (#…

d4a1d94

…664) Closes #648

feat: chore(zeroshot-rust): establish the separate native product and…

c507ac8

… backend seam (#701) Closes #666

feat: feat(zeroshot-rust): add central safe faults and minimal observ…

62a22c3

…ability (#702) Closes #684

feat: feat(zeroshot-rust): add injected ArtifactStore and local CAS (#…

a0a4bcb

…705) Closes #699

feat: feat(legacy-worker): expose current Node Zeroshot as one bounde…

0d7fdcf

…d worker (#708) Closes #652

feat: feat(cluster-protocol): implement the reusable production full-…

e7d7594

…v1 graph verifier (#706) Closes #667

chore(release): sync main into dev for 6.7 promotion

eccce90

# Conflicts: # AGENTS.md # lib/detached-startup.js # lib/start-cluster.js # scripts/assert-release-published.js # src/orchestrator.js # tests/e2e/helpers/e2e-harness.js

tomdps mentioned this pull request Jul 17, 2026

chore(release): preserve main ancestry for 6.7 promotion #716

Merged

Merge pull request #716 from the-open-engine/codex/sync-main-into-dev…

ce84e24

…-6-7 chore(release): preserve main ancestry for 6.7 promotion

tomdps added this pull request to the merge queue Jul 17, 2026

Merged via the queue into main with commit bc35ddd Jul 17, 2026
22 of 23 checks passed

github-actions Bot added the released label Jul 17, 2026

This was referenced Jul 17, 2026

[URGENT BUG] Resume rejects VALIDATION_RESULT despite registered handlers #712

Closed

bug: resume rejects populated stopped cluster with missing workflow triggers #713

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

release: promote dev to main - #715

release: promote dev to main#715
tomdps merged 287 commits into
mainfrom
dev

tomdps commented Jul 17, 2026

Uh oh!

greptile-apps Bot commented Jul 17, 2026 •

edited

Loading

Uh oh!

Uh oh!

github-actions Bot commented Jul 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Conversation

tomdps commented Jul 17, 2026

Summary

Release candidate

Verification

Uh oh!

greptile-apps Bot commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

github-actions Bot commented Jul 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

greptile-apps Bot commented Jul 17, 2026 •

edited

Loading