-
Notifications
You must be signed in to change notification settings - Fork 5
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
chore(data): five data-plane hygiene items from the index audit
area:serverGo API, CLI, MCP, storage, or server runtimeGo API, CLI, MCP, storage, or server runtimeevidence:e2-sourceSource or log evidence identifies the likely causeSource or log evidence identifies the likely causestatus:needs-triageAwaiting maintainer classificationAwaiting maintainer classificationtype:maintenanceMaintenance, tooling, refactoring, or repository workMaintenance, tooling, refactoring, or repository workStatus: Open.#178 In bytefolk/mem;test(recall): the recall benchmark has no producer for the search path that ships
area:recallRecall, ranking, and feedbackRecall, ranking, and feedbackevidence:e2-sourceSource or log evidence identifies the likely causeSource or log evidence identifies the likely causestatus:needs-triageAwaiting maintainer classificationAwaiting maintainer classificationtype:maintenanceMaintenance, tooling, refactoring, or repository workMaintenance, tooling, refactoring, or repository workStatus: Open.#175 In bytefolk/mem;fix(index): index-generation endpoints report execution wired while no executor exists
area:serverGo API, CLI, MCP, storage, or server runtimeGo API, CLI, MCP, storage, or server runtimeevidence:e2-sourceSource or log evidence identifies the likely causeSource or log evidence identifies the likely causeseverity:s2-mediumMedium impact with a practical workaroundMedium impact with a practical workaroundstatus:needs-triageAwaiting maintainer classificationAwaiting maintainer classificationtype:bugSomething is broken or behaves incorrectlySomething is broken or behaves incorrectlyStatus: Open.#174 In bytefolk/mem;release(tag-path): verify v0.1.1 tag route and restore a sanctioned tag-cut path under ruleset 21899500
priority:p0Required for the next shared product proofRequired for the next shared product proofstatus:readyScope and acceptance criteria are ready for developmentScope and acceptance criteria are ready for developmentStatus: Open.#163 In bytefolk/mem;[Release] Migrate mem-mcp to @bytefolk/mem-mcp v0.1.2
priority:p0Required for the next shared product proofRequired for the next shared product proofstatus:readyScope and acceptance criteria are ready for developmentScope and acceptance criteria are ready for developmenttype:maintenanceMaintenance, tooling, refactoring, or repository workMaintenance, tooling, refactoring, or repository workStatus: Open.#153 In bytefolk/mem;feat(release): publish an installable memd artifact and reconcile /v1/version with client revision pins
area:infraCI, release, packaging, and repository infrastructureCI, release, packaging, and repository infrastructurearea:serverGo API, CLI, MCP, storage, or server runtimeGo API, CLI, MCP, storage, or server runtimeevidence:e2-sourceSource or log evidence identifies the likely causeSource or log evidence identifies the likely causestatus:needs-triageAwaiting maintainer classificationAwaiting maintainer classificationtype:featureA new user-facing capabilityA new user-facing capabilityStatus: Open.#151 In bytefolk/mem;[Bug] Prevent concurrent Qoder checkpoint regression and staging collisions
bugSomething isn't workingSomething isn't workingStatus: Open.#139 In bytefolk/mem;chore(ingest): extract the shared local ingestion core (walk, cursor, change gate, report) from the qoder connector
area:cliCommand-line interfaceCommand-line interfaceevidence:e2-sourceSource or log evidence identifies the likely causeSource or log evidence identifies the likely causestatus:needs-triageAwaiting maintainer classificationAwaiting maintainer classificationtype:maintenanceMaintenance, tooling, refactoring, or repository workMaintenance, tooling, refactoring, or repository workStatus: Open.#111 In bytefolk/mem;feat(sync): put --watch one-way directory watch (minimal tier, carved from Phase 2 sync drive)
priority:p2Useful backlog work outside the immediate critical pathUseful backlog work outside the immediate critical pathtype:featureA new user-facing capabilityA new user-facing capabilityStatus: Open.#110 In bytefolk/mem;mem-mcp 上架执行 G1–G6（MCP hubs 硬前置，运营派单）
priority:p1Important after the immediate critical pathImportant after the immediate critical pathtype:maintenanceMaintenance, tooling, refactoring, or repository workMaintenance, tooling, refactoring, or repository workStatus: Open.#104 In bytefolk/mem;