docs(rfc): hardening and DX roadmap (WIP) - #69
Draft
matthew-demidoff wants to merge 1 commit into
Draft
Conversation
Proposes the next round of work in priority order: offsite database backups with a restore drill, queue round-trip coverage in CI, worker type-checking, typed server-action results, an oauth service split, and finish-or-cull decisions for the half-built features. Draft for review; no behavior changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft roadmap for the next round of work, ordered by risk reduction:
offsite DB backups + restore drill, queue round-trip coverage in CI,
worker type-checking, typed server-action results, an oauth.ts split,
and finish-or-cull calls on subscriptions and TERMS_VERSION. Security
review items stay tracked privately and are referenced, not listed.
WIP on purpose: the point is to argue about the ordering and the open
questions (backup tooling/target, staging vs scratch-db flow) before
any implementation starts.