Collaborators — active assignments
Tracks who’s working on what, so any session (or Mika) can check this FIRST before assuming a file/task is unclaimed. This is the human- readable companion to the in-file comment rule (see decisions.md “issues assigned to a collaborator must also be marked in-file”) — that rule marks individual files, this file gives the overview across all of them.
Rules for using this file
- Before starting work on any file that looks empty/stub/unclaimed, check here first, not just the file itself.
- When assigning a new issue to a collaborator, add an entry below AND follow the in-file marking rule from decisions.md.
- When a collaborator’s PR merges and closes their issue, move their entry to “Completed”, don’t delete it — keeping history here matters more than keeping the list short.
- If a collaborator goes quiet on an assigned issue for a while, note that here too (don’t just silently reassign or duplicate the work).
Active assignments
mwakidenis — issue #147
- Task: Implement 3 remaining apps/web/hooks stubs
- Files:
apps/web/hooks/useClipboard.ts,useCommandPalette.ts,useMediaQuery.ts - Status: not started
- Assigned: 2026-08-07
- Note: 4th active collaborator, first assignment. Also independently added CITATION.cff (unprompted, unassigned contribution) before this. Profile suggests frontend/React-heavy background, picked this task to match.
ManSio — issue #176
- Task: Design + implement a shadow/duplicate symbol definition detector
- Files:
packages/detectors/detectAmbiguousSymbolResolution.ts - Status: PR merged (feat/ambiguous-symbol-detector)
- Assigned: 2026-08-08
- Note: 5th active collaborator. Came in via a detailed GitHub comment (not a cold invite) — starred the repo, asked sharp questions about incremental re-analysis, and suggested this exact detector idea based on real experience building mscodebase-intelligence (a mature MCP codebase-intelligence server for Zed, 1032 tests, 13.9k+ lines in src/core/ alone). Delivered a complete, well-reasoned first PR (detectAmbiguousSymbolResolution.ts) same-day, following existing repo patterns without being asked. Added to CODEOWNERS 2026-08-09 based on that first PR’s quality.
ManSio — issue #186
- Task: Fix Python repos showing zero graph edges (resolvePath.ts likely doesn’t handle Python’s dotted import style)
- Files:
packages/graph/resolvePath.ts - Status: Done, merged via PR #192
- Assigned: 2026-08-09
- Note: 2nd task for ManSio. Confirmed root cause (resolvePath.ts didn’t recognize dotted Python module paths, not a parsePython.ts issue) before writing the fix, and checked for side effects on JS/TS repos (lodash.get-style names) before shipping. Also independently caught 2 issues in their own earlier PR (#176): categorize() wasn’t wired into doctor.ts, and had case-sensitivity + path-segment-boundary bugs. Both fixed via PR #193.