Restack learning routing onto current #569 tip (#570)

[davekilleen]

Linked Issue

• Restack of Starter for the learning routing step from #503: parse, cluster, propose, record #570 onto the same-origin Proposal: declare how long an observation stays trustworthy, and measure it #569 tip (Restack knowledge half-life onto current main (#569) #744)
• Linear issue: none (Track C learning stack)

What Changed

• Cherry-picked the one real Starter for the learning routing step from #503: parse, cluster, propose, record #570 commit (048febde → 97c7f1f1) onto Restack knowledge half-life onto current main (#569) #744 head f35e24df1cb30d593c601a5afc2c7c7ea5e5f8e6
• Dropped the seven earlier commits already on main (Capture corrections when they happen, not at the end of the day #568) or restacked in Restack knowledge half-life onto current main (#569) #744 (Proposal: declare how long an observation stays trustworthy, and measure it #569)
• Intended behavior only: mechanical learning-routing starter — parse, cluster, propose destination, record implemented/dropped. Applies nothing.
• Did not invent skill wiring. Confirmation still belongs in a skill that can hold a conversation.

Old fork head: 048febdefea55a067199f3cc4d7e60848d27f1de (chrisjackson-coding:learning-routing)
New same-origin head: 97c7f1f1f6cc93fb17cb839869ceef441ff05b32
Stacked on: #744 (f35e24df) which itself sits on main #568 (8cf7dd84)

The original fork PR (#570) is DIRTY and cannot be force-pushed (workflow-file restriction on the chrisjackson-coding fork). This same-origin branch is the MERGEABLE restack, same pattern as #744 / #743 / #742.

Test Plan

• Unit/integration tests added or updated: core/tests/test_learning_routing.py (14 tests, carried forward from Starter for the learning routing step from #503: parse, cluster, propose, record #570)
• Negative/error-path tests added or updated: malformed file, non-day file, invented status refused, two entries in one file never have statuses crossed
• Commands run locally:
  • pytest core/tests/test_learning_routing.py → 14 passed
  • pytest core/tests/test_freshness.py → 18 passed
  • pytest core/tests/test_mcp_session_lifecycle.py → 10 passed (including test_parent_death_reaps_the_process_pair on first run; no wait hardening)

Ralph Wiggum Loop

• I implemented the change.
• I self-reviewed for defects and edge cases.
• I requested specialist review for risky areas (testing/infra/security when relevant).
• I addressed review findings and re-ran checks.

Quality Gates

• I added/updated tests or documented why no tests are needed.
• I added a regression test for bug fixes, or this PR is not a bug fix.
• I validated failure modes / edge cases.
• I updated docs or confirmed no docs impact.
• CI checks for lint + tests + coverage are expected to pass.

Risk & Rollback

• Risk level (low/medium/high): low — rebase/restack of the one unique Starter for the learning routing step from #503: parse, cluster, propose, record #570 commit only
• Rollback plan: close this PR; original fork Starter for the learning routing step from #503: parse, cluster, propose, record #570 is untouched

Docs Impact

• Files updated: none
• If none, reason: starter module and tests only; no skill wiring and no generated catalog/inventory changes

Notes

• Do not merge the dirty fork PR Starter for the learning routing step from #503: parse, cluster, propose, record #570 until its head can be updated
• Does not touch usage PRs The feature-adoption log had a reader, a documented writer, and no way to reach it #590 / Nothing calls the adoption tool, so skills still hand-edit the log #593 / Restack #590: make the feature-adoption log reachable after the learning stack #743 / Restack #593: wire skills to mark_feature_used after the learning stack #742
• Stacked on Restack knowledge half-life onto current main (#569) #744; merge Restack knowledge half-life onto current main (#569) #744 first if landing this stack onto main

  

[github-actions]

What this pull request touches

• session hooks — feeds starting sessions and carrying useful context into the next interaction.
• tests — feeds catching regressions before contributors and users encounter them.

Gates that will judge this change

• Personal-data gate: added lines must not expose real identities or personal vault content.
• Change-aware gates: source changes are checked for tests, path-contract use, documentation drift, and touched-file coverage.
• Tests and coverage: the Python, MCP, migration, hook, and script suites must remain healthy.
• Safety and quality: security, lint, distribution, path consistency, and large-vault checks still apply.

Based on 12 changed files.

[cursor]

Approved. Cursor Bugbot was not present after the first check poll, so that signal was skipped. No approval policy required human review, and no reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}