docs(agents): record the Vogt registration and the monorepo rationale

[thedancingdeveloper]

Adds a Work tracking — Vogt section to AGENTS.md. Documentation only; no code, no CI, no build changes.

Why

rustnzb is now registered in Vogt as rustnzb on the dev instance (prj_01M04J3R35QZ2FHB04YKESAFDK), swept, and consolidated — 31 issues, 59 PRs, 12 labels and 25 releases, read-only upstream, write_back: none. The point of that is that "what is outstanding here" becomes a question you ask Vogt rather than one the next agent re-derives from the tree. That only holds if the tree says so, which is what this note is.

What it records

• The Vogt slug, instance and project id, and that write-back is none — Vogt says nothing upstream on this repo.
• The name split: directory rustnzbd, repo and product rustnzb. The trailing d is a local directory artefact and deliberately does not enter Vogt. It is also a GHCR/Forgejo image name, and no repository by that name exists.
• The canonical remote, and that the legacy-org URL still returns 200 because GitHub follows transfer redirects — a redirect, not a home.
• That a separate record for this project exists on the production Vogt instance, and that the dev instance is the destination by owner decision.

The part worth reviewing

The monorepo layout is stated as deliberate. Without that, the next agent finds two things that look like unfinished work and are not:

1. Contract v1 marks this repo non_compliant on LICENSE, design/ and src/. The missing root src/ is the intended end state of the monorepo conversion — crates live in crates/ and apps/. The note says explicitly not to create a src/ to score a pass. Tracked as Vogt WI-1.
2. The first drift pass opened 30 unresolved_dependency proposals, every one an intra-workspace Cargo path dependency that resolves inside this repository. Accepting any of them asserts the target is not a project, which is false for all 30. Tracked as Vogt WI-2.

The note also records that the root workspace's exclude = ["benchnzb", "desktop"], and that fuzz/ is not a member either — those three are separate Cargo workspaces nested here, reaching back into the main workspace's crates by relative path. That is intended, and it is the detail that makes the obvious fix for WI-2 wrong: a tool keying on the root workspace's members list still mis-flags five of the thirty.

🤖 Generated with Claude Code