Skip to content

v0.9.0 — Project memory visibility

Choose a tag to compare

@askwigconsulting askwigconsulting released this 24 Jul 01:15
· 40 commits to master since this release
dadbda9

Added

  • cohort lint single-sources the orchestration in-flight cap. The "≤10 agents
    in flight" cap is restated across five canonical files; the lint now declares the
    number once in docs/model-tiers.md and fails if any canon file drifts to a
    different one — anti-drift only, not runtime enforcement. A DESIGN [S] note records
    that the orchestration invariants (the cap, footprint-disjointness, signoff) are
    coordinator discipline plus the human PR gate by design: a declared orchestration
    graph and a PreToolUse hook counter were both evaluated and rejected (static checks
    are vacuous/impossible/duplicate; a hook counter is install-global and deadlocks on a
    crashed subagent).
  • Dashboard surfaces each project's agent-memory store. Project cards now show a
    🧠 N memories chip for the Claude Code per-project memory store
    (~/.claude/projects/<slug>/memory/) — where a project's session memory actually
    accumulates at compaction — with the newest-write time in the tooltip. This is a
    different tier from Cohort's own .cohort/canonical/memories/, and was previously
    invisible, so an active project looked memory-less. Read-only and content-free (count
    and freshness only, never file contents — the same posture as the project-memory
    git-state chip).