Repository navigation
fix: surface Pi graph errors and deliver reminders between steps - #42
Merged
Merged
Conversation
Epsirom
added a commit
that referenced
this pull request
Oct 4, 2026
## Change Prepare matching `@chrok/braid` and `@chrok/pi-braid` 0.3.0 releases from #41 and #42. This minor version accounts for writable Pi shell tools and Git-aware checkpoint semantics; it also includes Pi graph diagnostics, focused status/usage exports, cumulative merge-source baselines, and reminders between model steps. Update both manifests, Pi's exact core dependency, and the workspace lockfile. Finalize the changelog with implementing PR links and author credits, document 0.2 → 0.3 migration, and align both READMEs and the roadmap. Both included PRs are by @Epsirom, whose earlier contributions were verified; there are no first-time human contributors. ## Validation - `npm ci` and `npm run verify`: 227 core tests, 90 Pi tests, both type checks, offline examples, and isolated tarball checks passed. The package smoke verifies public imports, declarations, transitive core installation, and a Pi background job outside the checkout. - `npm pack --dry-run` for both packages: inspected clean file lists, licenses, and 0.3.0 versions; core has 39 files and Pi has 11. - `RELEASE_TAG=v0.3.0 node scripts/check-release.mjs` and `git diff --check` passed. - Hosted CI and CodeQL must pass before merge/tag. Publication will use the existing trusted-publishing workflow, followed by exact-version, latest-tag, provenance, and clean registry installation checks. - [x] Relevant tests and type checks pass. - [x] User-facing docs and changelog are updated where needed. - [x] Breaking changes include migration guidance. - [x] Release notes link feature/fix PRs, credit authors, and identify first-time contributors per the release guide.
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
1 participant
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.
Change
Pi could display failed graph submissions as jobs with undefined IDs, hide the output requested by a focused status read, and hold pause/completion reminders until the entire foreground task ended. This makes errors visible and delivers reminders after the current assistant response and tool batch so the parent can handle pauses during ongoing work.
mergeSources[].changes.baseCommitmetadata for cumulative diffs after read-only reviews, and explain how to handle multi-parent checkpoints. Regression coverage verifies integration preserves staged, unstaged, and untracked caller edits.Validation
npm run verify: 227 core tests and 90 Pi tests pass, plus both type checks, offline examples, and external tarball installation/build checks.Real Pi host fixtures verify reminders during model responses and tool batches, without skipping tools, plus idle continuation and acknowledgement behavior. Additional host/schema checks passed with Pi 1.0.2.
Kimi K3 parameter-generation smoke preserved all requested node fields. A reviewed Pi 1.0.2/Kimi K3 session completed parallel worktrees, atomic update/resume, read-only acceptance, integration, and an optional-failure/cancel probe; its generated project passed 17 tests. No session transcripts or provider outputs are included.
Live coverage did not exercise feedback retries or the final cumulative-baseline addition; these are covered by deterministic runtime/Git regressions.
Relevant tests and type checks pass.
User-facing docs and changelog are updated.
Compatibility reviewed: diagnostic metadata is additive and the new public field is optional; no breaking changes in this PR.
Not a release PR.