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
No public-facing marketing — table-stakes credibility moves so first-time visitors see an actively maintained project.
Tasks
Delete throwaway branches from the v0.6.0 train:
claude/dispatch-release-v0.6.0 (the one-shot release.yml dispatcher; couldn't delete via MCP auth)
claude/v0.6.0-handoff-doc (superseded; content was the playbook for the now-shipped session)
Audit + archive/delete ~30 stale claude/* and copilot/* branches (none are tracked in open PRs anymore). Use git for-each-ref --merged main refs/remotes/origin/ to find safe-to-delete merged branches.
Local-first semantic code intelligence for AI coding agents. 40-70× token reduction on code questions, brain-like synapse layer that learns from co-activation, and an Obsidian-style graph view (neuralmind serve). MCP server + PostToolUse compression for Claude Code, Cursor, Cline, Continue.
pyproject.toml keywords (bundled with Phase 1 instead)
Why it matters
Indirect marketing. A visitor landing on the repo today sees ~70 branches and no recent About-box edit. Two hours of UI clicks moves the project visibly from "lots going on, hard to read" to "tight ship". This sets up Phase 1's announcement to land in a credible context.
Effort
~1-2 hours, all UI work that needs maintainer hands (mostly). MCP tools can do PR triage and issue tracking; branch deletion via UI.
Tracking issue for Phase 0 of the v0.6.1 "Install Anywhere" plan.
See
docs/HANDOFF-v0.6.1.mdfor full context.Scope
No public-facing marketing — table-stakes credibility moves so first-time visitors see an actively maintained project.
Tasks
claude/dispatch-release-v0.6.0(the one-shot release.yml dispatcher; couldn't delete via MCP auth)claude/v0.6.0-handoff-doc(superseded; content was the playbook for the now-shipped session)claude/*andcopilot/*branches (none are tracked in open PRs anymore). Usegit for-each-ref --merged main refs/remotes/origin/to find safe-to-delete merged branches.graph-view,code-visualization,synapse,hebbian-learning,obsidian,force-directed-graph,code-graph. (Currently 10; aiming for ~17.)release.yml. Should be fine since the v0.6.0 publish succeeded, but confirm at https://pypi.org/manage/project/neuralmind/settings/publishing/Out of scope
Why it matters
Indirect marketing. A visitor landing on the repo today sees ~70 branches and no recent About-box edit. Two hours of UI clicks moves the project visibly from "lots going on, hard to read" to "tight ship". This sets up Phase 1's announcement to land in a credible context.
Effort
~1-2 hours, all UI work that needs maintainer hands (mostly). MCP tools can do PR triage and issue tracking; branch deletion via UI.