Repository navigation
/sync-gbrain reports failed pushes and imports instead of OK, and one bad queued path no longer blocks artifacts sync - #4455
Merged
Conversation
…ne malformed queued path no longer stops artifacts sync (#4445, #4418, #4417) An empty project slug queued projects//timeline.jsonl and the refused batch blocked every later record; enqueue now refuses such paths and the drain drops and reports them. A failed push stays push_failed until a push succeeds, and the brain-sync row reads the drain's status instead of its exit code. The memory row reads the ingest's failure counts instead of its exit code. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
|
😎 This pull request was merged. |
…, and report malformed-path drops only once they are dropped Review-Finding: p1/red-team#1 reader=red-team Review-Finding: p1/red-team#2 reader=red-team Review-Finding: p1/specialist-batched#1 reader=testing Review-Finding: p1/specialist-batched#2 reader=testing Review-Finding: p1/specialist-batched#3 reader=testing Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…th drops in the sync error guide Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This was referenced Nov 17, 2026
capy-ai Bot
added a commit
that referenced
this pull request
Nov 18, 2026
- A test, or a scratch repository in the temp directory, can no longer write approval rows into your real Capy Drive (GST-3027). (#4466) - An unattended /autoplan run on Claude Code no longer says the publication guard is off while it is on. (#4481) - A phase report written only in reasoning now gets a denial that says so and names the fix. (#4481) - `gstack-autoplan revise` no longer refuses a plan that the first `next` accepted. (#4470) - `revise --plan` with a different file now says the run follows that file. (#4470) - A second-model plan review in `/autoplan` is no longer reported as unavailable when it actually ran (GST-3051). (#4471) - The /ship conductor trial plan now lets case reverts that conflict with later code be resolved by hand in docs, tests and the planted file, so large pull requests can be cases (GST-3003). (#4460) - A locked plan for a trial of /ship without its separate conductor subagent (GST-3003). (#4456) - A driven /ship now runs each phase as one command, counts its calls, and stops itself at 100 minutes. (#4451) - /ship stops asking owners to clear two kinds of bookkeeping noise: base-side merge text and a reviewer's confirmation prose. (#4458) - A base merge that only touched base-side text no longer stops `/ship` finish for an owner's grant. (#4458) - A reviewer's confirmation prose no longer becomes a Critical finding that only an owner can clear. (#4458) - A CI run that passed only after its failed jobs were re-run is now marked wherever gstack reuses it. (#4473) - /ship reuses CI's passing test run when merging the base changed no file, and stops instead of quietly starting hour-long test runs or reviewing an empty diff (GST-3019). (#4461) - /ship on Codex no longer stops at the test coverage audit. (#4489) - A cold first-use check before an app build reaches its owner (GST-3025). (#4465) - `skill_prefix=true` now survives updates when gbrain is installed. (#4454) - The OpenClaw docs no longer send you to ClawHub, which held only April 2026 builds of office-hours, ceo-review and retro and no longer has gstack skills (the docs also said four skills while listing three). (#4454) - `gstack-issue-links` no longer reads other repositories' issues as gstack's. (#4454) - /ship's pre-gate finds the tests of a monorepo app that imports through its own `@/` alias. (#4464) - /office-hours explains why it recommends a mode. (#4450) - /office-hours keeps its 34 founder videos and essays out of the skill file. (#4463) - Two `gstack-owner-answers add` runs for the same answer no longer collide. (#4490) - A Captain can check an ask against the owner's earlier answers before sending it. (#4467) - `gstack-post` stops reading /ship's own receipt identifiers as phone numbers, so posting a /ship PR body no longer needs a confirm. (#4488) - GitHub release notes now list every change in plain words, with a link to its pull request. (#4390) - gstack's router no longer gives bug reports a special rule, so the model fixes a bug the way it would without gstack. (#4442) - /ship's review plan now sorts Swift and Xcode files by risk instead of sending every iOS PR to the full review panel (GST-3041). (#4469) - /ship's review plan now sends Swift code that touches private user data to the full review panel (GST-3052). (#4472) - A round grant at /ship's review round cap now buys the fix round it names, in the same run or the next (GST-2968). (#4479) - The secrets check stops flagging three kinds of ordinary code as a secret, and catches two misses. (#4457) - A security finding's location and reason no longer go into a PR body. (#4486) - The token-capped /ship child on Claude Code now starts its prompt with the typed `/ship` command, so the skill actually loads. (#4487) - A /ship receipt now counts the second-model review's blocking findings, and refuses to be written while one is still open. (#4485) - A `/ship` with a token cap on Claude Code no longer stops at its first handoff. (#4452) - /ship's push step now always ends with one line that says whether it pushed (GST-3053). (#4474) - A PR's review-round count can no longer be overwritten by the body `/ship` posts. (#4440) - One queued record with a malformed path no longer stops artifacts sync for every project. (#4455) - A failed artifacts push stays reported until a push succeeds. (#4455) - The /sync-gbrain memory row no longer says OK when pages failed to import. (#4455) - ### Tests (#4495) - A policy-floor test no longer fails once gstack's own version reaches the minor after the newest policy key; it now checks a floor above both, so the v1.101.0.0 release can pass CI. (#4495) - CI now uploads free-suite test results to Trunk with analytics-uploader v2.1.8 and analytics-cli 0.17.0, up from v2.1.6 and 0.16.2. (#4453) - Packing a checkout for a Ubicloud run no longer fails when git beside it is rewriting a ref. (#4447) - The /plan-ceo-review HOLD SCOPE eval no longer fails a review because its follow-up question didn't repeat the mode name. (#4447) - Unattended /autoplan now records the owner's relayed gate reply instead of refusing it. (#4484) - Unattended /autoplan now runs the second-model review you turned on, and waits for it instead of ending the session. (#4459) - Two /autoplan runs started in the same second no longer share a run id. (#4459) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.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.
/sync-gbrain now says when an artifacts push failed or memory pages failed to import, instead of printing OK and "pushed", and one malformed queued path (from a skill started where the project slug was empty) no longer stops artifacts sync for every project.
Why: people trusted those rows and lost track of unsynced work; fixes #4445, #4418 and #4417.
Nothing to do after upgrading: a stuck
projects//timeline.jsonlrecord is dropped and reported on the next sync.Thanks to @exGeni for all three reports and their hermetic reproductions.
What changed
gstack-brain-enqueuerefuses a path with an empty,.or..component (exit 1, nothing queued). The drain classifies such a record asinvalidbefore staging, so git never stages it under another spelling; the record is dropped, the rest of the queue syncs, and the status message, stderr and~/.gstack/.brain-sync-drops.jsonname it. The writers' own local write toprojects/timeline.jsonlis unchanged (out of scope).okandidlebecomepush_failed;heldandcollisionkeep their code (their attention line names the files) and carry the unpushed count in the message. This covers the drained-queue and nothing-stageable branches the empty-queue path already handled.gstack-brain-sync --oncewrote in this run instead of trusting exit 0:oksays "curated artifacts pushed to git",idlesays "nothing new to push",held/collisionare WARN, andpush_failed/blocked/errorare ERRartifacts not pushed (<status>: <message>). When no status was written (sync off, lock held) the row says nothing was pushed. The gbrain page-count check still runs on every non-failure row.defaultsource fail repeatedly while /sync-gbrain reports the memory stage OK #4417).gstack-memory-ingestwrites its written/failed counts toGSTACK_INGEST_RESULT_FILEwhen the orchestrator sets it. Any failed page makes the row WARN, failed pages with none imported make it ERR, and the row shows the count and the first failure's cause (the child's FAILED lines were never shown by /sync-gbrain). Per-page failures still exit 0 and retry next run.curated artifacts pushed, and WARN/ERR rows as concerns.docs/gbrain-sync-errors.mdgains entries for the new brain-sync ERR row and the malformed-path drop.Tests
Each new test failed on main e0c4136 before the fix and passes after:
test/brain-sync.test.ts: enqueue refuses malformed paths; a malformed queued record is dropped and reported while the clean record syncs (main: whole batch refused); push_failed survives a drain of an unchanged queued file and of a file gone from disk (main:idle).test/gstack-gbrain-sync.test.ts: end to end with a real artifacts repo, the brain-sync row says pushed after a push andERR artifacts not pushed (push_failed: ...)after a rejected push and on the run after it (main: OK "pushed"). The A5 page-count test now expects the "nothing was pushed" lead, since sync is off in that fixture.test/gstack-gbrain-sync-transcript-mode.test.ts: a fake gbrain refuses every import; the memory row is ERR0 imported, N failedwith gbrain's cause (main: OK), and OK again once imports succeed.Issues
Refs #4417
Refs #4418
Refs #4445
Agent notes
Thread GSTA-585, issue GST-2996.
Plan: exempt: bug fix with failing-first tests (R65)
Review: gate class, full panel on pass 1 (testing/security/state-machines specialist, red team, coverage audit): 5 below-floor findings, all fixed in 1791d1a (unparseable transcripts no longer turn the memory row ERR; malformed-path drop note written only after finalize; drain freshness compares mtime and content; 9 unit tests and 1 integration test added). Fix-check at 1791d1a (grant a-924ef19e46ce): 3 notes. Step 11: native adversarial 5 Low notes; second-model review (gpt-6.1-sol) 1 finding ruled a note; targeted reader: no findings.
Ruled note: bin/gstack-gbrain-sync.ts:338:outside-voice at 1791d1a ruled by Captain GStack Minder (GSTA-36) at 2026-11-17T18:12:39.036Z: missing or unreadable ingest counts read as zero failures: below the floor, matches main; WARN change is a Captain follow-up (approval a-10c5371b47a6)