You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Coordinate the next Vault 966 improvement wave across product polish, Watch Tonight discovery, security hardening, live-service reliability, public contributor onboarding, and architecture cleanup.
Context
This parent issue tracks the work split into individual implementation issues. The child issues are intentionally scoped so each Codex thread/worktree or forked contributor PR can pursue one concrete outcome.
Each child thread or forked PR should produce one of:
A draft or ready PR linked to its issue, with tests and verification summarized.
A final handoff comment explaining changed files, tests run, blockers, and whether live service verification passed.
Avoid merging broad overlapping changes without rebasing against earlier Library/security work. Public contributors do not need collaborator access or assignment; they can fork the repository and open a pull request that links the issue they are addressing.
Goal
Coordinate the next Vault 966 improvement wave across product polish, Watch Tonight discovery, security hardening, live-service reliability, public contributor onboarding, and architecture cleanup.
Context
This parent issue tracks the work split into individual implementation issues. The child issues are intentionally scoped so each Codex thread/worktree or forked contributor PR can pursue one concrete outcome.
Workstreams
Library polish
Discover / Watch Tonight
Security hardening for private home use and public self-hosters
Operations and release safety
Architecture cleanup
Contributor-friendly UX and accessibility
Public demo and onboarding
Recommended first merge batch
Dependency Notes
Thread and Contributor Guidance
Each child thread or forked PR should produce one of:
Avoid merging broad overlapping changes without rebasing against earlier Library/security work. Public contributors do not need collaborator access or assignment; they can fork the repository and open a pull request that links the issue they are addressing.