Sprint 12 closed: engineering activity as signal

Sprint 12 is closed. ADR-0013 (Engineering Activity as Signal, and Knowledge Consolidation) is Accepted.

After Sprint 11, Meronq could rank knowledge by strength — but almost nothing produced strength except memory_search. A day of work on packages/memory left that package cold. Vitality was measuring assistant attention, not engineering work.

What changed

Commits reinforce what they touch. Sync reads git log with file paths. A change under packages/memory/** strengthens that component; an ADR edit strengthens that ADR. Reinforcements are idempotent, so replaying the same window cannot inflate the graph.

Finished work stays live. Closing an issue or merging a PR no longer erases it from project memory. Open items stay, plus the 20 most recently updated closed issues and merged pull requests.

Commits consolidate into pull requests. Evidence for each commit is durable and never archived. When a squash-merge commit leaves the recent window, its entity merges into pull_request:…#N instead of becoming archived churn. Direct pushes to main stay visible as their own entities.

Presence is cheap again. Handshake records one access event per session, not one per entity.

Hygiene. Closed sprints are no longer shown as current. CI runs build and tests on pull requests; the permanently-red website deploy workflow is gone (Cloudflare Git already publishes the site).

What we deliberately deferred

memory_expand and memory_pack — personal UI dials to widen or compress a session's working set — wait until the substrate is in daily use. They must stay session-local, not shared team objects.

Principle

Sprint 11: Meronq does not forget facts, it forgets relevance.
Sprint 12: where relevance is shared across a review boundary, Meronq merges the representation — and lets real work leave a signal.