Files
whetstone_DSL/sprint50_plan.md

1.3 KiB

Sprint 50 Plan: Security and Performance Gates for Porting

Context

A transpilation pipeline is not deployment-ready without security and performance validation. Sprint 50 adds hard gates to migration acceptance.


Goals

  1. Add static/dynamic security checks to generated C++
  2. Add sanitizer and UB checks for target artifacts
  3. Add benchmark comparison against source baseline
  4. Integrate gates into acceptance contract

Steps

Step 729: Security scan orchestrator for generated targets (12 tests)

Step 730: Sanitizer gate integration (ASan/UBSan profile hooks) (10 tests)

Step 731: Dependency and supply-chain audit packet (10 tests)

Step 732: Perf benchmark harness contract (10 tests)

Step 733: Baseline-vs-target perf comparator (10 tests)

Step 734: Gate severity policy (block/warn/info) (8 tests)

Step 735: whetstone_run_porting_gates MCP tool (8 tests)

Step 736: Migration acceptance contract wiring (8 tests)

Step 737: Reporting templates for C++ review teams (8 tests)

Step 738: Sprint 50 integration summary + regression (8 tests)


Acceptance Defaults

  • No new high-severity security findings
  • Sanitizer clean in required profile
  • Perf regression within configured tolerance
  • Explicit waivers required for any blocked gate