linked-repos

IN BUILD

"As tools mature the time and cost of building and deploying the whole hub starts to become a friction point. Conversely, sometimes I have projects that I started outside of the hub that I'd like to track and keep in short term memory. I want to have a mechanism to remain aware of external projects as well as help working prototypes leave the nest safely."

STAGES

  1. proposal06-29
  2. requirements07-05
  3. design07-05predates the Figma as-is + proposed pair
  4. tasks07-05
  5. build—
  6. archived—

CAPABILITIES — 3 IN ONE CHANGE

  • hub-as-proxy3 requirements
  • linked-repo-tracking5 requirements
  • prototype-graduation3 requirements

OUTCOMES — 17 OF 40 DONE, AND NOT MAPPABLE TO A CAPABILITY

This change organises its tasks by workstream rather than as spec scenarios, so progress cannot be split per capability.

WHAT HAPPENED

  1. PROPOSAL

    proposal landed

    2026-06-29 · 1 pull request
    • #257fix(workflow): symlink .claude/commands for opsx slash commands in Claude Code

  2. 6 days quiet — nothing touched this change

  3. TASKS

    specs and design and tasks landed

    2026-07-05 · 2 pull requests
    • #260feat(linked-repos): track external repos, graduation, hub-as-proxy (backend)
    • #269chore(mvds): wire GitHub Packages registry and session npm auth

  4. 7 days quiet — nothing touched this change

  5. BUILD

    fix(api): resolve dynamic route conflict crashing admin login (504)

    2026-07-12 · 1 pull request
    • #273fix(api): resolve dynamic route conflict crashing admin login (504)

History read from a manifest built at 2026-09-30 (09e7bcc).

4 pull requests, found by commits touching the change folder