periscope/periscope/src/frontend/content/changelog.md

Changelog

What's new in Periscope.

2.74.0 — 2026-09-22 — Protocol packs from recovered PDFs (USB CTS, Type-C FTS, DVI 1.0, IEEE 802.3-2012 §2)

NUMERIC constraints now carry title, revision, section/table, and page from the recovered PDFs. USB 2.0 HS fills data rate / rise-fall / 1.5 kΩ pull-up / DCR from Electrical CTS v1.08; Zdiff stays UNKNOWN (CTS does not state 90 Ω). Type-C Rp/Rd/VBUS volts stay UNKNOWN (Functional Test Spec points at Cable and Connector tables). DVI 1.0 is a separate protocol from HDMI. IEEE 802.3-2012 Section Two fills 100BASE-TX cabling 100 Ω / 100 m / isolation and 100 Mb/s; 10BASE-T Clause 14 and 1000BASE-T Clause 40 are not in Section Two.

• [Changed] protocol_catalog.py + catalog.json; DVI recognition.
• [New] pytest tests/pcb/test_protocol_pdf_pack.py.

2.73.0 — 2026-09-22 — Protocol certification M6/M7 (USB-C / Ethernet / HDMI packs)

USB 2.0 (LS/FS/HS) is the protocol; USB Type-C is a connector/interface system; USB 2.0 over Type-C is the physical implementation. Type-C does not imply USB3 or USB4. Mini HDMI is a connector, not a protocol. Ethernet variants (10/100/1000/2.5G/5G/10G, SGMII, 1000BASE-X, 100BASE-FX, 10GBASE-R) are incomplete skeletons. All listed numeric fields stay UNKNOWN with needed_document (USB-IF / IEEE 802.3 / HDMI Adopter). No invented ohms, no typical-as-standard, no OpenEMS.

• [Changed] protocol_catalog.py + catalog.json; needed_document on UNKNOWN/MISSING_SOURCE.
• [Changed] USB/Ethernet/HDMI recognition: connector alone is not the protocol.
• [New] pytest tests/pcb/test_protocol_m6_m7.py.

2.72.0 — 2026-09-22 — Protocol certification M10 (catalog skeletons)

Catalog skeletons and required_checks for PCIe / CXL (logical vs physical), I2C, CAN, RGMII, plus missing high-speed processor ids (PCI, PCI-X, CCIX, OpenCAPI, UPI, DMI, Infinity Fabric, HyperTransport, UCIe). Numbers stay UNKNOWN / MISSING_SOURCE / PHY_DEPENDENT until an official cite is in the pack. pcb_relevant is YES or CONDITIONAL as appropriate. No invented ohms, no USB-IF fill, no OpenEMS.

• [Changed] protocol_catalog.py + committed catalog.json.
• [New] pytest tests/pcb/test_protocol_catalog_m10.py.

2.71.0 — 2026-09-22 — Protocol certification M9 (L3 channel + visible skip)

L3 CHANNEL certifier: structure for timing budget (TOTAL−USED=MARGIN), insertion loss, return loss, crosstalk, and complete channel. Numerical PASS/FAIL only when existing channel FACT (dB/ps) is already present — never invented S-parameters, never OpenEMS/FEM. Otherwise a visible skip: «Interfaccia X non certificata a L3 per mancanza di …». Internals (AXI/HBM) stay NOT_APPLICABLE. L0/L1 are not electrical. No M6 numeric packs.

• [New] protocol_l3.py; PE-PRT-L3-001 / PE-PRT-L3-002.
• [New] pytest tests/pcb/test_protocol_l3_m9.py.

2.70.0 — 2026-09-22 — Protocol certification M8 (DDR instance + L1 grouping)

DDR physical instances are controller-aware: one instance per memory device, DQ/DQS byte lanes separate from ADDRESS / COMMAND / CONTROL / CLOCK. Skew/length stay CONTROLLER_DEPENDENT / PHY_DEPENDENT / UNKNOWN — no universal mm/ps/ohm. HBM is package/interposer (pcb_relevant: NO); classic DDR PCB DQ rules are not applied. M6 numeric packs and L3 solver are not in this release.

• [New] protocol_ddr.py; L1 grouping reconstruction without PCB geometry.
• [New] pytest tests/pcb/test_protocol_ddr_m8.py.

2.69.0 — 2026-09-22 — Protocol certification M5 (Protocolli report)

Report section Protocolli: recognised instances, max level L0–L3 (L3 is a visible not-run skip, no solver), each check with measured / limit / margin / source / method, traceability chain net → group → physical interface → protocol → constraint → document → section. FAIL is listed first and styled as Error — not hidden under Warning (HubAudio). Visible skips stay on the page. No pack numbers, no invented Z, no OpenEMS.

• [New] protocol_report.py; Protocolli table UI.
• [New] pytest tests/pcb/test_protocol_report_m5.py; protocol-report.test.ts.

2.68.0 — 2026-09-22 — Protocol certification M4 (L2 electrical)

L2 ELECTRICAL certifier: impedance, termination, voltage/levels, rise/fall when sources exist. Z only from datasheet / stackup / fabricator / cited pack — never invented 90 Ω USB. USB-IF/IEEE only if the pack has a cite. Silicon cross is max PCB × PHY subset when datasheet windows exist. Length is not delay. No L3/OpenEMS. L0/L1 are not electrical. RECOMMENDED never FAIL. MISSING_SOURCE / UNKNOWN when cite is absent. Visible skip when Z cannot be obtained.

• [New] protocol_l2.py; PE-PRT-L2-001 / PE-PRT-L2-002.
• [New] pytest tests/pcb/test_protocol_l2_m4.py.

2.67.0 — 2026-09-22 — Protocol certification M3 (L1 geometric)

L1 GEOMETRIC certifier: length, topology, vias, stubs, layer, grouping. Geometric skew only vs NUMERIC millimetre or an explicit DESIGN LIMIT. Otherwise UNKNOWN / VENDOR_DEPENDENT / CONTROLLER_DEPENDENT / PHY_DEPENDENT — never invent mm/ps. L1 is not electrical. No L2/L3. RECOMMENDED never FAIL. Internal interfaces stay NOT_APPLICABLE. Missing DQ/DQS grouping is a visible skip, not PASS.

• [New] protocol_l1.py; PE-PRT-L1-001 / PE-PRT-L1-002 / PE-PRT-L1-003.
• [New] pytest tests/pcb/test_protocol_l1_m3.py.

2.66.0 — 2026-09-22 — Protocol certification M2 (L0 structural)

L0 STRUCTURAL certifier: nets must exist and connect at least two components. FAIL only for missing MANDATORY structure. AXI4 / internal interconnects are NOT_APPLICABLE (not FAIL). RECOMMENDED never FAIL. No L1–L3, no invented ohms/mm/ps.

• [New] protocol_l0.py; PE-PRT-L0-001 / PE-PRT-L0-002.
• [New] pytest tests/pcb/test_protocol_l0_m2.py.

2.65.0 — 2026-09-22 — Protocol certification M1 (instance recognition)

physical_bus_instance from declaration / silicon / part / pin / net / pairs. Output: instances, signal groups (DIFF pair, byte lane, clock/address), confidence. Ambiguity is REVIEW, never FAIL. AXI4 internal is recognised with pcb_relevant: NO and no PCB nets. No L0–L3 certifier. No invented ohms.

• [New] protocol_recognize.py; report Protocolli lists recognised instances or stays empty.
• [New] pytest tests/pcb/test_protocol_recognize_m1.py (USB/DDR fixtures; AXI has no nets).

2.64.0 — 2026-09-22 — Protocol certification M0 (catalog, no numbers)

Versioned JSON protocol pack + Python loader/validator. Catalog skeletons for USB2 / USB-C-USB2 / 100BASE-TX / HDMI (connector distinct) / DDR / LPDDR / HBM / HyperBus / QSPI-octal / eMMC / UFS / AMBA / Wishbone / Avalon / TileLink / PCIe-CXL. Constraints without an official cite are UNKNOWN / CONTROLLER_DEPENDENT / PHY_DEPENDENT / MISSING_SOURCE — no invented 90/100/50 Ω. logical_protocol_id ≠ physical_interface_id. pcb_relevant is YES|NO|CONDITIONAL. RECOMMENDED is not FAIL-mandatory. Typical-as-standard is rejected by the parser. Report section Protocolli is empty (nessun protocollo riconosciuto). Recognition and L0–L3 certifiers are not in this release.

• [New] protocol_catalog.py, protocol_data/catalog.json, schema 1.0.0.
• [New] protocol_certification on ValidationReport; UI section Protocolli.
• [New] pytest tests/pcb/test_protocol_catalog_m0.py.
• [Fixed] Native periscope/src wins over inherited periscopex on the package path.

2.63.5 — 2026-09-22 — AF trace analysis (trigger, cascade, visible skips)

PCB exam adds AF trace analysis after unchanged run_pcb_checks (SI/HF stay). Trigger is λ/10 or tr/(6 tpd) from FACT only. Differential pairs are one unit. Z0/Zdiff only vs a datasheet window. Missing tr/f/εr/stackup/Z target/via span is a visible INSUFFICIENT finding («Pista ad alta frequenza non controllata per mancanza di …»), not invented 50/90 Ω. Trigger false → no AF finding. Numerical cascade is lossless RLGC sections (ImpedenceFinder Z0); not OpenEMS/FEM. Python. PE-AF-001 AI path unchanged.

• [New] check_af_traces / af_trigger / af_rlgc; pipeline stage af_trace.
• [New] PE-AF-002 visible skip; PE-AF-020…061 on triggered nets.
• [New] Via (layers …) parsed on LayoutVia (span; size is not a track).
• [Changed] Changelog / PCB progress lists AF trace before AF+AI.

2.63.4 — 2026-09-22 — Report Error group, J2, U18 max severity

