Repository navigation
Description
Why this issue exists
On 2026-11-15, draft PRs #68 (architecture reconciliation) and #69 (CI contract gates) were moved to ready and merged by the hyperpolymath GitHub identity while checks/reviews were still outstanding. This tracker does not allege who initiated the action (human versus concurrent automation). The assistant did not request or execute merges.
Not completed under the standing rule: latest-head green required checks and substantive review threads resolved.
Review debt from #68 (all unresolved at merge)
- Update root
0-AI-MANIFEST.a2mlto consume deed-era contracts and remove template-name/legacy ReScript instructions. - M0 roadmap must include an approved local staging apply for mint and retrofit, not only dry-run.
- Define contract-authorised overlay path replacement and precedence; undeclared conflicting paths still fail.
The previously prepared corrective changes were not pushed because docs(architecture): reconcile Scaffoldia with deed-era contracts and M0 acceptance gates #68's branch was deleted after merge. Reapply via a new scoped PR after safe coordination, answer each review thread and resolve it only after evidence.
Live CI blockers on main 8c833fbe38c63561b7a9d7bc1c74f786c95d49d1
- Well-Known Standards succeeds with published
www/.well-knownpaths (fix(ci): use published well-known paths and verify actions.lock-backed pins #69). - Lock-verifier fixture positive and negative self-tests succeed (fix(ci): use published well-known paths and verify actions.lock-backed pins #69).
- Workflow Security Linter fails because
static-analysis-gate.ymlusesactions/upload-artifact@v7.0.2four times while its generatedactions.locksection specifiesv7.0.1. Correctusesconsistently with lock or regenerate lock withgh actions-lock; never hand-edit generated actions.lock. Verify on PR head. - E2E harness fails because Idris2 is absent on the runner. Provide an actual verified Idris2+Zig toolchain, then run real builds and integration tests; don't greenwash with skips.
- Static Analysis Gate reports
startup_failure(not an executed security test); determine allowlist/lock/permission/root cause from GitHub Actions diagnostics. - Reusable scanner/hypatia/governance/mirror callers still reference old
hyperpolymath/standardsand fail. Verify canonicalmetadatastician/standardsreusable paths, permissions and full-SHA pins before changing. -
build/just/validate.juststill contains stale licensing paths and AI install expectations;validate-statecurrently prints INVALID without non-zero exit. - Idris2
rsr_*imports disagree with Zigscaffoldia_*exports and result semantics; ABI cannot be claimed linked/proven.
Guardrail and next changes
The current branch rulesets have only a narrowly required scan / gitleaks status (with a repository-role bypass); they do not require the E2E, workflow linter or static-analysis checks. Do not add speculative required check names: first make true emitted contexts and jobs pass, then propose protections, reviewed against actual status context IDs.
Do not auto-merge or squash before application review, substantive thread closure and genuine latest-commit CI evidence. One corrective issue is tracked here to prevent independently merged drafts from being misrepresented as completion.
Scope of follow-up PRs
- P0a review-contract amendments: agent manifest, roadmap local apply, overlay precedence.
- P0b Actions lock mismatch + real E2E toolchain; canary negative tests.
- P0c reused standards workflow paths/permission/startup causes.
- P0d validators and optional ABI seam decision.
No estate-wide propagation or repository config changes without owner review.
Activity
coderabbitai commentedon Nov 15, 2026
🔗 Related PRs
#68 - docs(architecture): reconcile Scaffoldia with deed-era contracts and M0 acceptance gates [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
fix(validation): fail closed on missing or malformed STATE metadata (#70