ThatGuySam 1248c705b0 docs(plan): add discovery and deploy follow-up research ... Capture the next discovery, security, compatibility-data, and dual-deploy planning work, and ignore local Vercel/env state that should not be committed. This keeps the operational research with the repo while avoiding accidental local-config churn. Constraint: Must not alter production runtime behavior Rejected: Fold research notes into the runtime fix commit | obscures the user-facing app-test correction with planning-only material Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep .omx local state untracked even when committing broad workspace updates Tested: Document review only Not-tested: No runtime verification required for docs and ignore rules		2026-04-04 15:38:39 -05:00
..
app-discovery-d1-automation.md	docs(plan): add discovery and deploy follow-up research	2026-04-04 15:38:39 -05:00
app-test-typescript-refactor.md	test(playwright): lock browser coverage before scanner refactors	2026-04-04 14:55:13 -05:00
cloudflare-dual-deploy-shadow.md	docs(plan): add discovery and deploy follow-up research	2026-04-04 15:38:39 -05:00