Adds the contact-form-cms feature docs (requirements, execution plan, functional and infrastructure design, code generation plan) and an optional Vite dev proxy for /api through API_PROXY_TARGET. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2.9 KiB
2.9 KiB
Execution plan: contact-form-cms
Summary
Single unit of work (web only): connect the ASF contact form to the CMS contact module through the copied headless package, with Friendly Captcha, CSP and dev proxy. Server work and the package captcha slot are delivered by other sessions.
Stages
| Stage | Decision | Reason |
|---|---|---|
| Workspace Detection | Done | Brownfield, Feature |
| Reverse Engineering | Skip | Team agreement |
| Requirements Analysis | Done (approved by SLS-Main for Bryan) | |
| User Stories | Skip | One persona (visitor); acceptance in requirements |
| Workflow Planning | This document | |
| Application Design | Skip | No new components; ContactForm, Gate and Panel are adapted. The package boundary is fixed by the package |
| Units Generation | Skip | One unit: contact-form |
| Functional Design | Execute | State machine of gate, availability, captcha and submit; field mapping; preselect; accessibility; error handling |
| NFR Requirements | Skip | Covered in the requirements (security, performance, testing); Security Baseline is enforced at each stage |
| NFR Design | Skip | Merged into functional and infrastructure design |
| Infrastructure Design | Execute | CSP directives (captcha), Vite dev proxy, deploy impact, pipeline, rollback |
| Code Generation | Execute | Plan first; approval before code (SLS-Main for Bryan; push and merge stay with Bryan) |
| Build and Test | Execute | Unit, component, PBT, e2e with mocks, manual run against the temporary environment, Lighthouse |
| Operations | Execute (included) | Deployment notes, monitoring (events only, no personal data), production readiness checklist; production stays off until Bryan's go |
Sequence and dependencies
flowchart LR
RA[Requirements<br/>done] --> WP[Workflow Planning]
WP --> FD[Functional Design]
FD --> ID[Infrastructure Design]
ID --> CG[Code Generation<br/>plan then code]
CG --> BT[Build and Test]
BT --> OP[Operations]
PK[Package with captcha slot<br/>SLP Software - SLS - Main] -.final copy.-> CG
SV[Server verifier and ASF host<br/>SLS Software - CMS / AndreaSlopFotografie] -.real test.-> BT
classDef done fill:#9ae6b4,stroke:#2f855a,color:#000;
classDef todo fill:#63b3ed,stroke:#2b6cb0,color:#000;
classDef ext fill:#f6e05e,stroke:#c05621,color:#000;
class RA done;
class WP,FD,ID,CG,BT,OP todo;
class PK,SV ext;
Text alternative: requirements are done; planning, functional design, infrastructure design, code generation, build and test and operations follow in order; the package slot and the server work from other sessions feed code generation and the real test.
Gates
- Design and plan approvals go to SLP Software - SLS - Main (acts for Bryan within the agreed frame).
- Push, merge, deploy, production and choices about design, text or privacy stay with Bryan.
- No code before the code generation plan is approved. The final package is copied only after SLS-Main's message.