Raw Payload
The harness remains a lightweight static verification page.
This wrapper keeps the harness inside the shared tool shell while the existing raw page continues to serve direct fixture and resolver checks.
Proof Surface
The harness remains intentionally lightweight; this wrapper aligns its route and framing strategy with the rest of the tool tier.
Verification Harness
Run quick browser-visible checks without dropping into a disconnected raw page.
The harness stays deliberately lightweight and fixture-driven. This route brings it under the shared tool shell while leaving the underlying static payload untouched for direct access and automation-friendly use.
Harness Payload
The existing static harness now runs behind the same shared tool frame.
This preserves the lightweight verification workflow while making the proof tier feel deliberate instead of fragmented.
Related Proof Surfaces
Use the harness when you need speed, not when you need the whole story.
The shared shell makes the relationship between direct browser checks, fixtures, and the wider proof layer easier to see.
Fixtures
Published fixtures remain directly accessible.
The harness still reads published fixture URLs, including the curated v0.2 signed-manifest lane and the broader v0.1 fixture corpus.
Proof Layer
The harness remains one tool inside the broader proof system.
Use the sandbox when you need a more narrative or broader verification path than the raw harness alone.