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
..
desktop-app-compatibility-data-strategy-2026-04-04.md	docs(plan): add discovery and deploy follow-up research	2026-04-04 15:38:39 -05:00
netlify-ubuntu-24-stork-2026-03-15.md	docs(research): capture search migration findings	2026-03-15 11:58:22 -05:00
pagefind-feature-parity-2026-03-15.md	docs(research): add pagefind feature parity memo	2026-03-15 13:03:57 -05:00
pagefind-viability-2026-03-15.md	docs(research): capture search migration findings	2026-03-15 11:58:22 -05:00
private-public-repo-sync-patterns-2026-04-04.md	docs(plan): add discovery and deploy follow-up research	2026-04-04 15:38:39 -05:00
public-repo-security-and-monorepo-patterns-2026-04-04.md	docs(plan): add discovery and deploy follow-up research	2026-04-04 15:38:39 -05:00