v0.3 · Contribute

Ship 0.3 without hiding its boundaries

What is complete, what remains release metadata, and what is explicitly out of scope.

01 / 0.3Primitive and rotation work is complete

Quarter-turn transforms, typed primitive families, polished qgate, semantic ports, bus-width checks, expanded UML relations, deterministic fuzzing, exact resource ceilings, and 100% core coverage are complete.

source:AC "AC" at (90, 120) #blue [type=voltage-ac]
capacitor:C "C" at (280, 120) #cyan [orientation=down]
adder:FA "FA" at (500, 120) #amber [type=full]
qgate:Q "R_z" at (710, 120) #purple [parameter="\theta"]
component:SYS "system" at (870, 290) #slate [width=150 height=80]
compiled by @schemd/core → shown in the rail

02 / GatePublication metadata remains pending

The 0.3 line documents releases 0.3.0 through the current 0.3.x patch; the newest release in the line is the deterministic fallback until npm publication confirms it. The timeline must replace the pending date and commit hash from registry/GitHub data after release. Phase 5 owns version changes, changelogs, README updates, tags, pushes, and npm publication authorization.

logic:READY "1" at (100, 120) #blue [type=high]
testpoint:GATE "release gate" at (340, 120) #amber
load:L "lamp" at (590, 120) #emerald [type=lamp]
READY.out -> GATE.node #blue [digital line]
GATE.node -> L.in #emerald [digital line]
compiled by @schemd/core → shown in the rail

Known boundaries remain deliberate: no arbitrary-angle rotation, no browser font measurement, no unbounded plug-in renderer, and no silent scalar/bus coercion.