Skip to content

Bootstrap V4 differential conformance campaign - #95

Draft
OttoApocalypse69 wants to merge 3 commits into
fix/v4-post-merge-contract-hardeningfrom
test/v4-differential-bootstrap
Draft

Bootstrap V4 differential conformance campaign#95
OttoApocalypse69 wants to merge 3 commits into
fix/v4-post-merge-contract-hardeningfrom
test/v4-differential-bootstrap

Conversation

@OttoApocalypse69

Copy link
Copy Markdown
Member

What changed

  • add a strict V3/V4 differential manifest and runner with four initial semantic cases
  • build a TY-only V4 campaign probe that embeds source opaquely, validates byte length/digest, and fails closed on native/runtime claims
  • rebuild current V3 through the canonical seed-to-stage2-to-CLI sequence rather than trusting a stale binary
  • enforce 11 phased campaign categories, including explicit empty phases, independently from compatibility relationships
  • reject duplicate manifest/probe JSON keys and bound complete process trees on Windows and POSIX
  • add a dedicated Ubuntu CI job for the campaign and nested POSIX cleanup self-test

Boundary and claims

This bootstrap compares frontend accept/reject/category behavior only. It reports v4-native=0 and never fabricates native equivalence. The V4 probe stops at TY and does not reach MIR, codegen, or target execution.

Validation

  • independent exact-head review of 3180fb5f36618f33259bb859d1665c5ea0b98676: APPROVE, no P0-P3
  • freshly rebuilt current V3 + V4 campaign: 4/4 pass, zero mismatches
  • LLVM-MinGW generated-probe self-test: 3 compiled probes
  • manifest self-test: 4 cases, all 11 ordered categories, phase mapping, duplicate-key rejection
  • Windows Job Object nested timeout cleanup: pass
  • independent WSL/Linux nested memory cleanup and outer-timeout probe: pass
  • Python compilation, AST/static boundary checks, and git diff --check: pass

Stack and pending gates

This draft is based on fix/v4-post-merge-contract-hardening / PR #91 and is independent of the MIR split. Current-head Ubuntu CI remains required for the committed POSIX aggregate memory/termination path; macOS process-accounting fallback remains a platform evidence item. No existing PR readiness was changed.

- Compare frontend acceptance, diagnostic classes, and stable phase summaries
- Fail closed on native runtime claims and resource-bound each adapter
- Reconstruct and bind opaque UTF-8 sources before frontend analysis
- Enforce schema, taxonomy, resource, and toolchain contracts
- Run the current frontend campaign in V4 CI
- Declare phased fixture categories and reject duplicate manifest keys
- Keep nested POSIX compiler processes inside the outer campaign bounds
- Cover process ownership and phased schema behavior in self-tests
@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3c47910c-d205-48b4-a3f1-648e46373753

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant