v0.7.7

Session Cartographer 0.7.7

This release adds the peer view, bounds file review to the session that did the
work, and closes three ways a real commit or edit could vanish from the corpus
without an error. The previous public release was 0.7.6.

Peer view: /standup

• /focus answers what has happened in a project. /standup answers who else
  is in it right now: every session active in the window with its provider,
  projects, idle time, span, and commits, followed by CONTENTION — the files two
  sessions are both editing. Read that section first; the roster is ambient.
• --commit <sha> names the session behind a commit that landed underneath
  you. --project scopes the roster and the contention list alike.
• A worktree edit and a main-checkout edit of one repository file count as one
  file. Workspace-root and worktree directory names are filtered from project
  labels but never from file paths. Unresolved edit candidates are reported in a
  NOT COUNTED footer rather than dropped, since a silent miss and a clean
  workspace otherwise print the same thing.
• Reads the session-attributed events the hooks already write. Captures nothing
  new, writes nothing.

Working memory

• File review diffs are bounded by the session: base is the last commit at or
  before the session's first event, head is the last commit within two minutes
  of its last event, falling back to the working tree while a session is in
  flight or committed nothing for that file. Both ends are named, and the review
  lists the ways the range can mislead. Split is the default layout, with the
  dependency-free unified table behind diff=unified.
• Artifacts group by document: one row per path, documents ahead of code,
  newest edit first, each carrying the threads that touched it. kind=md is a
  permalinked documents-only toggle.
• Windows run from 1 hour through 90 days. Search, filters, catch-up state,
  paging, sort, brushing, camera, and comparison axes are canonical browser
  history, so Back, Forward, reload, and Copy link restore the same desk.
• Every Explorer view names the agent that produced the row. Claude and Codex
  sessions keep their identities through transcript enrichment, and the facet
  bar can narrow to one agent.
• Heavyweight routes each have a recovery boundary, so a render failure no
  longer blanks the Explorer shell. Transcript text loads independently of its
  optional analysis, with typed missing, blocked, empty, and unreadable states.

Hooks and recall

• Commits made after a cd on its own line, or after a ;, are recorded. The
  hook previously stripped only the && form and dropped the whole command as
  noise. The commit hash and subject are now read from the repository rather
  than scraped from stdout, so git commit -q no longer produces a commit with
  no row.
• backfill-git-history.sh recognises commits the hook already logged and no
  longer duplicates them on a recovery run. Existing duplicates are not
  rewritten.
• Variable-bound python writes (p='file' … open(p,'w')) are recorded as
  edits even when the compound command carries an incidental > such as
  2>/dev/null. Before this, the edit logged as a plain command and the Memory
  Desk reported the file as never edited by that session.
• Memory and the session digest resolve edited files through one parser, so
  loose shell-detector candidates are counted as unresolved instead of becoming
  fabricated hottest-file entries.

Pre-fix history under-counts commits and edits for sessions that used these
command shapes. scripts/backfill-git-history.sh --project <name> --limit N
recovers the commits; edits are not recoverable retroactively.

Agent documentation

• The /carto skill documents the Memory Desk permalink grammar in full,
  transcribed from the route parser, with recipes for an agent's own thread, a
  bounded file review, a compare view, and a replayed window. Agents can hand an
  operator a URL instead of a description.
• /standup is listed everywhere the other skills are listed, and its reporting
  guidance says to hand over a peer session's permalink rather than a bare id.

Installation and verification

The archive is one local marketplace for Claude Code and Codex. Follow its
README for installation and restart the agent client afterward. If a detached
Turbo service is already running, refresh it through the managed controller or
the memory page; restarting the client alone does not refresh that process.

Release metadata, including the root lockfile, is checked before packaging.
Publication requires Node 22 unit tests, the Explorer build and Chromium flow,
and the package smoke test. Managed CLI install checks run when those CLIs are
available; hosted CI does not establish a local managed-install result.

Turbo remains optional and experimental.