Forgejo Code Server Shell

Mirror kubernetes/kubernetes into a Forgejo-hosted demo namespace without bespoke setup.

Project refs, pull requests, and merges through the Git↔jj gateway before analysis.

Expose maintainer concentration, expertise signals, hotspots, provenance overlays, and the first stress/heat surface on the same host.

Use Forgejo's repo, tree, issue, and pull-request UI unchanged.

Reuse Forgejo authentication and session handling instead of building a parallel account system.

Treat Vaglio as an adjacent panel or sidecar surface, not a hard fork of Forgejo chrome.

Let Forgejo emit Git-shaped events while Vaglio translates them at the gateway boundary.

Keep the internal source of truth `jj`-first behind the Git↔jj translation layer.

Branch projection

%{
  git: %{kind: :branch_ref, branch: "master", ref: "refs/heads/master"},
  jj: %{
    kind: :bookmark_projection,
    writable: true,
    bookmark: "git/heads/master"
  },
  provenance: %{lossy: false, notes: [], translated_from: :git}
}

Commit projection

%{
  git: %{kind: :commit, sha: "cafebabe"},
  jj: %{kind: :revset_selector, revset: "commit_id(\"cafebabe\")"},
  provenance: %{
    lossy: false,
    notes: ["Git commit SHAs map to explicit `jj` revset selectors, not synthetic change IDs."],
    translated_from: :git
  }
}

Review projection

%{
  git: %{
    state: :open,
    title: "Controller observability and ownership tracing",
    number: 884,
    kind: :pull_request,
    head_ref: "feature/controller-observability",
    base_ref: "master"
  },
  jj: %{
    change_key: "git/pr/884",
    kind: :change_proposal,
    base_bookmark: "git/heads/master",
    head_bookmark: "git/pr/884/head",
    review_state: :open,
    source_branch_bookmark: "git/heads/feature/controller-observability"
  },
  provenance: %{
    lossy: false,
    notes: ["Pull requests are projected as change proposals, not canonical internal review objects."],
    translated_from: :git
  }
}

Merge projection

%{
  git: %{
    strategy: :merge,
    kind: :merge_event,
    base_ref: "master",
    merged_commit_sha: "cafebabe",
    pull_request_number: 884
  },
  jj: %{
    kind: :bookmark_move,
    merge_strategy: :merge,
    bookmark: "git/heads/master",
    target_revset: "commit_id(\"cafebabe\")"
  },
  provenance: %{
    lossy: false,
    notes: ["Non-squash merges preserve Git edge ancestry most directly."],
    translated_from: :git
  }
}

Top maintainers are less dominant overall, but critical subsystems still hinge on a narrow review core.

A deep bench exists, but expertise is partitioned by subsystem.

API machinery, controllers, test-infra, and release tooling dominate coordination heat.

Expertise signals

Subsystem hotspots

Provenance overlays

Cross-SIG changes amplify review contention even when overall ownership is broad.

API machinery, controllers, release tooling, and test-infra recur as pressure zones.

Maintainer specialization patterns are strong enough to make the hotspot ranking legible.

Compatibility obligations create repeated prediction error whenever controller-facing schema assumptions move.

Fast-moving control loops create dense change history, but only some of that churn resolves underlying uncertainty.

Stress rises when release readiness depends on a narrow operational review core.

The sampled branch history shows 562 contributors with 45.0% of commits concentrated in the top three authors, indicating medium coordination concentration.

Top sampled contributors

Recent sampled commits

Sampled path hotspots

• Stronger long-term substrate for agent-scale code velocity.
• Needs deliberate compatibility surfaces for human contributors.

• Easier external adoption and procurement story.
• Less compelling substrate once agents dominate throughput.

Keep native in jj

Keep compatible at the edge

Reads and writes discussion repos against Forgejo's API.

Maps Git refs, pull requests, commits, and merges into `jj`-native analysis objects.

Hosts the existing roundtable dashboard without requiring Git to become the internal source of truth.