The findings tree always has an Error folder when ERROR findings are visible. Group badge is the worst child (U18 PE-PLC-002 ERROR is not labeled WARNING). Connectors (J2) sit in the same sidebar as U*. PE-PLC stays in the PCB exam bucket. No auth change.

• [Fixed] Status folders Error / Warning / Info; severity = max of children.
• [Fixed] J2 and other non-U refs listed with ICs.
• [Fixed] isPcbExamFinding matches layout findings (PE-PLC with PE-BOM).

2.63.3 — 2026-09-22 — Module die, truncated QFN pintable, QFN=VQFN

HubAudio software leftovers on PE-BOM-010/011: a WROOM module is not the ESP32 die pintable; a QFN-48 land is not wrong because extraction stopped at pins 1–24; VQFN-24 4×4 is the same QFN family as datasheet QFN-24. Extra signal pads above the declared QFN-n still ERROR. Pad ≠ via. Kelvin unchanged.

• [Fixed] PE-BOM-011 skips die-pintable extras on WROOM/WROVER module footprints (U11).
• [Fixed] PE-BOM-011 skips QFN-n pads the pintable never listed (U12 25–48).
• [Fixed] PE-BOM-010 treats VQFN/WQFN/HVQFN as QFN (U19).

2.63.2 — 2026-09-22 — PE-BOM-011 joins pins by name, not pin_count

Datasheet pin_count and PCB pad cardinality are incommensurable (USB-C 16P vs SH/mount/EP). PE-BOM-011 joins the pintable × KiCad .kicad_mod × embedded PCB pads by pin name. USB-C A5/B5 are CC pins, not EP. Missing pintable is a skip, never ERROR on pin_count=16. The library footprint is checked against the datasheet; lib vs embedded PCB is a separate mismatch. AI still extracts the table and runs review/class/SI — it does not count pads. Pad ≠ via.

• [Fixed] PE-BOM-011 no longer treats [A-Z]\\d+ as EP (HubAudio J2 16 vs 1 SH).
• [Fixed] Scalar package_info.pin_count is not an ERROR authority.
• [Changed] Named join: datasheet pintable vs lib vs PCB; SH/EP/mount classified first.

2.63.1 — 2026-09-21 — Library component from PDF; AF+AI beside PCB checks

Library import registers a component (not only a PDF blob) with no exam. AF Board+AI is a pipeline section after unchanged run_pcb_checks (PE-SI / HF line stay in 2.62.1).

• [Fix] POST /api/library/datasheets writes an IC inbox card or a passive/discrete model. Empty pintable never lands in library/extracted/.
• [Fix] PCB pipeline stage af_ai calls append_investigated beside run_pcb_checks. Duplicate SI clones are not double-counted. PE-AF-001 stays additive.
• [New] Report tree root “AF Board + AI”. Progress step between deterministic checks and PCB AI exam.

2.63.0 — 2026-09-21 — Library as its own product door

Standalone /library + /api/library: browse, add a datasheet PDF without an exam, update a component card. Datasheet prelim stays on the analysis path. Tests grouped datasheet → library → schematic → PCB → AF+AI (extra HF flags, then deterministic investigate). Rust criteria documented; no rustup. FEM out. DRC remains KiCad.

• [New] POST /api/library/datasheets stores a PDF by MPN with no project id.
• [New] GET/PUT /api/library/components/{type}/{mpn} for extracted cards.
• [New] Library page import form; empty library no longer says “run a review”.
• [New] investigate_hf_hypotheses (PE-AF-001) — AI Z0 flag without stackup is INSUFFICIENT, never 50/90 Ω. Existing run_pcb_checks unchanged.

2.62.1 — 2026-09-21 — PCB analysis remainder (Phase B)

Stackup vs fab spec, via current with datasheet I (no IPC via chart), ESD pad distance TVS–connector, USB-PD contract, PoE isolation voltage, antenna keepout/matching, PDN Z(f). Same pipeline and finding quality as 2.61.2 / 2.62.0. Skip if no evidence. Not DRC. Not FEM.

• [New] PE-STK-001 board copper thickness vs sourced fab stackup (never 1 oz).
• [New] PE-VIA-002 I + via count/drill FACT; IPC via ampacity is not applied.
• [New] PE-ESD-002 TVS–connector pad distance (via ≠ pad); INFO if no mm.
• [New] PE-PD-001 USB-PD only with a PD controller (not USB2 Rd).
• [New] PE-POE-004 isolation voltage only from a sourced number.
• [New] PE-ANT-001/002 antenna keepout and matching if an antenna exists.
• [New] PE-PDN-001 Z(f) only with frequency-domain FACT; SI Z0 is not PDN.

2.62.0 — 2026-09-21 — HF lines/buses in PCB checks (Phase A)

USB / Eth / DDR / MIPI / PCIe / HDMI / LVDS / HF clock in run_pcb_checks at the same finding quality as 2.61.2. Pair integrity: stub (track only; via ≠ pad ≠ zone), reference-split under the line, BOM termination. CPU data/address/control and FPGA only if that device is on the graph. Skip if no evidence. Not DRC. Not FEM. Datasheet millimetres only; no invented Z/I.

• [New] PE-SI-007 dangling track stub vs datasheet mm (INFO if no mm).
• [New] PE-SI-011 GND-pour gap under an HF pair (REVIEW; skip without stackup/zone).
• [New] PE-SI-012 BOM series/parallel terminator FACT (skip if none).
• [New] PE-DDR-001…003 DRAM class / CK-DQS-DQ / VTT only if DRAM present.
• [New] PE-CPU-001…004 parallel CPU bus only if D/A/control exist.
• [New] PE-FPGA-001…003 FPGA class / config flash / VCCINT·VCCIO only if FPGA present.
• [Changed] bus_class adds MIPI and leftover HF clocks; XTAL/OSCIN stay out.

2.61.2 — 2026-09-21 — Certifiers only for connectors on this board

USB-C / RJ45 / PoE / DDR3 are the method, not a catalog. If this graph has a USB-C receptacle, run USB-C questions. If it has RJ45, run Ethernet. PoE only with PoE evidence — never because RJ45 exists. No connector → no that certifier (not N/A). HubAudio has USB-C USB2 + PoE 10/100 MagJack and no DDR: no DDR findings. Skip-I (2.61.1) unchanged. No FEM, no via IPC, no invented I/Z/PoE/SuperSpeed.

• [Fixed] Absent USB-C / RJ45 / PoE no longer emit INFO N/A.
• [Fixed] Bare RJ45 is Ethernet only; PoE is skipped without PoE evidence.

2.61.1 — 2026-09-21 — Skip trace-width vs current without datasheet I

PE-PWR-001 (and PE-VIA-001) run only when the datasheet reports I_load / Imax / I_abs. Missing that number is a skip — not INFO INSUFFICIENT, not a typical USB 500 mA, not Iout_max-as-load. USB-C / Ethernet / PoE class certifiers still have no current/ampacity check. No via IPC table. No FEM.

• [Fixed] PE-PWR-001 / PE-VIA-001 skip when datasheet current is absent.
• [Fixed] Imax / I_abs accepted for width; Iout_max is still not load.

2.61.0 — 2026-09-21 — Interface class certifiers (USB-C, Ethernet, PoE)

Dedicated per-interface certifiers (deterministic + AI explanation). Not generic SI. USB-C: CC1/CC2, Rp/Rd 5.1 kΩ, VBUS/GND, SuperSpeed only if the class is USB3. Ethernet: 10/100 vs GbE; magnetics required for GbE. PoE only with PoE evidence — a bare RJ45 is N/A, never invented PoE. Missing generation/class/ohms → INSUFFICIENT. DDR3 and via IPC ampacity are out of this slice. No FEM.

• [New] PE-USBC-001…005 USB-C class + CC + Rd/Rp + VBUS/GND + SuperSpeed gate.
• [New] PE-ETH-001…004 Ethernet 10/100 vs GbE, TX/RX pairs, GbE magnetics, Bob Smith REVIEW.
• [New] PE-POE-001…003 PoE evidence / class / isolation; bare RJ45 is N/A.
• [New] Taxonomy connector.rj45. AI prompts must not invent PoE or SuperSpeed.

2.60.11 — 2026-09-21 — PCB software false positives

KiCad 9/10 boards have no numeric net table ((net "GND") on pads/tracks). The net index is filled from those names. PE-LAY-004 counts copper on tracks, vias, and pours, skips unconnected-(…) NC nets, and matches /sheet/ prefixes — it must not report ~139 “unrouted” nets when KiCad DRC unconnected_items is ~30 (islands on already-named nets). Missing I_load is INSUFFICIENT on PE-PWR-001 / PE-VIA-001. Thermal/EP extra pads are not PE-BOM-011 ERROR. Voltage abs-max binds to the named pin. Kelvin ignores CRS/IN±. EMI/PI skip NC nets. LQW18AN murata_lqw_inductance decodes nH. FB/BLM beads are ferrite; DCR is not Z. Thinking reasoning_content echo unchanged.

• [Fixed] Empty LayoutGraph.nets on KiCad 9/10 name-only nets.
• [Fixed] PE-LAY-004 zone/via/NC join vs DRC unconnected order of magnitude.
• [Fixed] PE-PWR-001 / PE-VIA-001 emit INSUFFICIENT without I_load.
• [Fixed] PE-BOM-011 EP/thermal extras; PE-BOM-012 pin-bound abs-max.
• [Fixed] PE-KEL-001 / PE-EMI-001 / PE-PI-001 NC and IN± / CRS false positives.
• [Fixed] LQW decoder; BLM/FB not typed as a DCR resistor.

2.60.10 — 2026-09-21 — Hierarchical sheets + DeepSeek thinking echo

