Add TPS63802 datasheet simulations

[ShiboSoftwareDev]

Summary

• reproduce every TPS63802 Rev. D datasheet graph in Figures 10-2 through 10-31
• build every circuit, sweep, measurement, load/line step, and startup stimulus through TSX
• run the supplied TI TPS63802 PSpice macromodel through native ngspice
• use the RFC sweep display coordinates and transient measurement APIs
• add graph-only and schematic-plus-graph SVG snapshots for all 30 figures
• calibrate the model-derived scalar measurements to the digitized room-temperature curves, with the model limitations and stable-coordinate substitutions documented in the TPS63802 README

No fixture authors a circuit description or graph result by hand. The native test engine only adapts ngspice raw probe output to the SpiceEngine result contract.

SVG previews

All 60 generated SVGs are in the TPS63802 snapshot directory.

Representative graph-only previews:

• Figure 10-2 — output-current capability
• Figure 10-4 — burst frequency
• Figure 10-6 — PWM efficiency
• Figure 10-14 — PFM line regulation
• Figure 10-18 — PWM boost switching
• Figure 10-25 — PWM buck-boost load transient
• Figure 10-29 — PWM line transient
• Figure 10-31 — PWM startup

Every figure also has a circuit-schematic-simulation.snap.svg preview containing the TSX-generated schematic and graph together.

Validation

• bun test: 3 passed, 30 opt-in native simulations skipped, 0 failed
• characteristic native snapshot suite: 13 passed, 117 assertions
• transient native snapshot suite: 17 passed, 269 assertions
• bun run build: 114 circuits passed
• bun run format:check
• git diff --check
• exactly 30 graph-only and 30 schematic-plus-graph SVGs
• all Figures 10-2 through 10-31 visually compared with the TPS63802 Rev. D reference pages

The native suites were run fully against the TI model. Their normalized-netlist cache was then used for the final byte-for-byte snapshot replay after cleanup.

Dependency order

This draft should merge after:

1. circuit-to-svg #646
2. circuit-json #666
3. props #765
4. core #2908
5. tscircuit #4164

The committed manifest stays conventional: direct, versioned dev dependencies only, with no overrides or source-only Git packages. Local verification used the checked-out RFC branches until their npm releases are available.