git:20260830.859f419 to git:20260908.4fb92cd

+ Never implement beyond the MVP cut list in `09-mvp-definition.md` (no incremental compilation; the "no LCEDA" cut was superseded by user direction 2026-08-27 — see the `.enet` paragraph below). Originally-cut items that have since graduated via Accepted RFCs and ARE implemented: structural-variant pattern matching (RFC-008), `cohdl fmt` canonical form (RFC-009), `cohdl check/build --json` (RFC-010), the formal error-code registry (RFC-011), `#[intent("...")]` opaque-metadata annotations (RFC-012), layout constraints — `layout {}` + `#[placement_hint]` → `layout.json`, E10xx checks (RFC-013), the LSP server `cohdl lsp` (RFC-014), the IPC-2581 handoff document `build --emit ipc2581` (RFC-015; contract in `docs/ipc2581.md`, schema gate needs `xmllint`), the module system (RFC-016: file-tree module paths, `use` imports, cross-package `pub` enforcement, E207-E209; references are REWRITTEN to fully-qualified names in `resolve.rs` — downstream maps are fq-keyed, `resolve::short()` for display), the library registry (RFC-017: `#[doc]` reference documents + `footprint` as a resolvable declaration kind — `footprint:` in parts is a symbol reference, never a string), and the pad/footprint format (RFC-018: `pad` declarations with a closed shape/layer/plating vocabulary, `pad N: Sym at (x, y)` placements + courtyard/silkscreen_ref in footprint bodies, the `Length`/`mm` unit as RFC-001's eleventh type, E805-E807 — pad-vs-device consistency checked at BUILD, empty footprints exempt as stage-one placeholders — and geometry projection into `out/footprints/*.kicad_mod` + IPC-2581 `Pin` elements; starter pads in `std/pads.cohdl`, remaining placeholders in `std/footprints.cohdl`), mechanical locating holes (RFC-022: `mount_hole N: PLATING at (x, y) diameter D`, disjoint from pad numbering, E810; RFC-023 extends it with an optional `shape:` reusing RFC-018's `PadShape` set plus a shape-dependent geometry field — `diameter D` for a circle, `size: (w, h)` for rect/oval, absent `shape:` defaults to circle), and array-typed instances (RFC-024, REDESIGNED from its own withdrawn first draft: `inst NAME: [Device; N]` declares ONE array-typed instance whose N elements are each fully real, addressed as `NAME[i]` — 0-based — EVERYWHERE an ordinary instance reference is valid: net members, `place`, `fn`-call args. A bare unindexed `NAME` is never a valid reference. Range/list fan-out `NAME[a..=b].PIN` / `NAME[i, j].PIN` survives as sugar over `NAME[i]`, still net-member-only. Elements are internally `NAME_0`…`NAME_{N-1}`; expanded in `check/expand.rs`, E202 for out-of-bounds, E211 for malformed/misplaced; does NOT solve daisy-chain wiring or arithmetic-derived `place` data), rotated pad placements (RFC-025: `pad N: Sym at (x, y) [rotate ANGLE]`, E811; KiCad 3-arg `(at x y angle)`, size never swapped), and back-side placement (RFC-026: `place … [rotate ANGLE] [side top|bottom]`, E1008; layout.json `"side"` only when bottom, IPC `layerRef="B.Cu"` + Xform mirror, pad x mirrors BEFORE rotation matching pcbnew Flip-then-orient; kicad_board.py must Flip only AFTER board.Add or headless pcbnew segfaults), and Quilter physics-constraint hints (RFC-027: seven structured attributes — `#[ground]` `#[high_current]` `#[impedance]` on nets, `#[bypass]` `#[crystal_oscillator]` `#[switching_converter]` `#[bga_fanout]` on insts — plus a `diff_pair(...) […]` physics bracket; E1009 structural / E110 unit mismatches; `build` emits the eight-file Quilter CSV set matching the supplied templates exactly — mA/nF/ohm/GHz scales, pad-number pins, multi-pad pins flatten to one row per pad — only when the design carries physics facts; RFC-028 lets `#[bypass]` target a bare `Pin`-typed fn parameter and the crystal/converter attributes take `Instance`-typed fn parameters, resolved per call site via `Binding::Pin`/`Binding::Instance` — one attribute inside `fn decouple` annotates every call site), package dependency versioning (RFC-029: a real `[dependencies]` manifest section — exact `X.Y.Z` versions ONLY, range syntax rejected permanently at parse — plus `cohdl.lock` recording each dependency's version AND sha256 content hash, re-verified on every check/build BEFORE any .cohdl parsing; hash mismatch = hard error. std is now an ordinary package (`cohdl.toml` + `src/`) — std is NOT special, and a package's version comes ONLY from its manifest's `[package] version`; directory names are convention, never mechanism (a registry family dir holds side-by-side versions in arbitrarily-named subdirs, discovered by reading their manifests; duplicate identity = hard error). `cohdl update [--dep NAME]` is the only sanctioned pin change (and migrates pre-RFC-029 manifests); `--std`/`COHDL_STD` survive as dev overrides behind the unsuppressable E1105 warning; E1101-E1108 in a new error block; `fmt` canonicalizes `[dependencies]` sorted; the pipeline's package set is explicit — `check_files_in_with_deps` — with dep files displayed `<name>/…`. Amendment (user-directed 2026-08-25): resolution walks the TRANSITIVE closure — every resolved package's own `[dependencies]` joins the compile and the lock records the closure; the root manifest's pin is the single authority (wins silently over any dep's pin), divergent dep pins with no root pin are the E1108 hard error (help: pin at the root to choose), check/build/LSP stay offline (E1102 names the requirer, "run `cohdl install`") while `install`/`update`/`add` fetch missing closure members, and under `--no-std`/`--std` a dep's std pin is skipped — std is settled outside the registry there, an escape of caller context, never of the name), the package registry (RFC-030: registry.cohdl.org — the RFC specifies the EXTERNAL CONTRACT only; the closed three-tier namespace is structural in the name itself — bare = CoHDL official, `@brand/name` = verified manufacturer, `@contrib/name` = community — validated client-side pre-flight AND server-side authoritative; CLI verbs `login/publish/add/remove/install/update` compose with RFC-029's lock mechanism unchanged — the SERVER's recomputed content hash is what cohdl.lock records; transport = the system `curl` (no crate dependency), archive = deterministic uncompressed tar (the RFC's ".tar.gz (or equivalent)"), cache = `~/.cohdl/registry` as an extra RFC-029 registry family; E1201-E1206 in their own block, distinct from E11xx by design — E1204 unreachable is NEVER conflated with E1103 hash mismatch; server implementation in `registry/` — Cloudflare Workers + D1 + R2 + KV + Workers Assets, Vite/TanStack/React UI, standalone like `editors/vscode`, root CI does not build it; a published version also carries `[package] license/description/repository` (per-version — the newest version is what "package-level" derives from) and an index of its RFC-017 `#[doc]` documents, which the package page renders through a no-raw-HTML Markdown subset. Registry policy: **`license` is REQUIRED to publish** — refused server-side (400 → E1202) and in the CLI pre-flight before packing, with no license-list validation (proprietary terms are fine; `""` is silence). None of these keys affect a verdict or an emitted byte), and the VS Code extension (RFC-019/DR-025: a real installable extension at `editors/vscode/` — TextMate grammar + `vscode-languageclient` wiring over `cohdl lsp`, `cohdl.path` setting; TypeScript/Node package with its own CI job and grammar-coverage test — ZERO compiler changes; the dependency-free constitution scopes the Rust crate, not this editor package; live-VS-Code session is a human checkpoint like KiCad). and silkscreen graphics for footprints (RFC-031: a `silkscreen { … }` footprint-body block — four closed primitives `line`/`circle`/`arc`/`polygon` plus two semantic marker shorthands `pin_1_marker near pad N shape dot|triangle` and `polarity_marker cathode_pin N shape band|arrow` that EXPAND to checked primitives in `emit::silk` — one expansion shared by both emitters so they cannot drift; E812; standoff is measured from the pad's EDGE, not its centre, or the mark would sit on the copper it marks; KiCad gets native `fp_line`/`fp_circle`/`fp_arc`/`fp_poly` on F.SilkS, and IPC-2581 gains its FIRST silkscreen output — every primitive reduced to a filled `Contour` polygon because `Features` accepts only a `StandardShape` and `Line`/`Arc` are `Simple`)., and typed logical composition (RFC-032: `subdesign` — a new declaration kind, a peer of `device`/`trait`/`fn`/`part`/`footprint`, resolved through RFC-016 unchanged. Explicit `Pin`-typed ports with RFC-002 obligations; RFC-007 generics and RFC-024 arrays reused VERBATIM at `subdesign name: Type<…>` use sites; retained hierarchy paths `Design::use::inst` feed RFC-005 unchanged; the container itself never becomes a component/designator/BOM row — ports resolve to phantom `(node, PORT)` members that merge net equivalence classes and are stripped at assembly. An internal `layout {}` is a DEFAULT the outer design transforms as one unit (`place use_site at … [rotate] [side]` — the RFC-025/026 mirror-x-then-rotate math via trig.rs, local rotation REVERSED on bottom) or overrides per instance through the dotted reach-in path (`place a.c_in at …`), the SOLE internals exception — `net`/`spec` stay behind ports. E1301-E1307; containment cycles checked at declaration (E1304, full cycle named); use sites in `fn` bodies rejected (E1307). Implementation: `check/subdesigns.rs` + `bodies.rs` shim (ports as Pin-params) + `expand.rs` (nodes in pass 1, port conns in pass 2, `compose_place` finalization). fmt deviation, ledgered: statement order is preserved (ports block canonicalized in place); layout-last is convention, not enforced reordering). RFC-001…032 are Accepted and implemented. Deviations from accepted text are ledgered in `docs/compliance-report.md`.