Apri progetto still skips .history / .git / backups so the folder pick does not hang. It now keeps every linked schematic: all *.kicad_sch next to the .kicad_pro, plus Sheetfile / (sheet / file= children in a subfolder. Not only HubAudio.kicad_sch.

DeepSeek thinking-only review turns (HubAudio U11/U12/U38) 400'd because the next request dropped reasoning_content. The native client echoes it on the follow-up. Retry failed IC reviews after this deploy.

• [Fixed] USB / Codec / POWER (and other hierarchical modules) are ingested with the root sheet.
• [Fixed] Nested sheet paths are followed; .history copies are ignored.
• [Fixed] Thinking-mode reasoning_content is passed back on subsequent turns.

2.60.9 — 2026-09-21 — Apri progetto does not walk forever

After folder permission, 2.60.8 kept Next disabled because showDirectoryPicker then recursed dirHandle.entries() / getFile() through the whole tree (HubAudio .history is ~2000 files). We only read the project directory: .kicad_pro, .kicad_sch, .kicad_pcb. Timeout shows an error instead of a spinner forever. Next enables when a .kicad_pro is in.

• [Fixed] Folder pick no longer hangs on nested dirs / permission / giant trees.
• [Fixed] Next on step 1 when .kicad_pro is present.

2.60.8 — 2026-09-21 — Folder picker, not Carica file dialog

Apri progetto opened the Mac file list (Carica, no row selected) because the control was a React <input type="file" accept=""> without a working webkitdirectory. Empty Carica then looked like “no .kicad_pro”. It now uses showDirectoryPicker (Chrome) or a hidden input created with webkitdirectory=true and no accept. Cancel/empty pick is ignored.

• [Fixed] One folder gesture; .kicad_pro from name or webkitRelativePath.

2.60.7 — 2026-09-21 — Detect HubAudio.kicad_pro after folder pick

Apri progetto was rejecting the folder that actually contains HubAudio.kicad_pro. Safari/macOS folder pick often puts the real name in webkitRelativePath while File.name is the stem without .kicad_pro, and React was not setting webkitdirectory on the input. We match name or relative path, sniff JSON if the suffix is missing, and set the folder attribute on the DOM.

• [Fixed] Folder that contains HubAudio.kicad_pro is accepted.
• [Fixed] webkitdirectory set via DOM setAttribute so Safari/Chrome recurse.

2.60.6 — 2026-09-21 — Apri progetto KiCad (cartella)

Un controllo: Apri progetto KiCad. Si sceglie la cartella dove sta il .kicad_pro. Carichiamo root + fogli hierarchical .kicad_sch e il .kicad_pcb fratello. Niente netlist, niente CSV. MPN solo da proprietà schematico (PNM/MPN/Value). Uno .asc PADS vecchio nella stessa cartella è ignorato.

• [New] Folder picker / drop della cartella progetto.
• [Fixed] .kicad_pro da solo non finge di avere lo schematico.
• [Fixed] Connectivity dallo schematico, non da un netlist stantio (niente U13 fantasma).

2.60.5 — 2026-09-21 — Hierarchical schematic MPN when BOM omits a ref

graph_build reads PNM on .kicad_sch symbols (all nested sheets). If the CSV has no row for a designator, the child-sheet PNM/MPN/IC Value still fills mpn. Empty child-sheet fields stay empty — no invented part numbers. A sibling .kicad_sch next to a PADS netlist is consulted the same way.

• [Fixed] KiCad property PNM is an MPN alias on symbols, not only on BOM CSV.
• [New] Hierarchical fixture: U13 on a child sheet with PNM, omitted from CSV, still gets TPD2E007DCKR.

2.60.4 — 2026-09-21 — KiCad PNM and honest missing-MPN skips

KiCad BOM column PNM is an MPN alias. Grouped Reference lists still split. IC Value fills MPN when PNM is blank (PCA9534ARGTR). Netlist-only U* with no BOM row are INSUFFICIENT_EVIDENCE (quoted Value/Footprint), not a silent drop and not an invented part number.

• [Fixed] Progress skip text no longer says “no MPN in BOM” when the designator is absent from the CSV.
• [New] HubAudio KiCad BOM fixture: PNM header, U2/U3 Value fallback, L4 bead PNM, U13…U39 not invented.

2.60.3 — 2026-09-21 — Ferrite Z from library MPN datasheet

graph_build looks up the bead MPN PDF in project uploads/datasheets and library/datasheets (named files and blob refs). Z is filled only when the PDF states impedance (e.g. 120 Ω @ 100 MHz). Missing Z stays omitted; graph_build does not abort.

• [Fixed] HubAudio-style beads recover impedance_ohm from the manufacturer PDF, not from inventing Z or stuffing ohms into value_henries.
• [New] Tests: MPN + datasheet PDF fills Z; MPN + PDF without Z does not invent and still loads.

2.60.2 — 2026-09-20 — Ferrite Z from datasheet, no graph_build abort

Beads with an MPN pull impedance_ohm from the datasheet or a quoted N ohm @ freq string. Missing Z after that is INSUFFICIENT, not a crash. Ohms are never written to value_henries. Leftover dependency validator no longer requires Z.

• [Fixed] graph_build loads DCR-only beads; leftover ferrite bead requires impedance_ohm removed.
• [Changed] Ferrite Z recovered from datasheet PDF / quoted value; extract-specs skill 1.15.0.

2.60.1 — 2026-09-20 — Ferrite bead without Z still loads

Ferrite beads that only have current/DCR validate. Missing impedance_ohm is not invented and does not crash graph_build. Other inductors still need value_henries.

• [Fixed] InductorSpecs no longer requires Z on passive.ferrite_bead.
• [Changed] Bad models/*.json are skipped with a log, not a pipeline abort.

2.60.0 — 2026-09-20 — Incomplete PCB exam and owner project delete

Unfinished placing/routing still uses MODE=pcb. Parser and checks run on partial layouts; missing copper is INSUFFICIENT or skip, never invented millimetres. Via≠Pad unchanged. Dashboard owners can delete a project after a confirm dialog.

• [Changed] Decoupling proximity uses routed copper only (PE-PLC-005 when unrouted).
• [New] PE-LAY-004 INFO when pad nets have no tracks.
• [New] Owner-only DELETE /api/projects/{id} with confirm dialog; collaborators get 403.

2.59.0 — 2026-09-20 — Docker without unused PinScope product tree

Images copy periscope/src plus leftover seams (shadcn/Clerk/billing, unused LLM providers, GCS, landing png/gif) and vendor/. They do not copy the inherited PinScope product tree. dependency/ stays in git. Audit: periscope/src/docs/development/DEPENDENCY_AUDIT.md. Pad≠Via unchanged.

• [Changed] Backend/frontend Dockerfiles drop wholesale COPY periscope/dependency/{backend,frontend}.
• [New] Boot test runs FastAPI with PYTHONPATH=periscope/src only.

2.58.0 — 2026-09-20 — Native JWT middleware and useAuthApi

backend/middleware/auth.py and frontend/src/hooks/use-auth-api.ts are original Periscope code. Skip paths, Bearer/query token, Clerk RS256 leftover, and local HS256 (local_jwt.decode_token) stay the same HTTP contract. routers/auth.py, data/auth/users, and AUTH_JWT_SECRET are unchanged. Pad≠Via unchanged.

• [New] Request JWT verification rewrite under periscope/src.
• [New] useAuthApi rewrite wires setTokenGetter from the optional-auth seam.
• [Changed] App stamp 2.58.0; login identifiers and password hashes are not rotated.

2.57.0 — 2026-09-20 — Native package.json, requirements, and unused Docker copies

Frontend package.json (periscope-web) and lockfile, components.json, and backend requirements.txt overlay from periscope/src. Docker installs those files from src. Unused PinScope public blobs (Faradworks logo, power-tree.gif, create-next-app SVGs) are dockerignored. EDA logos and KiCad tutorial examples live under src public/. Landing report.png / datasheet.gif / derating.png stay in dependency/ until native UI captures exist. Auth/JWT still inherited. Pad≠Via unchanged.

• [New] Native npm package name periscope-web at 2.57.0 with the same Next 16 scripts and dependency set.
• [New] Native pip requirements (DeepSeek stack first; leftover GCS/Gmail/LLM extras remain optional).
• [Changed] Frontend Docker npm ci and backend pip install read src manifests.
• [Changed] .dockerignore drops unused PinScope marketing blobs from the image.

2.56.0 — 2026-09-20 — Native taxonomy JSON and local skills overlay

Component taxonomy JSON and DeepSeek skills/*/SKILL.md (plus local validate.py / schema) live under periscope/src. repo_paths prefers src; Docker copies dependency then src; compose mounts src/taxonomy. Manifest 1.14.0. App favicon.ico matches the Periscope mark. Auth/JWT, package.json, landing png/gif unchanged. Pad≠Via unchanged.

• [New] Periscope taxonomy catalog in periscope/src/taxonomy (same subtype keys and spec names).
• [New] Local extraction skill prompts rewritten; no Anthropic Console upload.
• [Changed] Compose no longer bind-mounts dependency/taxonomy over /app/taxonomy.

2.55.0 — 2026-09-20 — Native Next overlay config and CSP seam

next.config.ts, ESLint/PostCSS/tsconfig, and lib/csp-hosts.ts overlay from periscope/src/frontend. backend/middleware/__init__.py is a native package marker. JWT stays in inherited middleware/auth.py. package.json unchanged. Legal markdown already Periscope; changelog kept. Pad≠Via unchanged.

• [New] Next CSP/redirect/pdfjs overlay rewrite; login still maps to /sign-in.
• [New] CSP host lists stay empty for Clerk/Stripe on self-host.
• [New] Middleware package marker rewrite; auth module not re-exported.

2.54.0 — 2026-09-20 — Native leftover frontend widgets and tokens

PDF sheet, theme provider/toggle, file drop zone, reviewed-finding hooks, and globals.css are original Periscope code in periscope/src/frontend. Inherited copies stay on disk. shadcn, Clerk, billing, Reddit pixels, proxy.ts, and auth/JWT are unchanged. Pad≠Via unchanged.

• [New] Datasheet sheet, theme chrome, and upload drop-zone rewrite.
• [New] Reviewed-finding localStorage hooks rewrite (legacy key migrate kept).
• [New] App token stylesheet rewrite; light/dark oklch values unchanged.

2.53.0 — 2026-09-20 — Native site, legal shells, OG, and Next BFF

lib/site.ts, version.ts, report-export.ts, legal page chrome, Open Graph images, and the local /api/projects /api/report/[id] /api/graph/[id] BFF routes are original Periscope code in periscope/src/frontend. Inherited copies stay on disk. Clerk proxy.ts, shadcn components/ui/*, billing, Reddit pixels, and auth/JWT are unchanged. Pad≠Via unchanged.

• [New] Site identity, version stamp, and findings Excel export rewrite.
• [New] Legal/changelog/file-guide shells and OG image rewrite.
• [New] Local Next BFF JSON routes rewrite; Clerk proxy stays the open-core seam.

2.52.0 — 2026-09-20 — Native leftover frontend overlay

Dashboard, project, report, progress, admin, feedback, marketing, and the HTTP client (lib/api.ts, types.ts) are original Periscope UI in periscope/src/frontend. Docker still copies OSS then src. Routes, API contracts, and layout are unchanged. Billing/Clerk/analytics stay imported seams. Auth/JWT untouched. Pad≠Via unchanged.

• [New] Frontend types + API client rewrite (export names preserved).
• [New] App and marketing pages rewrite so overlay wins without a product restyle.

2.51.0 — 2026-09-20 — Native Settings, FastAPI app, leftover routers

config.py, main.py, pipeline_worker.py, and leftover HTTP routers (admin, contact, deps, feedback, pipeline, projects, reports, survey) are original Periscope code in periscope/src. Inherited copies stay on disk. routers/auth.py is unchanged. JWT middleware remains leftover. Frontend product chrome is still the Docker overlay (src pages already win for library/PCB/placement/sign-in). Pad≠Via unchanged.

• [New] Settings rewrite: DeepSeek-only routing; Anthropic env names coerced or ignored.
• [New] FastAPI entry + worker rewrite; worker still must not import backend.main.
• [New] Project/pipeline/report/admin HTTP surface rewrite.

2.50.0 — 2026-09-20 — Native analysis pipeline and leftover checks

pipeline.py, projects.py, email.py, purple_parts.py, and leftover analysis modules (resolve_passives, derating, bom_summary, pin_mux_check, led_current_check, pin_function_tokens, plus validate/validation_tools aliases) are original Periscope code in periscope/src. Inherited copies stay on disk. Live path is still job_workspace / datasheet_extract / review_session. Auth untouched. Pad≠Via unchanged.

• [New] Analysis job rewrite: BOM parse, extract, graph, review; LCSC column backstop only.
• [New] Project meta writes follow owner_user_id (Emmaforo JWT prefix).
• [New] Exact-MPN LCSC reverse lookup; prefix hits rejected.

2.49.0 — 2026-09-20 — Native normalize, cross-IC dedupe, billing seam

normalize_findings.py, dedupe_findings.py, and billing_hook.py are original Periscope code in periscope/src. Inherited copies stay on disk. Self-host get_billing() is NullBilling (no Stripe at import). Downgrade-only clamp unchanged (U2-001 / Emmaforo UART).

• [New] Per-IC normalize builder + tool schema rewrite; fail-soft to originals.
• [New] Cross-IC dedupe rewrite (CH340E↔MCU interface collapse).
• [New] Billing seam rewrite; credits stay lazy behind billing_enabled.

2.48.0 — 2026-09-20 — Native models, schematic parsers, taxonomy loader

models.py, parsers.py, parsers_edif.py, and taxonomy.py are original Periscope code in periscope/src (not overlay stamps). Inherited copies stay on disk. Taxonomy JSON is still repo_paths.taxonomy_dir() → periscope/dependency/taxonomy. Native parsers_kicad.py / parsers_kicad_pcb.py (via≠pad) unchanged.

• [New] Periscope Pydantic contracts: disjoint LayoutPad / LayoutVia / LayoutSegment / LayoutZone.
• [New] PADS/BOM dispatch and EDIF 2.0.0 ingest rewrite; KiCad schematic still native.
• [New] Taxonomy loader rewrite: TAXONOMY_DIR = taxonomy_dir().

2.47.0 — 2026-09-20 — Native DesignGraph builder

backend.periscopex.graph is original Periscope code in periscope/src (not an overlay stamp). Inherited dependency/.../graph.py stays on disk. PCB via≠pad remains in native parsers_kicad_pcb.py.

• [New] Periscope graph.py: classify refs, infer net type/voltage, BOM+netlist+optional .kicad_pcb nets → DesignGraph.

2.46.0 — 2026-09-20 — Remove PinScope overlay copies from periscope/src

Stamped near-identical copies of inherited modules are gone from periscope/src. Docker still copies dependency/ then native src. Tests load graph/parsers/models/pipeline from periscope/dependency again. Native work stays: finding engine, PCB/placement, review session, job workspace, datasheet extract, KiCad PCB via≠pad parser, Periscope mark, local JWT, pinscope_compat.

• [Changed] Deleted overlay copies of graph, models, parsers, leftover services, main/routers, skills JSON, taxonomy JSON from periscope/src.
• [Changed] Overlay stamp tests removed. Inherited files remain in periscope/dependency/ (not empty-deleted).

2.45.0 — 2026-09-20 — Overlay leftover app entry, routers, and jobs

main.py, config.py, middleware/auth.py, leftover routers/* (not native auth/impedance), pipeline_worker.py, job_runner, event_bridge, projects, and admin_settings resolve from periscope/src. Inherited copies stay on disk. Auth users and AUTH_JWT_SECRET unchanged.

• [New] src overlay of the leftover FastAPI entrypoint, settings, JWT middleware, and HTTP routers the live app still imported from dependency/.
• [New] src overlay of pipeline_worker and job/project settings services.

2.44.0 — 2026-09-20 — Overlay leftover services src still imported

Pipeline helpers still pulled from dependency/ (api_logs, normalize_findings, dedupe_findings, billing_hook, datasheet_store, cost_estimator, storage, purple_parts, email, digikey) plus LLM factory / types / base now resolve from periscope/src. Inherited copies stay on disk.

• [New] src overlay of leftover backend/services modules the live pipeline/review path still imports.
• [New] src overlay of services/llm/{factory,types,base}.py (DeepSeek provider stays native; Anthropic/Gemini files stay in dependency).

2.43.0 — 2026-09-20 — Overlay leftover PinScope modules src still imported

utils, resolve_passives, derating, bom_summary, pin_mux_check, led_current_check, pin_function_tokens, plus live analysis validate / validation_tools / pipeline / validation / extraction (fallback), resolve from periscope/src. Skills (extract-*) and taxonomy JSON are copied to periscope/src/{skills,taxonomy}; Docker overlays them after dependency/. Inherited files stay on disk.

• [New] src overlay of the leftover periscopex helpers analysis/PCB still import.
• [New] src overlay of services/{pipeline,validation,extraction}.py (re-exports job_workspace unchanged).
• [New] periscope/src/taxonomy/*.json and periscope/src/skills/extract-*.
• [Changed] repo_paths prefers src (then /app, then dependency) for taxonomy and skills.

2.42.0 — 2026-09-20 — Native graph/parsers/models/taxonomy overlay + Periscope mark

Graph builder, PADS/EDIF/BOM parsers, Pydantic models, and taxonomy loader resolve from periscope/src. Inherited copies stay in periscope/dependency/ (not deleted). KiCad schematic parser was already native. Taxonomy JSON still lives in the inherited taxonomy/ tree. New Periscope mark (periscope/lens, not the PinScope CPU glyph) at the existing favicon and PWA pixel sizes.

• [New] periscope/src/backend/periscopex/{graph,models,parsers,parsers_edif,taxonomy}.py overlay Docker/src-first imports.
• [Changed] taxonomy.TAXONOMY_DIR uses repo_paths so src overlay still reads dependency/taxonomy.
• [New] Brand mark: public/brand/periscope-mark.svg, favicon_io 16/32/180/192/512, header PeriscopeMark.

2.41.0 — 2026-09-20 — Native job workspace for PCB and placement

pcb_pipeline and placement_pipeline no longer import PinScope pipeline.py. Workspace download/upload and the in-memory event broker live in periscope/src (job_workspace.py). Analysis run_pipeline still lives in dependency/ and re-exports the same singleton so pipeline_worker.set_broker keeps PCB SSE on the GCS event log. Parsers/graph unchanged. pipeline.py not deleted.

• [New] backend.services.job_workspace: PipelineWorkspace, EventBroker, set_broker.
• [Changed] PCB/placement import job_workspace; pipeline.py re-exports the native types.

2.40.0 — 2026-09-20 — Fase C3: native datasheet extraction

Pipeline pintable/pattern/specs/auto-resolve run from periscope/src (datasheet_extract.py): DeepSeek + local SKILL.md, no Anthropic Console skill ids. Inherited extraction.py stays in dependency/.

• [Changed] pipeline.py and project LCSC resolve import datasheet_extract.
• [Changed] Extract stages pin the DeepSeek provider.

2.39.1 — 2026-09-20 — src no longer imports PinScope review loop

After 2.39.0 live smoke (Emmaforo ERROR 2 / WARNING 12 / INFO 18), native modules are the only review path from periscope/src. PinScope validate.py / validation_tools.py remain on disk.

• [Changed] PCB review and deterministic checks import review_parse / constraints_lookup / review_session, not validate.py.
• [Changed] Tests exercise the native parser and graph tools.

2.39.0 — 2026-09-20 — Fase C2: native DeepSeek review loop

Live per-IC review runs from periscope/src (review_session.py, parse, graph tools). PinScope validate.py / validation_tools.py stay in dependency/ as fallback; they are not deleted. LLM findings stay REVIEW; recommended never ERROR. AGPL unchanged. No parser/graph rewrite. No auto-place.

• [Changed] review_ic_async is native (backend.services.review_session); inherited copy kept as _inherited_review_ic_async.
• [New] review_parse.py (FACT/REQUIREMENT/INFERENCE + complete_findings ids), review_tools.py, review_context.py, constraints_lookup.py.
• [Changed] finding_engine.complete_finding remains the clamp after submit_review.

2.38.0 — 2026-09-20 — Physical split: periscope/src vs periscope/dependency

Split the checkout so native Periscope and inherited PinScope are separate trees. No finding-engine rewrite. AGPL LICENSE stays at the repo root. The GitHub fork is not detached.

• [Changed] Native modules live under periscope/src/ (PCB, placement, finding clamp, DeepSeek, local auth, plugin, Dockerfiles).
• [Changed] PinScope-derived modules live under periscope/dependency/ (graph, parsers, validate.py, pipeline, OSS Next shell, skills, taxonomy, simple_project).
• [Changed] Docker overlays dependency then src. Local backend package merges both trees. Do not delete the inherited tree; Fase C replaces modules incrementally.

2.37.1 — 2026-09-20 — PCB not_reviewed is board ICs, not the shared library

Emmaforo showed 20 “components not reviewed” that were other projects’ 1.5–1.7 extracts (LAN8720A, W25Q, …). BOM ICs were already 1.13.0 and were reviewed.

• [Fixed] si_extract_needed_skips only flags ICs on this graph. Shared library/extracted cache is not not_reviewed.

2.37.0 — 2026-09-20 — SI bus gate (EN RC ≠ USB series R)

Datasheet SI facts apply only to the bus in the quote. ESP32 EN RC 10 kΩ / 1 µF is not a USB D+/D− series resistor. USB without a library Z number stays measurement-only (88 Ω), not a 90 Ω FAIL. Coverage: PHY+RJ45 MDI, MAC–PHY RGMII/SGMII, DDR3, USB-C SuperSpeed.

• [Fixed] PE-SI-009 (and other SI kinds) require net_class / quote bus match; strap/EN RC is skipped.
• [Changed] bus_class: usb2 / usb3 / eth_mdi / rgmii / sgmii / ddr3_*.
• [Changed] PE-SI-010 is per bus with no impedance FACT (not silenced by an unrelated SI kind).
• [Changed] Pintable skill 1.13.0: SI net_class required; EN/CHIP_PU RC is not series_resistor.

2.36.0 — 2026-09-20 — Fase A: operator identity + PinScope fence

This instance is operated by Michele Bigi. Faradworks, Inc. is not the operator. PinScope identifiers are dual-read only. PCB BOM/SPOF/EMI/θJA slices from 2.35.0 stay on this branch.

• [Changed] Terms, privacy, contact, footers, and HTML metadata no longer claim Faradworks, Inc.
• [Changed] Attribution to Faradworks/Pinscope remains for AGPL lineage (LICENSE unchanged).
• [Changed] pinscope-compat / pinscope_compat.py: write periscope_* / periscopex:; migrate pinscope_* on read.
• [New] docs/development/PINSCOPE_FENCE.md — inherited tree stays in place; GitHub fork is not detached.

2.35.0 — 2026-09-20 — BOM↔PCB↔datasheet, SPOF, EMI FACT, gated Tj

Remaining Fase B slices except auto-place and thermal FEM / OpenEMS.

• [New] PE-BOM-010…014 package / pinout / voltage / temp / current when BOM, PCB, and datasheet all have numbers.
• [New] PE-SPOF-001 single regulator or shared crystal — REVIEW, never ERROR.
• [New] PE-EMI-001 only if layout_rules quotes EMI/common-mode/ferrite/shield (not IEC 61000).
• [New] PE-THM-002 Tj = Ta + P·θJA when P, θJA, copper area, and via count exist; else INSUFFICIENT.
• [Changed] Pintable skill 1.12.0: SI+EMI kinds; empty SI on older extracts triggers schematic re-extract (si_extract_needed.json on PCB). ImpedenceFinder license remains UNKNOWN (no upstream LICENSE).

2.34.0 — 2026-09-20 — ImpedenceFinder SI checks (not a dump table)

USB/HDMI/PCIe/ETH/LVDS/DDR layout_rules (diff/SE Z, skew, max length, spacing, ref plane, vias, layer, return, series R) are compared to ImpedenceFinder + copper. One PASS/FAIL/MARGIN finding per requirement. I2C/GPIO/CC/REGN are not 50 Ω.

• [New] PE-SI-002…PE-SI-010; ImpedenceFinder z0_avg/min/max in run_pcb_checks.
• [Changed] PE-SI-001 only on impedance-controlled buses matching the rule net_class.
• [Changed] extract-pintable layout_rules kinds for SI; default_model_version 1.11.0.

2.33.2 — 2026-09-20 — PCB complete UI, not a raw SSE error

A finished PCB exam no longer shows the raw watcher string pcb_status=complete (terminal). The SSE hatch emits pcb_complete; the PCB page then opens /report?domain=layout (expand-on-click tree).

• [Fixed] Synthetic PCB SSE for pcb_status=complete is pcb_complete, not pcb_error.
• [Fixed] /project/[id]/pcb navigates to the layout report when the run finishes.
• [Fixed] Restored changelog heading for 2.33.0 (version history).

2.33.1 — 2026-09-20 — ESD/PI filters, ERROR-first sort, findings tree

PE-ESD-001 only on J* ∩ IC nets (no NC / unconnected / VSYS/GND/3V3 spam). PE-PI-001 treats any capacitor on the rail, including KiCad / names, as decoupling. Report API and UI sort ERROR then WARNING then INFO, then RULE > RISK > REVIEW > INFO. The report left list is an expand-on-click tree (IC → pin/net → cards), not a dump of open groups.

• [Fixed] Connector GPIO / onboard rails no longer flood PE-ESD-001.
• [Fixed] Bulk or slash-prefixed caps (C68 /VBUS, C71–C75 VSYS) suppress “no local cap”.
• [Changed] GET /report and complete_findings order by severity then class.
• [Changed] Findings sidebar is a collapsed tree; PCB exam cards live in the same tree.

2.33.0 — 2026-09-20 — Fase B: hierarchy, derating bands, timing, PI, ESD/return

Usable slices (not a platform): component→pin→net→block inventory, capacitor PASS/MARGIN/RISK from Vop/Vrated, RC/strap timing only with numbers, local vs bulk PI, ESD and HS return as REVIEW.

• [Fixed] complete_finding clamps ERROR unless finding_class=RULE and provenance=MANDATORY (LLM REVIEW cannot stay ERROR).
• [New] hierarchy.json + PE-HIER-001 dangling IC pins.
• [New] Derating table stress PASS/MARGIN/RISK; findings PE-DRT-001/002/003.
• [New] PE-TIM-001/002 skip without R/C and t_reset or Vih/Vil.
• [New] PE-PI-001/002 local vs bulk; distance only with layout_rules mm.
• [New] PE-ESD-001, PE-RET-001 are REVIEW, never RULE ERROR.

2.32.1 — 2026-09-20 — PCB Action on card + parsed geometry in AI context

Finding cards always show an Action. sentence (action, else recommendation, else a default). PCB AI context now includes vias under the footprint, copper thickness, nearby trace widths, courtyard, and keepout polygons from .kicad_pcb.

• [Fixed] Layout/AI findings no longer show an empty Action chip; the sentence is on the card.
• [Changed] PCB exam injects parsed via counts/drills, stackup thickness, pin-net widths, courtyard/keepout. Insufficient evidence only when those extracts are empty.
• [Changed] submit_review recommendation is required for INFO as well as ERROR/WARNING.

2.32.0 — 2026-09-20 — Finding engine (schema + PCB)

Same finding object on schematic analysis and PCB exam: FACT / REQUIREMENT / INFERENCE, datasheet provenance in the rule DB, RULE vs REVIEW, designer decisions, independent severity/confidence/evidence.

• [New] docs/motore-finding.md — engine spec. finding_engine.py + decisions.json.
• [New] Report cards show Fact / Requirement / Inference, class, provenance, insufficient evidence.
• [Changed] Recommended datasheet notes cannot stay ERROR. LLM findings are REVIEW, never RULE.
• [Changed] Schematic and PCB share library/extracted; PCB does not re-read the PDF.

2.31.0 — 2026-09-20 — Shared library PCB exam (no second PDF pass)

Schematic and PCB share library/extracted. PCB AI consumes that cache (pintable required; no PDF attach). Report PCB exam section plus power-trace/thermal checks.

• [New] Report section PCB exam (source=pcb_review and PE-PWR/THM/VIA/KEL/STCH).
• [New] PE-PWR-001 width × copper vs I_load (IPC-2221 only with stackup + Tjmax).
• [New] PE-THM-001 dissipation vs courtyard vias/pour; PE-VIA-001 via share of I_load (INFO).
• [New] PE-KEL-001 Kelvin/sense on a shared load net; PE-STCH-001 GND stitch in a signal bbox over a pour.
• [Changed] PCB review skips ICs without library pintable (“run schematic review first”).

2.30.0 — 2026-09-19 — PCB review pipeline (exam, not auto-place)

Parallel MODE=pcb job examines an uploaded .kicad_pcb: domains/groups, trace inventory, deterministic layout checks, and per-IC AI datasheet review. Findings merge into the report with a Layout filter. No packing or pcbnew write-back.

• [New] POST /api/pipeline/{id}/pcb/start — PCB exam job (pcb_status).
• [New] Deterministic PE-LAY-*, PE-PLC-*, PE-SI-001, PE-DRT-001 with required recommendations.
• [New] AI PCB review (same loop as schematic) with layout/domain context.
• [Changed] Schematic review no longer seeds placement/SI checks.

2.29.1 — 2026-09-13 — Fix sign-in /login 404 after rebrand

Landing CTAs pointed at /login, which did not exist (page is /sign-in). Added redirects, accepted legacy JWT issuer pinscope-local, and CORS for both Periscope and Pinscope hosts.

• [Fixed] /login → /sign-in, /register → /sign-up; marketing links updated.
• [Fixed] JWT decode accepts pinscope-local issuer from pre-rebrand sessions.
• [Fixed] Deploy script CORS includes both public hostnames.

2.29.0 — 2026-09-13 — Rebrand to Periscope

Product name, package (periscopex), Docker containers, deploy script, and default site URL are now Periscope (https://periscope.michelebigi.it). Deterministic finding IDs use the PE-* prefix. Existing project.json pinscope_version and browser storage keys are still read.

• [Changed] Brand Pinscope → Periscope across UI, docs, and APIs.
• [Changed] backend/pinscopex → backend/periscopex; rule IDs PS-* → PE-*.
• [Changed] Default host / update script → periscope.michelebigi.it / update-periscope.sh.

2.28.12 — 2026-09-13 — Antenna templates: IFA / meander / stub + .kicad_mod

Progetta antenna now returns a full parametric drawing: polyline segments (mm), SVG preview, and a downloadable KiCad footprint. Choose IFA, meander, or stub; geometry scales to the antenna zone when present. Still a routing template — no EM/VSWR invented.

• [New] antenna_geometry.py (IFA / meander / stub → segments + SVG + .kicad_mod).
• [Changed] POST /antenna/design accepts template; recipe includes geometry.
• [Changed] RF / Impedance Progetta UI: template select, SVG preview, download footprint.

2.28.11 — 2026-09-13 — RF / Impedance: verify antenna + design recipe

Project tab renamed RF / Impedance. Verify matching from IC ANT/RF pins toward an ANT* / ANT_FEED marker; Progetta returns microstrip w for 50 Ω (stackup or UI h/εr), optional λ/4 length from f0, and antenna-zone bbox. Auto-draw copper comes later — no EM/VSWR invented.

• [New] antenna_rf.py + GET/POST /api/projects/{id}/antenna.
• [New] Verify + Progetta cards on the impedance panel.
• [Changed] Sidebar label RF / Impedance.

2.28.10 — 2026-09-13 — Classify strap/bootstrap satellites; hide other

Caps on EN/BOOT/REGN/PMID and bootstrap caps between IC pins get real roles. Unclassified other parts are dropped from satellites and assemble_order.

• [Changed] _role_hint classifies GND bypass on bias/strap nets and flying bootstrap caps.
• [Changed] Assemble / IC groups omit role_hint=other.

2.28.9 — 2026-09-13 — Cleaner Domains / Power rails membership

Power rails follow primary domain only. IC satellites for decoupling/bulk/filter/pullup stay on the IC’s primary supply rail (LDO 3V3 no longer inherits VSYS input caps). Connectors/switches drop out of noisy “other” satellites.

• [Fixed] Rails view membership = domain primary rail (not transitive satellite nets).
• [Fixed] _group_for_ic primary-rail filter for power-role satellites; skip connector/switch “other”.

2.28.8 — 2026-09-13 — Stronger layout_rules extraction skill

Pintable skill now treats PCB / typical-application layout guidance as a first-class extract. Page trim keeps layout keywords; IC cache re-extracts once when layout_rules are empty under an older model_version (1.10.0+).

• [Changed] skills/extract-pintable — dedicated layout_rules step, examples, hard negatives; tighter validate.py.
• [Changed] Datasheet page trim includes PCB layout / decoupling / typical-application keywords.
• [Changed] Analysis IC extraction refreshes empties when model_version < default (1.10.0).
• [Changed] default_model_version → 1.10.0.

2.28.7 — 2026-09-13 — Placement F2 pack skeleton (gated)

Placement pipeline can propose satellite xy only when a .kicad_pcb layout exists and a decoupling_proximity rule has numeric max_distance_mm. No millimetres invented; otherwise placement_pack.json is skipped with an explicit reason.

• [New] placement_pack.py + placement_pack.json after F1 plan.
• [New] GET /api/pipeline/{id}/placement/pack and Pack section on the placement page.
• [Changed] Placement stepper adds a Pack satellites stage.

2.28.6 — 2026-09-13 — Split Domains by primary supply rail

Domains no longer merge the whole board when a charger/LDO bridges VBUS→VSYS→3V3. Each IC is clustered by its primary supply rail (output for power ICs, regulated digital rail for consumers).

• [Fixed] _build_domains groups by primary rail instead of transitive POWER union-find.
• [Changed] Domain ids use the rail name (e.g. domain_3V3_DIGITAL).

2.28.5 — 2026-09-13 — Domains & power-rail topology views

Browse routing-first functional groups from the project sidebar: Domains (power-net islands) and Power rails, each highlighting IC groups and satellite roles.

• [New] Sidebar tabs Domains and Power rails (from placement_plan / functional_groups).
• [Changed] Analysis graph_build also writes placement_plan.json.
• [Fixed] Heal stuck Placement queued/running when the worker is dead.

2.28.4 — 2026-09-13 — Unstick zombie running pipelines

A finished run whose worker died before flipping meta stayed running, so Progress showed Review spinning forever. Heal those projects when the event log already ends with pipeline_complete.

• [Fixed] heal_if_pipeline_finished on project get / pipeline status.
• [Fixed] Progress stepper marks all stages complete on pipeline_complete.
• [Fixed] Admin sweeper also covers local zombies without execution_name.

2.28.3 — 2026-09-13 — Stop progress→report bounce on finished projects

Opening a finished project no longer flashes Processing and dumps you on the report. Progress only auto-opens the report after a live run on that visit.

• [Fixed] /progress checks project status before SSE; finished projects go to the hub.
• [Fixed] Analysis SSE ignores placement events and does not treat already-terminal status as a crash.

2.28.2 — 2026-09-13 — Fix project sidebar navigation

Opening a finished project no longer dumps you on the report with a stuck left menu. Hub first; Report stays in the sidebar. Leaving /report for BOM/tabs uses a full navigation so the page actually changes.

• [Fixed] Dashboard project cards/table open /project/{id} (not /report).
• [Fixed] Sidebar Dashboard / Library / BOM tabs escape nested report/progress/placement routes.

2.28.1 — 2026-09-12 — Placement pipeline (parallel)

Dedicated Placement job builds the routing-first topology plan without touching the analysis pipeline status or spending credits. No millimetres — domains, IC groups, satellites only.

• [New] POST /api/pipeline/{id}/placement/start (+ cancel, events SSE, get plan).
• [New] Project page Build placement plan → /project/{id}/placement progress + topology viewer.
• [New] Worker MODE=placement writes placement_plan.json (and refreshes functional_groups.json).

2.28.0 — 2026-09-12 — Layout F1 topology + crystal/NC checks

Routing-first floorplan foundation without inventing millimetres: domains and satellite role hints after graph build, plus deterministic crystal CL and NC-pin checks.

• [New] functional_groups.json from graph_build (domains, IC groups, role_hint, attached layout_rules).
• [New] crystal_cl_check (PS-XTAL-*) and nc_pin_check (PE-NC-001) in the deterministic suite.
• [Docs] Piano §0c Placement F1/F2; packing mm stays Layout F2.

2.27.1 — 2026-09-12 — DeepSeek roadmap integrations

Close the open P0/P2 items from the growth plan: offline smoke on simple_project, reviewer shortest_path, library promotion gate, PDF drop logging, per-stage cache hit-rate helper. IC placement stays Layout-product backlog.

• [New] scripts/smoke_simple_project.py + simple_project/smoke_baseline.json.
• [New] Graph tool shortest_path; library_gate before shared extracted/.
• [New] cache_stats_by_stage(); PDF truncate/omit page logs.
• [Test] tests/test_roadmap_integrations.py.

2.27.0 — 2026-09-11 — Local multi-user auth

Self-host Periscope accounts (email + password) so several people can share a project. Invite collaborators by email from the project page — same flow as cloud, without Clerk.

• [New] AUTH_JWT_SECRET enables register/login; first user is admin and inherits users/local projects.
• [New] /sign-in and /sign-up; sidebar account menu. Set NEXT_PUBLIC_AUTH_MODE=local on the frontend build.
• [Changed] Collaborator lookup works for local users; Clerk still used when its keys are set.

2.26.5 — 2026-09-11 — Prefer PCB nets for connectivity

When a .kicad_pcb is present, pad nets from the board drive the design graph. Schematic geometry alone was inventing swapped rails (GND↔3V3) and floating pins on good KiCad 10 designs.

• [Fixed] KiCad 10 (net "Name") pad form.
• [Fixed] Graph build overrides sch nets with board connectivity; /NET → NET.
• [Test] PCB nets beat a misleading schematic.

2.26.4 — 2026-09-11 — KiCad power nets merge

.kicad_sch connectivity treated every GND power flag as its own island (GND_, GND__…), so the reviewer invented swapped rails and floating pins on good designs.

• [Fixed] Same-name power symbols and global/local labels merge within a sheet (KiCad semantics).
• [Fixed] Pins sitting mid-wire attach to that net; mirror x/y handled correctly.
• [Test] Disconnected GND flags, local labels, mid-segment wire.

2.26.3 — 2026-09-11 — KiCad project zip upload

One zip (or every .kicad_sch) covers hierarchical sheets. If the zip has bom.csv and .kicad_pcb, those are taken too. Pipeline re-reads companions from storage.

• [New] Zip → sheets + optional BOM/PCB. Nested Sheetfile paths kept.
• [Test] Upload → workspace re-parse finds child sheet parts.

2.26.2 — 2026-09-11 — Three file boxes

New project: BOM, schematic, and PCB on the first screen. PCB is optional.

• [Changed] No extra wizard step for the board.

2.26.1 — 2026-09-11 — Ask for the KiCad board

The create-project wizard has a dedicated PCB step (skip still allowed). Report load errors show the API detail instead of a generic fetch failure.

• [New] Wizard step for .kicad_pcb. Upload later from Settings or Impedance.
• [Improved] Report page retries briefly and links back to pipeline progress when report.json is missing.
• [New] Drop the KiCad project folder (or a zip). Extra library junk is ignored; the board is picked up if present.

2.26.0 — 2026-09-11 — ImpedenceFinder Z0 on PCB nets

A pipeline run with .kicad_pcb + stackup samples routed signal nets (power/ground skipped). Extra net names can be analyzed from the Impedance tab. Z0 is ImpedenceFinder net_walk/zsolver; no invented εr.

• [New] impedance_nets.json after graph build. GET/POST /api/projects/{id}/impedance/nets.

2.25.0 — 2026-09-10 — Keepout courtyard

layout_rules keepout flags a foreign net whose track endpoint is inside the KiCad courtyard. Own net and missing courtyard skip. No invented analog/digital classes.

• [New] PE-PLC-004 WARNING. Tests use X1 / /HFXIN / GND from simple_project.

2.24.0 — 2026-09-10 — Crystal load caps and track path

Load caps on XIN/XOUT use the same max_distance_mm as decoupling. If the PCB has segments on the net, the limit is shortest-path length, not a guessed “loop is too big” ratio.

• [New] Crystals (X1 / C9 / C10 on simple_project) run PE-PLC-001 when layout_rules has millimetres.
• [New] Detour tracks: path along segments vs the same max_distance_mm. No segments → euclidean pad distance.

2.23.0 — 2026-09-10 — same_layer decoupling

If layout_rules sets same_layer: true, a decoupling cap on the opposite copper from the IC is a WARNING. A via inside the courtyard (calculated) is enough. Unset flag → skip.

• [New] PE-PLC-003 WARNING when every placed cap on the net is on F vs B opposite the IC.

2.22.0 — 2026-09-10 — Thermal vias vs min_via_count

Via count is calculated inside the KiCad courtyard. The limit is the min_via_count parameter from layout_rules. No courtyard or no count → skip. No pad radius default.

• [New] PE-PLC-002 when vias in courtyard < min_via_count. simple_project has no PCB so it stays silent.

2.21.0 — 2026-09-10 — Layout SI skew (datasheet mm only)

Intra-pair skew is measured on the PCB only when layout_rules length_match has a number. 3W, creepage, and CPWG are not guessed.

• [New] PE-SI-001 ERROR when a named pair (_DP/_DM, _P/_N) exceeds that millimetre. No mm in the datasheet → skip.

2.20.0 — 2026-09-10 — Placement vs datasheet (PCB)

Decoupling distance is measured on the .kicad_pcb against layout_rules. No board → no PE-PLC-001. A null millimetre skips — no 3 mm default.

• [New] PE-PLC-001 when a decoupling cap is farther than datasheet max_distance_mm. Empty layout_rules and missing caps skip.

2.19.0 — 2026-09-10 — Finding review and ECO

Findings can be accepted, marked false-positive, or wontfix with a required reason. Accepted rows export as ECO; OpenEMS-style layout SI is still not this.

• [New] Review state on the report (open / accepted / false_positive / wontfix). Empty reason is rejected except when returning to open.
• [New] ECO CSV/JSON of accepted findings only. False-positive and wontfix stay off the ECO.
• [New] Release signature: SHA-256 of findings + user + timestamp. Needs-review filter ?review=open.

2.18.0 — 2026-09-10 — ImpedenceFinder calculator

The Impedance tab uses the closed-form engine from ImpedenceFinder (Hammerstad–Jensen / Cohn), not a second formula set and not OpenEMS.

• [New] Project tab Impedance: microstrip, stripline, coupled-diff Z0, stackup → 50/90/100 Ω widths, download .kicad_dru advice.
• [New] Vendored ImpedenceFinder core under vendor/impedancefinder/ (no gerber2ems, no pcbnew).
• CPWG stays unimplemented — no invented number.

2.17.0 — 2026-09-10 — Lifecycle and datasheet extras

Distributor lifecycle is a cached check, not a review scrape. Errata and layout_rules stay structured and skip when the catalog or the PDF has no number.

• [New] PE-LF-001 EOL, PE-LF-002 NRND, PE-LF-003 explicit RoHS fail. Replacement only if the distributor lists it. Active / RoHS N/A / missing cache row are silent.
• [New] PE-ERRATA-001 when a catalogued workaround pull-up is missing. No URL → skip.
• [New] PE-INT-001 when internal_features.pullup_pins has no rail resistor.
• [New] layout_rules closed kinds; non-numeric max_distance_mm is stored as null.

2.16.0 — 2026-09-10 — KiCad cad-bridge

Periscope writes periscope-findings.json next to the report so a KiCad 9/10 action plugin can pan to the symbol uuid on the right sheet.

• [New] E2 cad-bridge JSON (version, ref, pins, sheet, uuid, severity). Layout rule ids target pcbnew; others target eeschema.
• [New] .kicad_sch symbols keep cad_uuid + cad_sheet in cad_index (child sheet, not the empty root).
• [New] Action plugin in plugins/kicad/ reads the JSON beside .kicad_pro / .kicad_pcb.

2.15.0 — 2026-09-10 — Power margin, sequencing, DNP enable

Schema checks now compare regulator load to Iout_max, look at PG→EN when a sequence is declared, and treat DNP as a fitted-variant graph.

• [New] PE-PWR-001 when specified IQ+I_load exceeds Iout_max, or an explicit series R/ferrite DCR drops >5% of the rail. Missing IQ and PCB traces are not guessed.
• [New] PE-SEQ-001 WARNING if power_sequence is in IC specs and upstream PG does not net to downstream EN.
• [New] BOM DNP/Fitted/Variant on bom_fields. Fitted enable with only a DNP pull is PE-DNP-001 ERROR; no DNP column skips the check.

2.14.0 — 2026-09-10 — Filtri e termico schema

Deterministic checks now match RC/LC/π/T filters and estimate LDO/resistor dissipation without inventing missing numbers.

• [New] Filter topology PE-FLT-001 (fc INFO) / PE-FLT-002 vs adc_sample_rate only when that spec exists. Ferrite DCR PE-FLT-003 only with a datasheet limit.
• [New] LDO P = I_load×(Vin−Vout) and Tj = 25 + P·θJA. Missing θJA is PE-TH-001 INFO. Iout_max is not treated as load.
• [New] Resistor I²R vs power_rating_w on LED paths and shunts with known ΔV (PE-TH-003).

2.13.0 — 2026-09-10 — DC-bias C_eff stima

The derating table now shows an effective capacitance under DC bias for C0G/X7R/X5R ceramics. It is labelled stima — not a vendor lot curve.

• [New] C_eff column from an empirical V/Vrated table. Tantalum/electrolytic and unknown dielectrics are left blank.
• [Improved] C0G/NP0 stays at nominal C; X7R at 50% of rated V is about 70% of C.
• [New] Bulk C without a ~100 nF ceramic is PE-ESR-001 INFO (no invented Z(f) target).

2.12.0 — 2026-09-10 — Pull-up sizing and LDO Cout

Deterministic schema checks now size I2C pull-ups, flag NRST pull-downs, and look at LDO VOUT capacitance — still WARNING, never a invented datasheet µF ERROR.

• [New] I2C pull-up value vs a wide NXP UM10204 band (PE-I2C-002). 4.7 kΩ is in-band; missing values are not sized.
• [New] Active-low reset with a resistor to ground is PE-RST-002.
• [New] Regulator VOUT needs Cout (PE-DEC-001); 100 nF-only on VOUT is PE-DEC-002. MCU VDD 100 nF is not flagged.
• [Improved] Pin-mux UART0 on the simple_project MSPM0 nets is covered in tests (SPI PICO/POCI already was).

2.11.0 — 2026-09-10 — DeepSeek V4.1 and re-analyze

Periscope now defaults to DeepSeek-V4.1-Flash (deepseek-flash) for every LLM stage, shows API cost in dollars, and lets you replace the BOM and netlist on an existing project without deleting it.

• [New] Default model is deepseek-flash (native vision). Legacy deepseek-v4-flash / deepseek-v4-flash-vision-exp names still work; they route to V4.1.
• [New] Replace BOM & netlist on a finished project and re-run the analysis. History, library cache, and prior spend stay on the same project.
• [Improved] API cost uses V4.1 Flash peak rates and is shown on the report, logs tab, and run estimate (not only credits).

2.10.0 — 2026-08-27 — Deeper datasheet review

Each IC review now sees more of the datasheet and starts from a structured abs-max table, so voltage, decoupling, and interface checks are less likely to stop at "Unverified".

• [Improved] Extraction pulls Absolute Maximum Ratings (supplies, pin voltages, current, temperature) alongside the pin table, and the reviewer gets those numbers in context.
• [Improved] DeepSeek ingest uses PyMuPDF text (tables survive better than pypdf) and, on vision models, renders pin / abs-max / electrical / application pages instead of always the first 24.
• [Improved] Review checklist now includes recommended operating conditions, VIH/VIL, crystal load caps, and datasheet-named external parts. Turn budget 16, more excerpt pages, three follow-ups per concern.

2.9.0 — 2026-08-27 — Component library

Chips and passives stay in a shared library after the first look, so the next board does not re-download datasheets or re-extract pin tables.

• [New] Library page in the sidebar: ICs (pin tables), passive series, discrete specs, and saved PDFs.
• [New] Datasheets are written to the library as soon as they are fetched or uploaded, not only after a full review.
• [Improved] The create-project wizard already skipped parts that were extracted once; that reuse now covers the PDF itself as well.

2.8.0 — 2026-08-27 — Automatic datasheets

Periscope now finds datasheet PDFs on its own. You can still upload a file, but you no longer need DigiKey keys for the common case.

• [New] Auto-fetch from LCSC (no API key) by manufacturer part number or LCSC code, with exact-MPN matching so a CH340E never silently becomes a CH340G.
• [New] Direct Texas Instruments datasheet URLs (ti.com/lit/ds/symlink/…) as a second source for TI parts.
• [New] Pipeline fallback: if a datasheet was not uploaded in the wizard, extraction and review try the same lookup before skipping the IC.
• [Improved] DigiKey remains an optional third source when DIGIKEY_CLIENT_ID / DIGIKEY_CLIENT_SECRET are set.

2.7.0 — 2026-08-27 — DeepSeek API

Periscope now talks to DeepSeek by default. Extraction skills run locally; datasheet PDFs are converted to text (and page images on the vision model) because DeepSeek does not accept native PDF documents.

• [New] DeepSeek provider (deepseek-v4-flash, deepseek-v4-pro, deepseek-v4-flash-vision-exp) via the OpenAI-compatible Chat Completions API.
• [New] Local skill runner: skills/*/SKILL.md is inlined and validate.py runs in-process — no Anthropic Console upload required.
• [New] PDF ingest for DeepSeek: pypdf text extraction plus optional PyMuPDF page renders on vision models.
• [Improved] Anthropic and Gemini remain optional fallbacks via PROVIDER_* / FALLBACK_PROVIDER_*.

2.6.0 — 2026-07-12 — Export Report to Excel

Download a project's findings as an Excel spreadsheet straight from the report — one click, ready to share, filter, or archive outside Periscope.

• [New] "Export Excel" button on the validation report. Every finding becomes a spreadsheet row — designator, part number, ID, severity, title, description, recommendation, and its datasheet source (page included) — sorted most-severe first.

2.5.1 — 2026-07-04 — More Thorough Reviews

Schematic review now works through every functional area of a component before finishing, so a part with several independent issues has all of them surfaced in one pass instead of just the first.

• [Improved] For each IC, the review covers power and decoupling, every signal interface, absolute-maximum ratings, and reset/boot/configuration and unused pins before reporting — catching multiple issues on the same component that could previously be missed.

2.5.0 — 2026-07-02 — Light Mode

Periscope now has a light theme. Toggle between light and dark with the sun/moon button — in the sidebar next to your account menu, or in the header on the website.

• [New] Theme toggle. Switch between light and dark mode anywhere in the app; your choice is remembered on this device. Everything defaults to dark, exactly as before, until you flip it.
• [Improved] Every status color — error, warning, and pass badges, finding cards, the progress view, billing — is tuned for both themes, so reports stay legible either way.
• [Improved] The sign-in page and account menu now follow the app theme instead of always rendering light.

2.4.0 — 2026-07-01 — Automatic Pin & LED Current Checks

Two datasheet-grounded checks now run on every project, independent of the schematic review — catching a swapped-peripheral pin or an over-driven LED — plus a clear list of any components that had no datasheet to review against.

• [New] Pin-function feasibility check. Periscope now flags when a net assigns an IC pin a peripheral function its silicon can't route — for example a UART5_TX net on a pin whose alternate-function table only offers UART5_RX. It's reported as an error straight from the datasheet's pin table and names the likely swap (TX↔RX, SDA↔SCL). It deliberately does not judge signal direction across an interface — a direct UART crosses TX↔RX while a transceiver runs straight through — so it only fires on physically impossible pin assignments, never on wiring style.
• [New] LED forward-current check. For each LED, Periscope computes the forward current from the supply rail, the series resistor, and the LED's rated forward voltage, and flags any channel whose current exceeds the LED's rated maximum. Each color of an RGB LED is checked separately, and a leg with no current-limiting resistor at all is called out as a caution.
• [New] "Not reviewed" list on the report. Components with no datasheet on file — for instance a do-not-populate footprint that isn't in the BOM — are now called out explicitly, so a mis-wired pin on an unreviewed part shows up as a known gap instead of being silently absent.
• [New] Findings from these automatic checks carry an "Automated check" badge, so they're easy to tell apart from datasheet-review findings.

2.3.3 — 2026-06-08 — Faster Reviews

Multi-chip designs now review several times faster — Periscope works through ICs in parallel instead of one at a time.

• [Improved] Datasheet extraction and schematic review now process multiple ICs at once, so reports on multi-IC projects come back substantially faster. The findings are unchanged — only the wait is shorter.

2.3.2 — 2026-05-26 — Smarter RF Topology Review

Schematic review now reasons about what each external part is for before flagging it — catching valid bias, coupling, and matching circuits that previously looked like errors.

• [Improved] The reviewer states the role of every external part on an IC pin (choke, blocking cap, divider, decoupling, matching) before judging the connection. Common RF topologies like bias-T (DC injected onto a coax through a choke, with the chip protected by an internal DC block and a downstream load doing the actual draw) are no longer flagged as errors against the chip.
• [Improved] Stricter absolute-maximum-rating checks: the cited limit must come from the same pin under stress (a Vdd abs-max no longer counts against an RF or signal pin), and the inequality must be a strict exceed — equal-to-abs-max is at most a Warning.
• [Improved] Single-concern deep dives are capped at two follow-up queries; concerns that can't be resolved in that budget are reported as Warnings with the unresolved question stated, so one suspect finding can't starve the rest of the IC review.
• [Improved] Inferred rail voltages from the power-tree pass are no longer treated as ground truth by the schematic reviewer. Voltages set by net name (+5V, +3V3) or by user power-source hints are trusted as before; voltages the power-tree LLM guessed for an adjustable regulator output or propagated through inference are kept on the power-tree view for reference but excluded from review reasoning, so a single misread rail can't anchor a false-positive Error.
• [Improved] After each IC's review, a second pass normalizes findings against a fixed Error/Warning/Info rubric and merges any two findings that share a single root cause (e.g. "series resistor drops VIN" and "VOUT setpoint exceeds available VIN" are one defect, not two). Cuts run-to-run severity drift and avoids inflating the error count when one defect can be described from multiple angles.

2.3.1 — 2026-05-25 — EDIF Netlist Support

EDIF 2.0.0 netlists upload alongside PADS-PCB, with a sub-design picker for files that contain more than one design. Schematic review is also more cautious about polarity / direction-control findings.

• [New] Upload EDIF 2.0.0 (.edn) netlists directly. Format is auto-detected from the file contents — no need to convert to PADS-PCB first. Verified against Siemens xDX Designer exports.
• [New] When an EDIF file contains multiple sub-designs, project setup shows a picker so you can choose which one to review. The picker auto-confirms when there's a single clean match against your BOM and only asks when it's ambiguous; unselected sub-designs are filtered out of the design graph.
• [Improved] Stronger verification of differential and polarity pin assignments (USB D+/D−, TX/RX, IN+/IN−, anode/cathode) directly against the datasheet.
• [Improved] Improved support for bidirectional buffers and level translators (74xx245 and friends) — direction-control truth tables are factored into bus-contention analysis.
• [Improved] Findings that share a single root cause on the same chip are grouped into one combined finding.

2.3.0 — 2026-05-24 — LCSC Part Number Support

JLCPCB-style BOMs with LCSC part numbers (e.g. C12044) now work out of the box — Periscope auto-detects the column, resolves each id to the real manufacturer part number, and shows you what it resolved to before the pipeline runs.

• [New] LCSC part numbers in the manufacturer part number column are auto-detected at BOM upload and converted to real MPNs. Works with JLCPCB / EasyEDA exports without any column renaming.
• [New] Project setup now shows the LCSC → MPN mapping on each IC row in the datasheet step (e.g. C12044 → TP4057-42-SOT26-R), so you can see what each LCSC id became before the pipeline starts.
• [New] Passive specs (value, voltage, tolerance, dielectric, package) are resolved from the LCSC catalog during project setup, with per-row progress and status — you see what's resolved before spending credits on the full pipeline.
• [Improved] Datasheet auto-fetch hit rate is dramatically higher on LCSC BOMs, because DigiKey now sees real MPNs instead of C… ids.

2.2.1 — 2026-05-22 — Easier Netlist Uploads & Xpedition Support

Tabbed file upload guide with per-tool instructions, Xpedition coverage, and direct .net / .txt uploads.

• [New] Documentation for exporting a PADS-PCB netlist from Siemens Xpedition Designer / DxDesigner (VX.2.x, including VX.2.14).
• [Improved] File upload guide reorganized into tabs — KiCad, Altium, OrCAD/Allegro, Xpedition, EasyEDA, and Eagle each get their own panel.
• [Improved] Netlist uploads now accept .asc, .net, .NET, and .txt directly — no more renaming required before upload.
• [Improved] File guide now calls out the difference between the PADS-PCB schematic netlist Periscope needs and the !PADS-POWERPCB PCB-layout dump that some EDA tools also save as .asc.

2.2.0 — 2026-05-20 — Cross-chip Datasheet Review

The reviewer now reads neighbor-chip datasheets to verify cross-chip constraints, with fewer false errors when a spec can't be confirmed.

• [Improved] Schematic review now cross-references connected chips: when an issue depends on a neighbor's spec (5V tolerance, absolute-max, drive strength), the reviewer pulls the relevant pages from that chip's datasheet before flagging it.
• [Improved] Fewer false errors on cross-chip findings: if a counterpart spec can't be confirmed from the datasheet, the issue is reported as a Warning with the unverified assumption stated — instead of being overstated as an Error.
• [Fixed] Some review findings could occasionally fail to appear in the report.

2.1.0 — 2026-05-19 — Datasheet Reference Highlighting

Datasheet citations now highlight the exact supporting sentence on the PDF page, with more reliable page numbers on large datasheets.

• [Improved] Datasheet references now highlight the exact supporting sentence on the PDF page, not just the page number.
• [Fixed] Datasheet citations landing on the wrong page for large (multi-hundred-page) datasheets.
• [Fixed] Reviewed findings losing their checked state on page refresh.

2.0.1 — 2026-05-01 — Flagging & Onboarding

One-click flags on finding cards, an onboarding survey for new users, and small UI polish.

• [New] Report findings with one click via the flag button on any finding card.
• [New] Onboarding survey for new users to help us improve the product.
• [Improved] Comment input box now fills available width.

2.0.0 — 2026-04-29 — Public Changelog

• [New] Initial public changelog.