RFC: Lumina-Note cloud integration P1 drained — next milestone?#229
Open
blueberrycongee wants to merge 1 commit intomainfrom
Open
RFC: Lumina-Note cloud integration P1 drained — next milestone?#229blueberrycongee wants to merge 1 commit intomainfrom
blueberrycongee wants to merge 1 commit intomainfrom
Conversation
Summarises one 8h loop session (12 iterations) of work on the Lumina-Note cloud integration: - 9 ship PRs (#217 #218 #220 #221 #222 #223 #224 #225 #227) covering C1, C2, C4-C9, C12. 86 tests, all passing. - 3 block PRs (#219 C3, #226 C10, #228 C13) — all three are spec-vs-PRD-§3 tensions that a single Lead read of §3's intent (does it cover docs? settings nav? IPC dispatcher additions?) would unblock at once. - C11 stays pre-blocked on the user's WIP edit lock in AISettingsModal.tsx; no PR opened. Lists recommended merge order, surfaces touched, follow-ups (real pubkey from T3, disk persistence after C3 unblocks, model display labels, online-verify reason copy), and a non-binding P2 sketch (sync, account portal, refund UX, quota warnings, server-side auth cache). Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
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
1 participant
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.
What
Per
cloud/TASKS.md's "When the backlog is drained" rule: every P1 task is now[x]or[BLOCKED]. This RFC captures the state for Lead to pick a P2 milestone from.Full summary in
cloud/RFC-P1-DRAINED.md.TL;DR
@noble/ed25519@^3.1.0,@noble/hashes@^2.2.0.AISettingsModal.tsx; ready to ship in <10 lines once that's resolved (re-uses cloud/C7: Lumina Cloud provider definition + visibility helper #223'sLUMINA_CLOUD_PROVIDER+isLuminaCloudVisible).Recommended merge order
main→ #217 → #218 → #220 → #221 → #222 → #223 → #224 → #225 → #227.Two merge commits (#225 brings in C4, #227 brings in C7) become no-ops once the upstream PRs land.
Lead asks (in priority)
lumina-cloudT3 to replace the all-zero placeholder insrc/services/luminaCloud/PUBLIC_KEY.ts.Touched files
cloud/RFC-P1-DRAINED.md. Inside thecloud/surface allowed by PRD §3 (the doc's own note that PRD.md and CONTRACT.md are Lead-only doesn't extend to other files incloud/).