Skip to content

General vs project: move general tooling into the fork (audit checklist) #834

Open

Description

@scuttletoby

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-apps exists 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-guards beside fork-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.md that project files link, plus a doc-budget check.
  • G6 Review skill: the project copy and fork-kit/review drift (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

Low

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-demand example 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

Activity

  1. scuttletoby commented on Nov 21, 2026

    @scuttletoby
    OwnerAuthor

    Progress and new items (11-21).

    Progress:

    New items:

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions