Harden public defensive integrity checks

Author: hamlet-lab

.github/workflows/ci.yml

@@ -11,19 +11,28 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-python@v5
+      # Pinned to actions/checkout v4 release tag commit 34e114876b0b11c390a56381ad16ebd13914f8d5.
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5
+        with:
+          persist-credentials: false
+      # Pinned to actions/setup-python v5 release tag commit a26af69be951a213d495a4c3e4e4022e16d87065.
+      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065
         with:
           python-version: '3.11'
-      - uses: actions/setup-node@v4
+          cache: 'pip'
+          cache-dependency-path: requirements.lock.txt
+      # Pinned to actions/setup-node v4 release tag commit 49933ea5288caeca8642d1e84afbd3f7d6820020.
+      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020
         with:
           node-version: '20'
-      - name: Install TypeScript for skeleton compile checks
-        run: npm install -g typescript@5
-      - name: Install package and test dependencies
+      - name: Install Node dependencies from package-lock
+        run: |
+          npm ci
+          echo "$PWD/node_modules/.bin" >> "$GITHUB_PATH"
+      - name: Install package and test dependencies with locked constraints
         run: |
           python -m pip install --upgrade pip
-          python -m pip install -e ".[dev]"
+          python -m pip install -c requirements.lock.txt -e ".[dev]"
 
-      - name: Phase 30 v1.0 RC candidate check
-        run: python scripts/run_phase30_v1_rc_candidate_check.py
+      - name: Phase 30 v1.0 RC candidate quick integrity check
+        run: python scripts/run_phase30_v1_rc_candidate_check.py --mode quick-integrity

.gitignore

@@ -12,14 +12,14 @@ build/
 prelaunch_results/
 golden_trace_results/
 *_results/
+.codex_tmp/
 .ainir_tmp/
-.ainir_local_tmp/
 ainir_phase*_trial_*/
 ainir_phase*_private_trial*/
 ainir_phase*_results*/
 ainir_private_trial_results*/
 github_private_trial_results/
-ainir_local_tmp_*/
+codex_ainir_*/
 ainir_demo_results/
 ainir_negative_conformance/
 ainir_golden_traces/

README.md

@@ -134,6 +134,8 @@ snapshot management, and profile-specific conformance packs. See
 Run from the repository root. The demo writes reports to your OS temp directory
 so the checkout stays clean.
 
+The demo runs bundled workflow drafts; it is not an interactive prompt.
+
 **macOS / Linux**
 
 ```bash
@@ -158,7 +160,7 @@ Expected result:
 AiNIR public demo: passed
 - account_deletion_hard_delete_blocked: blocked (10 critical)
 - create_user_outbox_safe: passed (0 critical)
-- order_payment_real_payment_blocked: blocked (15 critical)
+- order_payment_real_payment_blocked: blocked (16 critical)
 - password_reset_raw_token_blocked: blocked (11 critical)
 - pii_export_raw_pii_blocked: blocked (17 critical)
 ```

docs/README.md

@@ -6,16 +6,16 @@ Start here if you want to understand the system rather than the development hist
 
 ## Recommended reading path
 
-1. [`v1_rc_candidate.md`](v1_rc_candidate.md) - v1.0 RC candidate decision and boundary.
-2. [`v1_rc_scope.md`](v1_rc_scope.md) - what is frozen for RC review.
-3. [`pre_v1_status.md`](pre_v1_status.md) - current scope and what AiNIR does not claim.
-4. [`trust_gate.md`](trust_gate.md) - the unified decision surface.
-5. [`trust_receipt_persistence.md`](trust_receipt_persistence.md) - issuing and replaying TrustReceipts.
-6. [`negative_conformance_corpus.md`](negative_conformance_corpus.md) - synthetic fixtures that must be refused.
-7. [`golden_traces.md`](golden_traces.md) - deterministic replay expectations.
-8. [`lowering_gate.md`](lowering_gate.md) - when lowering is allowed or refused.
-9. [`verified_intent_packet.md`](verified_intent_packet.md) - optional future export surface.
-10. [`public_private_boundary.md`](public_private_boundary.md) - what belongs in the public repo.
+1. [`v1_rc_candidate.md`](v1_rc_candidate.md) — v1.0 RC candidate decision and boundary.
+2. [`v1_rc_scope.md`](v1_rc_scope.md) — what is frozen for RC review.
+3. [`pre_v1_status.md`](pre_v1_status.md) — current scope and what AiNIR does not claim.
+4. [`trust_gate.md`](trust_gate.md) — the unified decision surface.
+5. [`trust_receipt_persistence.md`](trust_receipt_persistence.md) — issuing and replaying TrustReceipts.
+6. [`negative_conformance_corpus.md`](negative_conformance_corpus.md) — synthetic fixtures that must be refused.
+7. [`golden_traces.md`](golden_traces.md) — deterministic replay expectations.
+8. [`lowering_gate.md`](lowering_gate.md) — when lowering is allowed or refused.
+9. [`verified_intent_packet.md`](verified_intent_packet.md) — optional future export surface.
+10. [`public_private_boundary.md`](public_private_boundary.md) — what belongs in the public repo.
 
 ## Core architecture docs
 
@@ -58,8 +58,8 @@ Start here if you want to understand the system rather than the development hist
 
 Phase-specific documents are kept for traceability. They are not required for a first read. Read them when you need to understand why a particular gate or fixture was added.
 
-- [v1.0 RC Candidate Patch 4 - Registry and Classifier Consistency](v1_rc_candidate_patch4.md)
+- [v1.0 RC Candidate Patch 4 — Registry and Classifier Consistency](v1_rc_candidate_patch4.md)
 - [Cross-platform output paths](cross_platform_output_paths.md)
 
-- [v1.0 RC Candidate Patch 6 - Release Identity and Cross-platform Temp Paths](v1_rc_candidate_patch6.md)
-- [v1.0 RC Candidate Patch 7 - Repo-local Temp Isolation Guard](v1_rc_candidate_patch7.md)
+- [v1.0 RC Candidate Patch 6 — Release Identity and Cross-platform Temp Paths](v1_rc_candidate_patch6.md)
+- [v1.0 RC Candidate Patch 7 — Repo-local Temp Isolation Guard](v1_rc_candidate_patch7.md)

docs/ci_supply_chain_hardening.md

@@ -0,0 +1,11 @@
+# CI Supply-Chain Hardening
+
+This public demo workflow is pinned for defensive integrity pass18:
+
+- `actions/checkout` is pinned to commit `34e114876b0b11c390a56381ad16ebd13914f8d5`, the v4 release tag commit observed during pass18.
+- `actions/setup-python` is pinned to commit `a26af69be951a213d495a4c3e4e4022e16d87065`, the v5 release tag commit observed during pass18.
+- `actions/setup-node` is pinned to commit `49933ea5288caeca8642d1e84afbd3f7d6820020`, the v4 release tag commit observed during pass18.
+- Python installs use `requirements.lock.txt` as a constraints file.
+- TypeScript is pinned to `5.8.3` and reflected in `package-lock.json`.
+
+This remains a public demo workflow, not a production runtime deployment workflow.

docs/cross_platform_output_paths.md

@@ -29,7 +29,7 @@ For private-trial and release-candidate checks, keep `TMP`, `TEMP`, and
 `AINIR_TEMP_ROOT` outside the repository checkout. A repo-local temp directory
 can make a trial copy see its own generated output. The Phase 26 runner now
 falls back to a sibling temp copy if the OS temp directory resolves inside the
-repo, and it ignores common local temp folders such as `.ainir_local_tmp/` and
+repo, and it ignores common local temp folders such as `.codex_tmp/` and
 `ainir_phase*_trial_*/`. Still, the recommended practice is to use the OS temp
 directory or an explicit path outside the checkout.
 

docs/demo_expected_output.md

@@ -12,7 +12,7 @@ Expected output:
 AiNIR public demo: passed
 - account_deletion_hard_delete_blocked: blocked (10 critical)
 - create_user_outbox_safe: passed (0 critical)
-- order_payment_real_payment_blocked: blocked (15 critical)
+- order_payment_real_payment_blocked: blocked (16 critical)
 - password_reset_raw_token_blocked: blocked (11 critical)
 - pii_export_raw_pii_blocked: blocked (17 critical)
 ```

docs/github_launch_checklist.md

@@ -2,7 +2,7 @@
 
 ## Files
 
-- [ ] Use the tracked repository contents from `hamlet-lab/ainir`.
+- [ ] Use the `ainir_public_demo_repo_v1_0_rc_candidate` repository contents.
 - [ ] Do not include private archive ZIPs.
 - [ ] Do not include generated check folders.
 - [ ] Confirm `LICENSE` is Apache-2.0.
@@ -67,4 +67,4 @@ python -m ainir phase30-v1-rc-candidate-check --out-dir /tmp/ainir_phase30_v1_rc
 python scripts/run_phase26_private_trial.py --out-dir /tmp/ainir_phase26_private_trial
 ```
 
-Keep the repository private until README rendering and GitHub Actions have been checked.
+Only upload to a private GitHub repository after this passes.

docs/golden_traces.md

@@ -1,4 +1,4 @@
-# Pre-v1 Phase 8 - Conformance Golden Traces
+# Pre-v1 Phase 8 — Conformance Golden Traces
 
 Phase 8 adds a deterministic replay harness for the public AiNIR demo pipeline.
 

docs/index.md

@@ -6,16 +6,16 @@ Start here if you want to understand the system rather than the development hist
 
 ## Recommended reading path
 
-1. [`v1_rc_candidate.md`](v1_rc_candidate.md) - v1.0 RC candidate decision and boundary.
-2. [`v1_rc_scope.md`](v1_rc_scope.md) - what is frozen for RC review.
-3. [`pre_v1_status.md`](pre_v1_status.md) - current scope and what AiNIR does not claim.
-4. [`trust_gate.md`](trust_gate.md) - the unified decision surface.
-5. [`trust_receipt_persistence.md`](trust_receipt_persistence.md) - issuing and replaying TrustReceipts.
-6. [`negative_conformance_corpus.md`](negative_conformance_corpus.md) - synthetic fixtures that must be refused.
-7. [`golden_traces.md`](golden_traces.md) - deterministic replay expectations.
-8. [`lowering_gate.md`](lowering_gate.md) - when lowering is allowed or refused.
-9. [`verified_intent_packet.md`](verified_intent_packet.md) - optional future export surface.
-10. [`public_private_boundary.md`](public_private_boundary.md) - what belongs in the public repo.
+1. [`v1_rc_candidate.md`](v1_rc_candidate.md) — v1.0 RC candidate decision and boundary.
+2. [`v1_rc_scope.md`](v1_rc_scope.md) — what is frozen for RC review.
+3. [`pre_v1_status.md`](pre_v1_status.md) — current scope and what AiNIR does not claim.
+4. [`trust_gate.md`](trust_gate.md) — the unified decision surface.
+5. [`trust_receipt_persistence.md`](trust_receipt_persistence.md) — issuing and replaying TrustReceipts.
+6. [`negative_conformance_corpus.md`](negative_conformance_corpus.md) — synthetic fixtures that must be refused.
+7. [`golden_traces.md`](golden_traces.md) — deterministic replay expectations.
+8. [`lowering_gate.md`](lowering_gate.md) — when lowering is allowed or refused.
+9. [`verified_intent_packet.md`](verified_intent_packet.md) — optional future export surface.
+10. [`public_private_boundary.md`](public_private_boundary.md) — what belongs in the public repo.
 
 ## Core architecture docs
 
@@ -58,8 +58,8 @@ Start here if you want to understand the system rather than the development hist
 
 Phase-specific documents are kept for traceability. They are not required for a first read. Read them when you need to understand why a particular gate or fixture was added.
 
-- [v1.0 RC Candidate Patch 4 - Registry and Classifier Consistency](v1_rc_candidate_patch4.md)
+- [v1.0 RC Candidate Patch 4 — Registry and Classifier Consistency](v1_rc_candidate_patch4.md)
 - [Cross-platform output paths](cross_platform_output_paths.md)
 
-- [v1.0 RC Candidate Patch 6 - Release Identity and Cross-platform Temp Paths](v1_rc_candidate_patch6.md)
-- [v1.0 RC Candidate Patch 7 - Repo-local Temp Isolation Guard](v1_rc_candidate_patch7.md)
+- [v1.0 RC Candidate Patch 6 — Release Identity and Cross-platform Temp Paths](v1_rc_candidate_patch6.md)
+- [v1.0 RC Candidate Patch 7 — Repo-local Temp Isolation Guard](v1_rc_candidate_patch7.md)