poe: eight budgets that only existed in prose, and the audit that counts the rest #1992
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1992
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-1426"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #130 - it does not close it. UDW-PRO still has no published port or PoE census; this fixes the class the issue's fallback exposed.
devices/ubiquiti/udw.jsoncarried twelvepoeOutports and nopoe.budgetW, soDevicefell through to the model-name parser, got nothing fromUDW, andshow power inlineprinted "budget not modelled" over live ports (#1979 fixed that one file). The invariant suite only polices the opposite direction - a budget with no port to spend it on - so nothing counted the rest.The census
node scripts/audit-poe-budget.js(alsonpm run audit:poe) over the whole catalogue: 401 models source PoE on at least one port; 130 silent (PoE out, no budget, no "never published" marker); 22 inferred from the model name rather than a document; 16 explicitly unknown; 0 orphaned.It exits 0 unless
--strict: gating the class today would fail the build on the 130.research/poe-budget-field-census.mdrecords the end state (zero silent, then--strictin the test job).The audit corrected itself twice, both written down: read the engine's
hardware.poeOutrather than the spec's literal key (a port template's generated ports never carry it - the first cut reported 37 false orphans), and require the wattage before the word "budget" (Teltonika's "240 W total budget and up to 30 W on any one port" read as 30 W) with a thousands separator (1,050 W read as 50 W).Eight budgets promoted, each re-read from the vendor today
Three of those prose figures sat beside a bigger, wronger number: 141.54 W input power, 660 W including PoE output, an 870 W supply rating. That is how a lab over-subscribes a budget.
One is a stated configuration, not a number:
ECS-24-PoEpublishes 1,050 / 450 W with 2x600 W modules and 2,250 / 1,850 / 1,050 / 850 W with 2x1,200 W modules. The spec records 1,050 W - reachable at any input voltage only in the 600 W-module chassis - and thepoe.notecarries all six figures. Same shape as the E6616X AC/DC slot arithmetic (#803): a capacity that depends on what is fitted.Gates
node scripts/syntax-check.js- 417 files, all OKnode scripts/audit-port-types.js- no port contradicts its declared typenode scripts/audit-devices.js- no hard defectsnode scripts/regen-registry-doc.js- catalogue pages current (2,356 models / 258 vendors / 29,721 sockets); no doc churnnpm test- 343 suites, 11,908 assertions, 0 failed (653 s)test/hardware-invariants.test.js26,test/poe.test.js18,test/poe-inference.test.js17No engine behaviour change: the new script is an audit, and every device edit adds a
poeblock the engine already understood.9f38c8aa7094f3af3429