Repository navigation
Conversation
Preserve the tested 0.1.12 JavaScript experiment independently of the current TypeScript CLI. Add random planner-first startup, all-active-member completion, explicit DONE reopening, and bounded cancellation before exit redistribution. Wire its 40 offline tests into the repository test command and allowlist every new file. Do not change the published package or default runtime behavior. Co-authored-by: Codex <noreply@openai.com>
Normalize Windows paths and line endings in the snapshot integrity manifest. Co-authored-by: Codex <noreply@openai.com>
The api-client filenames cause six fixed SHA-256 entries to match the generic API-key detector; keep all other secret scanning enabled. Co-authored-by: Codex <noreply@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem and behavior
An experimental goal run can stall when a member exits while other agents keep waiting for its output. A member's DONE also needs to be reversible when another member explicitly asks it to revise or verify work.
This PR adds the independently deployed
0.1.12-planner-quorum.3JavaScript experiment underexperiments/planner-quorum-client/, with:@<roster-name> REOPEN <request-id>: <instruction>requests, deduplication, queued delivery, and DONE revocation;completed_degraded, structured recovery events, and unchanged time/token bounds.Repository boundary
This is a standalone experimental snapshot of the deployed 0.1.12 fork, not a port into the current 0.1.16 TypeScript CLI. The production CLI, its version, its dependencies and default behavior are unchanged. The experiment is private and outside the pnpm workspace; invoke its entry explicitly. Keeping it isolated preserves the tested artifact and makes the experiment available for review without replacing newer upstream behavior. A TypeScript integration would be separate work.
The root test command runs the experiment's 40 offline tests, and all new files are explicitly export-allowlisted. Portable runtime hashes and baseline provenance are included; deployment paths, credentials, run records and node_modules are not. Six exact historical checksum fingerprints are excluded from Gitleaks because the api-client filenames caused SHA-256 manifests to match the generic API-key rule; all other scanning remains enabled.
Validation
Passed on Linux (Node 22 experiment image, isolated from credentials):
pnpm check:exportpnpm typecheckpnpm test, including all 40 experiment testspnpm test:package(unchanged production CLI installed-package smoke)gitleaks git . --redact --no-banneron the final branch: no leaksThe experiment's 40 tests also pass on Windows and in a network-disabled Linux container. Windows full upstream tests/package smoke hit existing environment limitations (temporary-directory EPERM and spawn npm ENOENT); Linux checks passed.
Prior deployed Earth_001 runs exercised successful explicit reopening and bounded cancellation/replanning after provider 429 exits. These observations are not service-contract certification and do not establish a benchmark score benefit.
Limits
Forced cancellation may interrupt file writes; existing artifacts must be revalidated. Failed cancellation confirmation blocks further scheduling. The post-check drain is client-side, not a server-atomic close transaction. Natural-language requests outside the explicit REOPEN protocol are not outstanding work items. No npm publication, merge, queue start or server version switch is part of this PR.