Repository navigation
fix: remediate exact-main release audit findings - #97
Merged
Merged
Conversation
Summary: - reject durable collection admissions before schema exhaustion - require authentication for effective public binds - enforce loopback same-origin access in tokenless mode Root cause: - persistence limits were enforced only after mutation - runtime authentication considered the internal bind but not the published bind Fix: - centralize durable collection capacity checks with concurrent Agent reservations - validate PUBLIC_BIND_ADDR and guard tokenless API requests by Host and Origin - cover server and Compose boundaries with causal regressions Testing: - 154 focused server tests - 7 Compose deployment tests - server TypeScript check - git diff --check
Summary: - eliminate the Project Group mention caret race - restore direct Playground E2E coverage under the Shepherd-first default - expose meaningful Settings field names and remove fractional footer clipping Root cause: - caret placement was deferred beyond React's controlled-input commit - legacy fixtures assumed the previous route default and Codex resume argv shape - numeric controls lacked explicit accessible names and scroll targeting had no rounding margin Fix: - synchronously commit mention content before placing the caret - explicitly select direct mode in legacy tests and parse the resume separator - add ARIA labels and a one-pixel scroll margin without changing layout Testing: - Playwright matrix: 38/38 passed at 1280x800 and 1440x900 - E2E harness units: 19/19 passed - web unit tests: 20/20 passed - web typecheck and production build
Summary: - make live Shepherd runtime discovery exact-tree and volume-aware - enforce server and browser coverage thresholds above 80 percent - validate pinned Terraform and keep runtime secrets out of state/cloud-init - cover and fix the Agent edit hydration race plus release browser paths Root cause: - release gates relied on ambient executables, incompatible coverage maps, and host-only Terraform - Terraform threaded runtime credentials through sensitive variables into state and user data - the Agent edit form rendered before authority hydration completed Tests: - server coverage: 86.15/80.05/91.46/88.03 - web coverage: 88.50/80.09/87.64/92.37 - Terraform 1.9.8 validate with volcenginecc 0.0.58 - 34 infrastructure and harness regressions, strict typecheck, npm audit
This was referenced Aug 31, 2026
Closed
sanjey99
marked this pull request as ready for review
August 31, 2026 13:23
sanjey99
added a commit
that referenced
this pull request
Aug 31, 2026
Summary: Reconcile the release ledger and test report after PR #97 merged as 53f2529. Change: - Record exact post-integration repository, coverage, browser, Terraform, live-preflight, and hosted results. - Move issue #96 findings from candidate to integrated while preserving independent UI, security, external Ark, and rehearsal gates. - Correct the stale OPS-06 compose-exposure status. Testing: - Local Markdown links resolve across all five changed documents. - git diff --cached --check passes. - Exact merge gates are recorded from the clean 53f2529 worktree.
10 tasks done
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.
Summary
Remediates every concrete defect found in the 2026-08-31 exact-main release audit
and adds reproducible release gates for the evidence that was previously blocked or
unverifiable.
Ownership and scope
fix/96-release-readiness-auditorigin/mainatf935fdb5581849f8377f20922e254c55d34e5de0223a5fe00f977013d4bf5df6560016a1719c8d11bb1a1dfbe5695a74c340031a427bcda9da782319Independent UI/security sign-off, the external Ark inference, protected-main
integration, and demo rehearsals are evidence responsibilities, not hidden product
exclusions. They are kept explicitly open below and in the task ledger.
Root causes and fixes
Durable and API boundaries
Durable admission was checked only after mutation, concurrent Agent creates did not
reserve capacity, and rejected creates could leave partial workspace/state. Tokenless
mode also trusted arbitrary Host/Origin values, while deployment publication could
bind publicly without the server seeing that effective address.
Admission is now reserved before mutation, all durable push sites are bounded, Agent
publication is atomic, tokenless requests are loopback/same-origin only, and public
binding fails closed without a strong token.
Browser behavior
Controlled React drafts could be consumed before their latest state commit. Agent
edit rendered before presets and Agent data had hydrated, so a rapid authority toggle
could overwrite edits. Focused synchronization/hydration fixes preserve the existing
components and styling. Regression coverage also pins Settings recovery/reset,
Agent CRUD/lifecycle/edit/delete/sorting, direct Playground, malformed/missing
routes, runtime contracts, cancellation links, accessibility names, and no document
overflow.
Live and deployment gates
The old live wrapper forced a host bind mount on the documented affected macOS Docker
Desktop layout and did not independently build the current tree. The new wrapper
builds disposable Runtime/controller images from the exact checkout and runs the
non-root controller on a named volume. Terraform validation now has a pinned Docker
fallback and operates on a disposable module copy. Runtime secrets are no longer
Terraform data.
Coverage and documentation
The repository had neither a coverage provider nor a reproducible 80% check.
Server V8 and browser Istanbul coverage are now separate canonical maps, with every
production file required and statements/branches/functions/lines all enforced.
docs/SHEPHERD_TEST_REPORT.mdrecords exact commands, counts, failures and limits;historical estimates are explicitly labelled rather than presented as current state.
Test evidence
npm run checknpm run test:coveragenpm run test:terraformnpm run test:shepherd:live:preflightnpm audit --json: 0 vulnerabilitiesgit diff --check, local Markdown-link validation, and bounded tracked credential/state/artifact scansbb1a1dfNode 22 / npm run checkrun33389614355: pass in 2m59sRequired checksrun33389614223: pass in 3m01s96eecb9:Node 22 / npm run checkrun33390293339passed in 3m16s96eecb9:Required checksrun33390293341passed in 2m34s14b69f2:Node 22 / npm run checkrun33391006561passed in 4m40s14b69f2:Required checksrun33391006569passed in 3m11sCommit log
2e7c915— harden durable and tokenless boundaries69c12de— close deterministic browser gate defects223a5fe— close release-readiness gaps across browser/live/coverage/Terraform/securitybb1a1df— reconcile exact-main release evidence96eecb9— record hosted release checks14b69f2— record the accepted Inter typography detector exceptionReview notes
product-scope removal was used to make a gate pass.
and later documentation commit.