37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
# Sprint 71 Plan: Web and API Ecosystem Semantics Pack
|
|
|
|
## Context
|
|
|
|
Modern transpilation quality depends on framework semantics, not just language syntax.
|
|
Sprint 71 adds web/API ecosystem packs for backend and frontend interoperability.
|
|
|
|
---
|
|
|
|
## Goals
|
|
|
|
1. Model HTTP/API semantics (routing, middleware, auth boundaries)
|
|
2. Add framework-aware lowering/raising hooks for web stacks
|
|
3. Preserve API contracts during language migration
|
|
4. Add API regression verification to support tiers
|
|
|
|
---
|
|
|
|
## Steps
|
|
|
|
### Step 939: Web/API semantics pack schema (12 tests)
|
|
### Step 940: Route/middleware/auth canonical model (10 tests)
|
|
### Step 941: Backend framework adapter hooks (10 tests)
|
|
### Step 942: Frontend API client contract preservation model (10 tests)
|
|
### Step 943: API schema diff and compatibility checker (10 tests)
|
|
### Step 944: API behavior regression runner integration (8 tests)
|
|
### Step 945: `whetstone_get_api_semantics` MCP tool (8 tests)
|
|
### Step 946: `whetstone_verify_api_compatibility` MCP tool (8 tests)
|
|
### Step 947: Web ecosystem migration report template (8 tests)
|
|
### Step 948: Sprint 71 integration summary + regression (8 tests)
|
|
|
|
---
|
|
|
|
## Contract Rule
|
|
|
|
- Breaking API changes must be surfaced as blocking gates by default.
|