anomalyco / anomalyco/opencode
Server/SSE + event/db hardening (audit-v7 and wave B findings)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Context
Part of the fork hardening series proposed in #48638 (branch session-diff-events). Tracker: #49565.
Problem
Server/SSE and event/db paths: audit-v7 findings across server + MCP tooling, event fanout and TUI/SDK desync risks, and general wave 7-11 hardening at the server boundary.
Change set (commit list)
- 292de78747 audit-v7 server/mcp
- 56feb5c84e wave 7-11 hardening
- 9e9b666c3b wave B server/SSE
- b50731ecdf wave B core event/db
- d1d211e431 wave B tui/sdk desync
Validation
- Targeted suites/typechecks green on the integration branch; no regressions across the audit corpus.
Linked: PR #48638 · tracker #49565 · sibling tracking issues listed in a follow-up comment.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with PR #48638 and the listed audit-v7, wave 7-11, and wave B commits, focusing on the server/SSE, event/db, MCP tooling, and TUI/SDK paths. Run the targeted suites and typechecks described in the issue; done means the integration branch remains green with no regressions across the audit corpus.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend, databases, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100