v0.0.80

[jbr-sekoia]

Version bump only — package.json + package-lock.json, the same two files and three lines as every previous bump. Subject is exactly v0.0.80 so the release-notes step filters it out of the changelog, as it does for v0.0.79 (#289) and its predecessors.

What ships in v0.0.80

PR
#296	the memory listing's guards reach the project-root files, the FTS index takes the body that passed them
#294	a schedule file reached through a symlink is listed and runnable
#293	the CLI's title is forwarded through tmux on attach
#292	subagent activity is traced from its single write path

Release notes for the manual publish

The workflow writes a bare subject dump and leaves the release a draft. Two things in this one need saying in prose — a silent behaviour change users will otherwise discover by finding files missing, and a freeze that was reachable without any hostile input. Suggested body for gh release edit v0.0.80 --draft=false --latest --notes-file …:

## What's changed

### Memory and schedules now follow symlinks — read the first note if you keep your configuration in a repo

- A `schedule-*.md` symlinked into a project's `.claude/commands` is listed in the brain tab and runnable from it. The cron loop always read through the link; the UI did not, so a scheduled task could run every week while the tab showed the project had no schedules at all (#294).
- The same for `CLAUDE.md`, memory notes and `.claude/*.md` reached through a link.

**Behaviour change.** A project-root `CLAUDE.md`, `GEMINI.md` or `agents.md` that is a symlink *pointing outside every known project root and outside `~/.claude`* is no longer listed. The Memory panel could never open those files — it refuses the same path — so the row opened blank and failed to save. If that symlink was a project's only memory file, the project itself no longer appears in the tab. Keeping the link's target inside a directory you have opened as a project restores it.

### Fixed

- A project holding a FIFO, a socket or a device named `CLAUDE.md` froze the app permanently: the read is synchronous on the main process and never returns. Non-regular files are now refused (#296).
- Files reached through a symlink are checked against the credential denylist and the project allowlist before being read, so a repository that links a `.md` at a key or an `.env` no longer puts its content in the searchable memory index (#296, #294).
- The "run now" button on a schedule checks what the link points at, not only where it sits, so a file that is not a schedule cannot become the prompt of a headless run (#294).
- An unreadable file in a scanned directory no longer hides every file listed after it.
- Opening the brain tab no longer rebuilds the known-project set once per file scanned (#296).

### Other

- The CLI's title is forwarded through tmux on attach, so an attached remote row is no longer mute (#293).
- Subagent activity is traced from its single write path, with its source (#292).

**Full changelog**: https://github.com/devsuitup/switchboard/compare/v0.0.79...v0.0.80

Order of operations

Per README.md "Fork release-flow gotchas" — the tag has to come after this merges, and from an account with push rights on origin:

gh pr merge <this PR> --squash        # main is protected: 1 approving review + green test (20)/(22)
git checkout main && git fetch origin && git reset --hard origin/main
git tag v0.0.80 && git push origin v0.0.80
# build finishes, 19 assets, release left as a draft on purpose:
gh release edit v0.0.80 --draft=false --latest --notes-file <the body above>

Tagging before the squash-merge would leave a tag that is not an ancestor of main, and the release-notes step derives its range from git describe.