feat: SQLite busy retry, ops reports, and security/acceptance closures - #4
Merged
Conversation
Add Stmt.stepCritical for events/orders/fills/equity/agent_runs/tools/ memories writers (AC-FD6). gate2-report and check-remote now surface system.status.disk and llm health for soak ops. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…OPS3/9, NFR01) - AC-SEC5: fixed-capacity HTTP response sinks (OKX 512KB, LLM 1MB, egress probe 4KB) + security/limits.zig structural JSON scan - AC-SEC6: security/isolation.zig source-scan tests enforcing agent module isolation (no http/net/fs/process/credential reach) - AC-SEC7: formatObservation neutralizes structurally unsafe tool data_json to null; fault-matrix injection tests (prose stays inert data, breakout/depth-bomb payloads neutralized) - AC-FR04: proposal fuzz tests (prefix truncation, 4000-round byte flips; parse never crashes, surviving mutants keep invariants) - AC-GO3: property tests for cost/shock monotonicity, drawdown tightening, and partial-fill replan convergence - AC-OPS3/9: hourly(24)/daily(30) rotated backups + retention sweep (tool_calls 30d, equity 1s 7d) wired into backup cycle - AC-NFR01: risk-apply latency histogram exposed in system JSON - docs: acceptance matrix and NEXT status updates Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
jamiesun
changed the title
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.
Summary
Two commits closing out pure-code acceptance items from the matrix (no demo keys / soak required).
949d7e9 — SQLite busy retry + ops reports
stepCriticalbusy retry on critical write paths4b2d2d5 — Security hardening & acceptance closures
security/limits.zigstructural JSON scan (depth bomb / breakout / truncation covered by unit tests)security/isolation.zig—@embedFilesource-scan tests enforcing agent module isolation (no http/net/fs/process/credential reach;openai.zigwhitelisted forstd.httponly)formatObservationneutralizes structurally unsafe tooldata_jsontonull; fault-matrix injection tests prove injected prose stays inert inside thedatafield and breakout/depth-bomb payloads are neutralizedmax_drawdowntightening monotonicity, and partial-fill replan convergence (qty monotone decreasing, side never flips)tool_calls30d, equity1s7d) wired into the hourly backup cycle, best-effort and never blocking the trading pathlatency_us{p50,p99,max,samples}in system JSONACCEPTANCE_MATRIX.md/NEXT.mdstatus updates with evidence notesValidation
All 173 tests green (was 151 before this branch; +22 new tests across limits/isolation/retention/latency/fuzz/property/injection).