Skip to content

P0: reconcile merged PR #68/#69 follow-ups before claiming readiness #70

Open

Description

@hyperpolymath

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.a2ml to 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-known paths (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.yml uses actions/upload-artifact@v7.0.2 four times while its generated actions.lock section specifies v7.0.1. Correct uses consistently with lock or regenerate lock with gh 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/standards and fail. Verify canonical metadatastician/standards reusable paths, permissions and full-SHA pins before changing.
  • build/just/validate.just still contains stale licensing paths and AI install expectations; validate-state currently prints INVALID without non-zero exit.
  • Idris2 rsr_* imports disagree with Zig scaffoldia_* 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

  1. P0a review-contract amendments: agent manifest, roadmap local apply, overlay precedence.
  2. P0b Actions lock mismatch + real E2E toolchain; canary negative tests.
  3. P0c reused standards workflow paths/permission/startup causes.
  4. P0d validators and optional ABI seam decision.
    No estate-wide propagation or repository config changes without owner review.

Activity

  1. added
    tech-debtKnown shortcut, drift, or hygiene owed - includes cleanup
    on Nov 15, 2026
  2. coderabbitai commented on Nov 15, 2026

    @coderabbitai
    Contributor
    🔗 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 plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 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:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    tech-debtKnown shortcut, drift, or hygiene owed - includes cleanup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions