Repository navigation
Open
Description
Rule: everything that is not project-specific lives in the fork. A project keeps only its facts (in config) and thin adapters. "How Gradle builds are queued" is general even if only one project uses Gradle today.
An audit on 2026-11-21 (host tools, the projects, the fork itself) found the items below. Each becomes its own issue/PR when started; tick it here when it is done.
High
- G1 GitHub App token tool: the installed tool still runs a project's copy; the fork kit
fork-kit/gh-appsexists but is unused. Install the kit, delete the copy. - G2 Memory/capacity check and build slots: 3 copies of the capacity check (2 already differ) and 2 build queues. Merge into
fork-kit/heavy; Gradle becomes one build variant. - G3 Owner-question convention and its list tool (today a private script with repo names in code): becomes a fork feature (Issues page plan, questions Issues page Q1: how far should we change T3's Issues page? #828-Issues page Q4: may our owner-question wording be the public fork's defaults? #831).
- G4 Agent guard hooks (pipe guard, workflow-disable guard, memory-index budget, background-command guard, agent-slot hook): 4 are in no repo. New
fork-kit/agent-guardsbesidefork-kit/model-guard; turn model-guard on; rules now only in memory become hooks. - G5 Agent rules (state question, reviewers, models, capacity, owner questions) are copied into 4+ instruction files and drift. One
docs/fork/agent-rules.mdthat project files link, plus a doc-budget check. - G6 Review skill: the project copy and
fork-kit/reviewdrift (comment format differs). One fork skill; a project keeps only its domain lenses and a review tier in config. - G7 (G7 Merge path: one merge queue and one merge CLI in the fork #848) Merge path: 6+ ad-hoc serial merge scripts plus a project PR queue next to
fork-ci/actions/pr-queue. One queue, one merge CLI. - G8 (G8 Agent slot counting: one source (server.agentSlots) #849) Agent slot counting: 3 mechanisms count the same thing. Keep
server.agentSlots. - G9 (G9 fork-adopt: starting a new project is not hand work #850) A new project is all hand work: no CI starter workflows, no adopt/pin-bump tool, 5-7 separate config files, no ruleset template. One project index file + schema check +
fork-adopt. Also: a project is pinned 10 fork-ci releases behind.
Medium
- G10 (G10 Orchestrator state, handoff and session hooks as a fork feature #851) Orchestrator state/handoff, session-start and compaction hooks, two-account login helpers: general, live in a project. Merge into the fork handoff feature + kit hooks.
- G11 (G11 Guaranteed wake-ups: one mechanism #852) Guaranteed wake-ups: a project wake service next to T3's waits. One.
- G12 (G12 Runners: one routing, one sandbox, one checkout-heal #853) Runners: PC routing (1000+ lines), runner units, 3 sandbox designs, 3 checkout-heal copies. Merge into fleet-route/fleet-watch,
fork-kit/desk,git-clean. - G13 (G13 Upstream sync of forks: keep fork-follow, make it config-driven #854) Upstream sync of forks: 2 mechanisms. Keep fork-follow, make it config-driven.
- G14 (G14 Cleanup and install drift: one cleaner for every project #855) Cleanup and install drift: 2 worktree pruners (one project's worktrees are never cleaned because it has no PRs), monitor, log archive, mirror, install-drift check. Merge into
fork-kit/cleanerand the kit installer. - G15 (G15 Deploy and release with migration and rollback: general flow, project adapters #856) Deploy/release with DB migration and rollback: general flow, project adapters.
Low
- G16 (G16 Leases, machine access, scheduled jobs, backups: general kits #857) Machine leases, VM access, scheduled data jobs, PC file sync, backups, paste-command convention: new kits reading a private machine file.
- G17 (G17 Interaction-limit keeper: one scheduler #858) Interaction-limit keeper: 2 schedulers of one job.
Reverse problems (project facts in general code)
- (a private project issue) One project's session hooks match every worktree folder, so they fire in other projects' worktrees (bug).
- General tools carry project names and hard-coded machine facts (slices, lock paths, repo names). Move facts to config, rename.
- (Fork code: small project leftovers (R1-R3 of the 11-21 audit) #872) Fork code is clean except small items: two action READMEs use one project's folder layout;
ci-demandexample config name differs from the fork's own; the cleaner hard-codes one game's file types.
Order: G1, G2, G3, G4, G6 + pin bump, G5, G9, G7, G8; the hook bug any time.
🤖 Generated with Claude Code
Metadata
Metadata
Assignees
Labels
No labels
Activity
fork-kit/heavy: machine-file holds for heavy facts (t3-capacity), on …
scuttletoby commentedon Nov 21, 2026
Progress and new items (11-21).
Progress:
New items:
🤖 Generated with Claude Code
fork-kit/gh-apps: call forms and GH_REPO check of the older per-user …
docs/fork/agent-rules.md + fork-ci doc-check: general agent rules, on…
fork-kit/heavy: machine-file holds for heavy facts / t3-capacity (sta…
fork-kit/agent-guards: the machine's agent guard hooks as a kit (#834 …