Repository navigation
Release 1.7.5: bounded reads and isolated peer workflows - #53
Merged
Merged
Conversation
This was referenced Sep 9, 2026
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.
Large job/workflow reads could exceed tool output limits and leave callers parsing truncated JSON. Public reads now return bounded, valid JSON (8192 UTF-8 bytes) with explicit omissions;
--outputwrites the complete authorized payload to a new mode-0600 file with a checksum receipt. Only complete delivery acknowledges a result, and unavailable/unsealed peer owners cannot expose sibling payloads.Independent workers receive complete memo, read/export and signal-cleanup instructions. Peer launches explicitly restrict builtins, deny discovered unselected MCP tools, disable ordinary hooks for that invocation, and reject forbidden tool events throughout memo/critique execution. Valid generic workflows retain normal result access. Native web citations use HTTPS strings with legacy compatibility and bounded schema-failure diagnostics.
Stateful direct tests use isolated homes. Full mutation runs in eight shards with unchanged targets/thresholds, and artifact actions use Node 24 with preserved archive/retention behavior. Version 1.7.5 adds no runtime dependency or history migration.
Validation on
66264eec6c20003c971011914bbbb03641989fd7: targeted RED/GREEN regressions and independent code/Fable reviews passed. Localnpm run checkpassed (1001 unit, 120 integration, 24 E2E plus lint/type/version/changelog checks). CI passed on macOS, Windows, Ubuntu coverage and Node 18; coverage is 92.79% lines/statements, 83.94% branches and 97.82% functions. PR mutation and all eight full mutation shards plus report merge passed. Downloadedmutation-fullartifact10101039469contains all eight JSON/HTML pairs with 14-day retention; thresholds are unchanged.Live design
workflow-mttyqjf8-56607729and researchworkflow-mttyzh4m-9585a4ddboth completed through critique/synthesis at revision 14. Memo and critique telemetry confirms Fable 5.1 / Opus 5, 1M context, no fallback or stream diagnostics, both selected exact Brave tools, native StructuredOutput, and no forbidden tool events. Full exports (98985 / 126650 bytes) matched their SHA-256 receipts and were read completely; final inventory matched all 204 initial entries including ignored files, with zero workspace changes.Known limit: an exceptional
fstatSyncfailure immediately after exclusive export creation can leave the new empty file until manually removed; no existing file is overwritten and the output is not acknowledged. Export publication is not crash-atomic. Native Windows peer execution and external MCP/managed-hook trust retain the documented boundaries.Closes #25
Closes #30
Closes #37
Closes #45
Closes #46
Closes #49
Closes #51
Closes #52