cert-exclude-sow-line

Notes

• 2026-11-05 (entirely-api ba49a1b): per-line cert exclusion. {“cert_exclude”: true} in a SOW line’s notes JSON leaves the line off the certification package only; the line keeps billing and stays on the scope record. build_cert_context drops it (product code suppresses auto-attach rules), validate_cert_readiness skips its specs and flags an all-excluded scope, context_summary lists excluded_scope_lines. Set via services.sow_specs.set_cert_exclude or PATCH /portal/projects/{id}/sow/{line}/cert-exclude (owner/admin, audited sow/cert_exclude). Distinct from as-built 0 (“not built”, which also drops the invoice line). First case blkhse.569433 (1637 Elkridge Dr, Edgewater MD): Dustin ruled the new cert certifies the 5 push piers only, invoice handled separately; the legacy 01/2026 cert already covered the IntelliJacks + waterproofing. No portal UI toggle yet.
• 2026-11-05 follow-through on blkhse.569433 (1637 Elkridge Dr): v1.1 regenerated through POST /cert-gen/approve with inspection_date override 2025-12-12 (project field was 12/11; visit record, photos and the January cert say 12/12); pier_log.json corrected through POST /portal/parse/save-pierlog (P2 25 ft/7 tubes, P3 28 ft/8 tubes per the handwritten log, avg depth 22.6); contractor stays “JES - Baltimore” by Dustin’s call. Routing: the project was parked on JES Triage by the legacy migration, so the cert route resolved to the triage list; POST /triage/return moved it to JES Baltimore (account swap + triage_status complete + comm log, no outbound message), so the portal’s Send Cert now routes to Julia Marketis + Nicole Lovo with ipbpri@aacounty.org (Anne Arundel rule) and Permits.Inspections@jeswork.com (legacy CC rule) on CC. Preflight 10/10, dry run clean. Send is Dustin’s, from the portal.