Repository navigation
Replace APS with paired case investigation and reconcile protected tests - #29
Merged
Merged
Conversation
SafetyMP
marked this pull request as ready for review
November 14, 2026 21:05
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.
This replaces the active APS interface with the five-view investigation experience: immutable side-by-side comparisons, a visible failure path, meaningful case inputs, retained reasoning, and a hypothetical recovery branch. Start here, Case Lab, Hazard study, Controls, and Evidence share the same session while distinguishing illustrative outcomes from frozen recorded trials.
The release starts from current main
b888da6005e052498520b7bb9aa5a2040c708e4f. Existing history and reusable workflow/decision-brief libraries remain preserved. Production integrity retains all 70 original protected files and the original inspection, separately pins only the three existing purchase regression files, and rejects unexpected additions, modified bytes and symlink substitution. The Node integrity suite remains a required CI step; Vitest excludes only that separately executed file.Validation at head
576a24e2d7a9bc552f4777e8ee4ed0e2e2a34b4a, tested mergef690cdd3d28025b094c7c7af5da40706af033330:14132035598, SHA256bc8c78d960c4f27c3638b3dbd69c52a9e83b6afe301306c84a140aec73ac0453.Local full Python validation passed 143 tests. Production dependency audit found no vulnerabilities; the existing development dependency advisories were not changed. The earlier failed Linux run is retained in the PR history; its test-runner discovery conflict is fixed without removing checks.
Predeployment verification only. Deployment workflow and historical postdeployment acceptance gate are unchanged. This does not attest deployment, cross-browser qualification, participant comprehension or real-world process safety. See
docs/APS_REDESIGN_RELEASE.mdfor scope and preservation details.Deployment completion
Merged and published at https://safetymp.github.io/Agentic-Process-Safety/. Final main commit
2232a5536347cad5cd35c32a3608c3c818d186d9passed deployment run43642042209, repository checks and CodeQL. All185 live browser assertions passed with zero console/page errors or nonstatic requests. All9live static files match the actual Pages build byte-for-byte.The strict authenticated postdeployment verifier passed, and final independent review accepted the exact QA inventory,7reviewed captures, actual source/run/deployment identities and9served files. Follow-up PR#30 binds acceptance to the exact reviewed redesign runner; PR#31 preserves a legacy screenshot outside the current capture directory after the gate correctly rejected an unexpected eighth image. Neither follow-up changes app or deployment workflow bytes; no acceptance check was relaxed, and failed/historical evidence remains retained.