Full Parity Milestone 7 Kukulkan Rewrite Evidence

Milestone 7 tracks the Kukulkan production rewrite.

Current state: unresolved-kukulkan-gap. The old Kukulkan source exists at

/home/n0um3n4/repositories/kukulkan, and current 0x0 Kukulkan packages,

runtime artifacts, deployment manifests, integrations, and release metadata

exist under apps/kukulkan/, but apps/real-rewrite-gap.tsv still has

Kukulkan rows that are not production-ready.

Gate

Generate the evidence ledger:

make full-parity-milestone7

Check the milestone evidence:

make full-parity-milestone7-check

The gate validates source presence, current 0x0 Kukulkan artifacts, old-source

availability, unresolved gap tracking, roadmap status, and documentation.

Current Evidence

• apps/kukulkan/packages/
• apps/kukulkan/deploy/
• apps/kukulkan/integrations/
• apps/runtime-revalidation.tsv
• apps/build-manifest.tsv
• parity/milestone7-kukulkan.tsv

Existing focused gates remain the behavior gates:

• make kukulkan-production-check
• make kukulkan-api-full-check
• make kukulkan-ui-full-check
• make kukulkan-deploy-check
• make apps-real-rewrite-gap-check

Closure Rule

Milestone 7 cannot close until apps/real-rewrite-gap.tsv has zero unresolved

Kukulkan rows and the deployed Kukulkan app runs from current 0x0 release

artifacts with API, UI, browser, deployment, rollback, and operations evidence.

Documentation Impact Review

Kukulkan package, API, UI, Live, browser, deployment, integration, release, or

operational behavior changes must update this file,

docs/kukulkan-pure-packages.html, docs/kukulkan-api-runtime.html,

docs/kukulkan-ui-runtime.html, docs/kukulkan-deployment.html,

docs/kukulkan-operator-runbook.html, docs/feature-support-matrix.html, and

docs/release-notes.html in the same change unless the ADR/RFC explains why a

location is unaffected.