Repository navigation
Conversation
|
Superseded by the reviewed current-main port in #21, normally merged as 5f5dcbd. The complete canonical tree matches the reviewed replacement, and its natural main CI passed: 20 scenarios, retained source/citation/render-record gates, and the existing smoke render. The eleven original bridge paths are retained or deliberately corrected within the fourteen-path port. Media remains observed; receipt references never certify outcomes. The branch-only v1 counter is corrected to workflowReceiptReferences without an alias, with productWorkflowProof not-certified and releaseReady false. Historical media and changed README/NODE-LOOPS digests are preserved without rebinding old captures to current documents. Current commands, dependency lock, wrapper, drivers and media remain intact. This old conflicting draft is closed unmerged. Its original head 36dd774, branch and historical receipts remain preserved. The old schema-only verified behavior and stale projection bytes were not adopted as fresh proof. The before/after update log is in docs/NODEKIT_PRESENT_EVIDENCE.md on main. One moderate and one high install-audit finding remain; this closure adds no workflow, pixel, provider, release or full-security certification. |
Summary
nodekit.evidence-index/v1artifactProof
npm run checkpassedHonest boundary
The three tracked artifacts are
observed; there are zero independent browser/judge receipts.releaseReady=falseandproductWorkflowProof=not-certified. No package publication or production deployment occurred.Pre-existing and not changed:
npm cilock/self-dependency failure and seven Remotion-chain audit findings.Integration handoff (2026-10-07): This draft retains the deterministic media-evidence bridge at 36dd774; current main b06ab18 declares FeatureClipStudio manifest/receipt ownership but does not contain this adapter. Preserve the adapter, schemas, tests, manifest and both generated artifacts. Its initial three assets remain observed with zero independent workflow receipts, releaseReady=false and productWorkflowProof=not-certified; receipt matching alone does not validate a browser/judge outcome. Before integration, confirm current canonical NodeKit contract compatibility, add the evidence lane without replacing main's current check/render/dependency controls, and reconcile the README provenance basis and deterministic outputs. The old local test/render assertions and old dependency failures describe their historical source, not current main or a newly validated integration.