Prepare 0.4 without pretending it is published

01 / CandidateThe 0.4 implementation is release-ready

The 0.4 candidate removes global component and connection ceilings, adds caller-controlled resource budgets, canonicalizes every port alias before topology analysis, and closes routing defects around terminal approaches, reversal buses, marker batching, and self-connections. Quarter-turn geometry, typed primitives, net semantics, collision validation, netlist inspection, structural design rules, accessible descriptions, deterministic fuzzing, and source maps remain part of the same compiler.

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]

02 / GatePublish core before the website consumes it

The release gate runs type checking, 100% statement/branch/function/line coverage, bounded property fuzzing, fourteen targeted mutants with a 100% kill score, six Chromium pixel goldens, installed package-boundary tests, two gzip budgets, and latency/scaling ceilings. Those gates prove the properties they assert. They do not prove a circuit is electrically safe, temporally correct, standards-certified, or manufacturable.

Publication order is non-negotiable, and it is now automated rather than remembered. A tag push publishes @schemd/core to npm and cuts the GitHub release from that version's CHANGELOG.md section, so the prose is written once. A scheduled job on the website then adopts the release — dependency and lockfile together, release snapshot regenerated from npm's own packument — runs the complete web gate against it, and opens a pull request. Nothing merges itself, because a compiler release is allowed to change rendered geometry and that is the part CI cannot judge.

The ordering matters for a reason worth stating plainly: a linked dist/ proves local integration, never that the published tarball and its export map work. Only an install from the registry does that, which is why the sync job installs rather than links.

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]

Known boundaries remain deliberate: rotation is limited to quarter turns; text measurement is deterministic rather than font-engine exact; the model is flat rather than hierarchical; design rules are structural rather than SPICE, timing, or formal verification; routing is deterministic but bounded; and scalar/bus coercion is rejected instead of guessed. See Limitations and Resource budgets before treating untrusted source as a server workload.