{
  "version": 1,
  "repository": "Knuckles-Team/repository-manager",
  "revision": "5d12e2fa908616f1afcc622b1b617d03224fd56a",
  "captured_at": "2026-11-06T17:39:41.356287+00:00",
  "records": [
    {
      "id": "RM-CONNECTOR",
      "kind": "spec",
      "parent": null,
      "source": "specs/connector-boundary/status.json",
      "title": "RM-CONNECTOR \u2014 Repository-manager connector boundary migration",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "document": "specs/connector-boundary/spec.md",
      "component": "Connector boundary",
      "code_refs": [
        {
          "declared_in": "specs/connector-boundary/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_server.py:1002",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_server.py#L1002"
        },
        {
          "declared_in": "specs/connector-boundary/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "scripts/check_complexity_staged.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/scripts/check_complexity_staged.py"
        },
        {
          "declared_in": "specs/connector-boundary/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "scripts/check_import_safety.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/scripts/check_import_safety.py"
        },
        {
          "declared_in": "specs/connector-boundary/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "spec.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/connector-boundary/spec.md"
        },
        {
          "declared_in": "specs/connector-boundary/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "tests/governance/test_no_parallel_lane_authority.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "test",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/tests/governance/test_no_parallel_lane_authority.py"
        },
        {
          "declared_in": "specs/connector-boundary/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "tests/test_adapter_extraction.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "test",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/tests/test_adapter_extraction.py"
        },
        {
          "declared_in": "specs/connector-boundary/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_server.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_server.py"
        },
        {
          "declared_in": "specs/connector-boundary/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "requirements.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/connector-boundary/requirements.md"
        }
      ],
      "relations": [
        {
          "declared_in": "specs/connector-boundary/spec.md",
          "evidence": "file exists; coverage not verified",
          "kind": "references",
          "label": "`RM-GOVERNANCE-R001`",
          "repository": "Knuckles-Team/repository-manager",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/development-governance/spec.md"
        }
      ],
      "plan_diagrams": [],
      "unparsed_references": []
    },
    {
      "id": "RM-CONNECTOR-R001",
      "kind": "requirement",
      "parent": "RM-CONNECTOR",
      "source": "specs/connector-boundary/status.json",
      "title": "Migrate connector imports to the public SDK boundary",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "68211dcdc4a0",
        "c4cd54f6527a",
        "d00c0834551e"
      ],
      "verified_by": [],
      "parent_title": "RM-CONNECTOR \u2014 Repository-manager connector boundary migration",
      "definition": "**Migrate connector imports to the public SDK boundary.** repository-manager keeps its existing Git, branch-management and release tooling in place and reaches connector transport only through the public scion-sdk API, keeping any orchestration-package import only at the boundary where an actual orchestration decision is made. Caller chain: the console script `repository-manager-mcp` (`pyproject.toml:53`) runs `mcp_server` (`repository_manager/mcp_server.py:1002`), which calls `get_mcp_instance` (:973); that builds the server with `create_mcp_server` and `register_tool_surface` (:33, :988) from `scion_sdk.mcp`, and the tool registrars in `repository_manager/mcp_tools/` import `scion_sdk.mcp.action_dispatch.resolve_action` and `scion_sdk.mcp.concurrency.run_blocking`. Shape: no module under `repository_manager/` imports a private SDK module or the orchestration package; the dependency is declared once as `scion-sdk[mcp]` in `pyproject.toml:12`. Depends on: `RM-CONNECTOR-R003`. | Test: `tests/test_mcp_registration.py::test_mcp_tools_registration` and `tests/test_adapter_extraction.py::test_registry_order_and_extension_seam_are_deterministic`.",
      "definition_source": "specs/connector-boundary/requirements.md",
      "definition_line": 5
    },
    {
      "id": "RM-CONNECTOR-R002",
      "kind": "requirement",
      "parent": "RM-CONNECTOR",
      "source": "specs/connector-boundary/status.json",
      "title": "Classify every import from the orchestration package",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "c7068e31825a"
      ],
      "verified_by": [],
      "parent_title": "RM-CONNECTOR \u2014 Repository-manager connector boundary migration",
      "definition": "**Classify every import from the orchestration package.** repository-manager inventories every production and test import drawn from the orchestration package and classifies each as orchestration, connector transport, governance or obsolete. Caller chain: a planned inventory script `scripts/check_import_inventory.py` (planned), run by a `local` hook in `.pre-commit-config.yaml`, walks `repository_manager/` and `tests/` with `ast`, as `scripts/check_import_safety.py` does for platform imports. Shape: the inventory is a machine-readable JSON file `scripts/import_inventory.json` (planned) with one record per import holding module, symbol, caller and one of the four classes; a dynamic import (`importlib.import_module`) with a non-literal name is a failure, not a class. Today no import from the orchestration package exists in the code, so the inventory is empty and the check asserts that. The four class names and the file location are accepted as written here. | Test: `tests/test_import_inventory.py::test_every_orchestration_import_has_one_disposition_and_none_is_dynamic` (planned).",
      "definition_source": "specs/connector-boundary/requirements.md",
      "definition_line": 6
    },
    {
      "id": "RM-CONNECTOR-R003",
      "kind": "requirement",
      "parent": "RM-CONNECTOR",
      "source": "specs/connector-boundary/status.json",
      "title": "Route connector transport imports through the public SDK",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "d00c0834551e",
        "f6407b9f45af"
      ],
      "verified_by": [],
      "parent_title": "RM-CONNECTOR \u2014 Repository-manager connector boundary migration",
      "definition": "**Route connector transport imports through the public SDK.** Imports classified as connector transport call the public scion-sdk API, and imports of the orchestration package remain only at the boundary where repository-manager makes an orchestration decision. Caller chain: every MCP tool registrar in `repository_manager/mcp_tools/` imports from `scion_sdk.mcp.*` (`action_dispatch`, `concurrency`, `tool_surface`, `server`, `content`) and from `scion_sdk.config`, `scion_sdk.file_lock`, `scion_sdk.utilities`, `scion_sdk.privacy` and `scion_sdk.tls`, all public modules of the package. Shape: the tool entry points execute through `register_tool_surface` and `resolve_action`; the retired private governance module `scion_sdk.governance.lanes` and its package are imported by no production module. Depends on: `RM-CONNECTOR-R001`. | Test: `tests/governance/test_no_parallel_lane_authority.py::test_no_production_module_imports_the_retired_lane_module` and `tests/test_mcp_registration.py::test_mcp_tools_registration`.",
      "definition_source": "specs/connector-boundary/requirements.md",
      "definition_line": 7
    },
    {
      "id": "RM-CONNECTOR-R004",
      "kind": "requirement",
      "parent": "RM-CONNECTOR",
      "source": "specs/connector-boundary/status.json",
      "title": "Keep governance imports under repository-manager authority",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "269c661d12fa"
      ],
      "verified_by": [],
      "parent_title": "RM-CONNECTOR \u2014 Repository-manager connector boundary migration",
      "definition": "**Keep governance imports under repository-manager authority.** Development-governance imports such as queueing, reservation and safe-commit stay under repository-manager's own authority (`RM-GOVERNANCE-R001`) rather than being routed back through the orchestration package. Caller chain: the lane, queue, reservation and commit tools call `LaneRegistry` (`repository_manager/lane_registry.py:648`), `merge_queue.dispatch` (`repository_manager/merge_queue.py:3621`), `concept_actions.dispatch` (`repository_manager/concept_actions.py:124`) and `safe_commit` (`repository_manager/safe_commit.py:613`). Shape: the governance package is `repository_manager/governance/`; `tests/governance/test_no_parallel_lane_authority.py` scans every production module outside it for the retired governance import. Depends on: `RM-GOVERNANCE-R001`. | Test: `tests/governance/test_no_parallel_lane_authority.py::test_the_packages_own_lane_module_is_the_live_implementation`, `tests/governance/test_no_parallel_lane_authority.py::test_concept_reservation_module_is_hosted_as_this_packages_own` and `tests/governance/test_no_parallel_lane_authority.py::test_no_production_module_imports_the_retired_lane_module`.",
      "definition_source": "specs/connector-boundary/requirements.md",
      "definition_line": 8
    },
    {
      "id": "RM-CONNECTOR-R005",
      "kind": "requirement",
      "parent": "RM-CONNECTOR",
      "source": "specs/connector-boundary/status.json",
      "title": "Preserve MCP/CLI contract during connector migration",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "a47346f9c0f0",
        "d00c0834551e",
        "dcb852f23680"
      ],
      "verified_by": [],
      "parent_title": "RM-CONNECTOR \u2014 Repository-manager connector boundary migration",
      "definition": "**Preserve MCP/CLI contract during connector migration.** The migration preserves every public MCP and CLI action name, its typed arguments, validation rules and error categories, or introduces an explicitly versioned, documented change. Caller chain: a client lists the tools of the server built by `get_mcp_instance` (`repository_manager/mcp_server.py:973`); the catalog is the tool list that `register_split_action_tools` and `register_tool_surface` (:988, :994) produce, and the actions are validated by `resolve_action` against the tuples of `repository_manager/mcp_tools/contracts.py`. Shape: the golden is the sha256 of the sorted tool catalog (`BASELINE_CATALOG_SHA256` in `tests/test_adapter_extraction.py`) together with `repository_manager/connectors/tool_schema_fingerprints.json`; a change of either is a reviewed, versioned migration. Depends on: `RM-CONNECTOR-R001`. | Test: `tests/test_adapter_extraction.py::test_per_operation_mcp_catalog_matches_contract` and `tests/test_skill_action_surface.py::test_skill_action_references_match_live_schema`.",
      "definition_source": "specs/connector-boundary/requirements.md",
      "definition_line": 9
    },
    {
      "id": "RM-CONNECTOR-R006",
      "kind": "requirement",
      "parent": "RM-CONNECTOR",
      "source": "specs/connector-boundary/status.json",
      "title": "Remove dead connector adapters after cutover",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "68211dcdc4a0",
        "c4cd54f6527a",
        "d00c0834551e"
      ],
      "verified_by": [],
      "parent_title": "RM-CONNECTOR \u2014 Repository-manager connector boundary migration",
      "definition": "**Remove dead connector adapters after cutover.** Once the new connector path passes its tests, repository-manager removes the dead adapters, duplicate publishers and fallback imports that supported the old path. Caller chain: the package build (`uv build` over `pyproject.toml`) and the `check-cli-help` hook of `.pre-commit-config.yaml` import and start `repository_manager.mcp_server` without any retired module. Shape: the source scan is the parametrized test over every production file in `tests/governance/test_no_parallel_lane_authority.py`. Depends on: `RM-CONNECTOR-R003`, `RM-CONNECTOR-R004`. | Test: `tests/governance/test_no_parallel_lane_authority.py::test_no_production_module_imports_the_retired_lane_module`. The retired-name scan of the whole package, `tests/test_retired_names.py::test_no_retired_package_name_in_production_code` (planned), extends it beyond governance.",
      "definition_source": "specs/connector-boundary/requirements.md",
      "definition_line": 10
    },
    {
      "id": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT",
      "kind": "spec",
      "parent": null,
      "source": "specs/connector-content/status.json",
      "title": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT \u2014 The connector serves its packaged content",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "document": "specs/connector-content/spec.md",
      "component": "Connector content and served tools",
      "code_refs": [
        {
          "declared_in": "specs/connector-content/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/connectors/tool_schema_fingerprints.json",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/connectors/tool_schema_fingerprints.json"
        },
        {
          "declared_in": "specs/connector-content/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/kg_ingest.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/kg_ingest.py"
        },
        {
          "declared_in": "specs/connector-content/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_server.py:1002",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_server.py#L1002"
        },
        {
          "declared_in": "specs/connector-content/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_tools/registry.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_tools/registry.py"
        },
        {
          "declared_in": "specs/connector-content/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_tools/registry.py:105",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_tools/registry.py#L105"
        },
        {
          "declared_in": "specs/connector-content/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/workspace_manifest.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/workspace_manifest.py"
        },
        {
          "declared_in": "specs/connector-content/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "requirements.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/connector-content/requirements.md"
        },
        {
          "declared_in": "specs/connector-content/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "scripts/check_complexity_staged.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/scripts/check_complexity_staged.py"
        },
        {
          "declared_in": "specs/connector-content/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "spec.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/connector-content/spec.md"
        },
        {
          "declared_in": "specs/connector-content/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_server.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_server.py"
        }
      ],
      "relations": [],
      "plan_diagrams": [],
      "unparsed_references": []
    },
    {
      "id": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT-R001",
      "kind": "requirement",
      "parent": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT",
      "source": "specs/connector-content/status.json",
      "title": "Default content",
      "delivery_state": "VERIFIED",
      "state": "verified",
      "done": true,
      "landed_in": [
        "28abfd2cece8",
        "4bc7426a1266",
        "b2ef3c823bf3"
      ],
      "verified_by": [
        "tests/test_default_content_surfaces.py:16"
      ],
      "parent_title": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT \u2014 The connector serves its packaged content",
      "definition": "**Default content.** `pyproject.toml` declares the fleet identity once, as the single entry `repository-manager = \"repository_manager\"` of the `scion_sdk.connector` group (`pyproject.toml:108`), and the server lists the packaged `skill://` and `ontology://` resources and each packaged prompt. Caller chain: the console script `repository-manager-mcp` (`pyproject.toml:53`) runs `mcp_server` (X; that calls `create_mcp_server` with `content=ConnectorContent(connector=\"repository-manager\", package_root=<package directory>, package_version=__version__)` (:981), and the SDK registers the skills, ontology and prompts of the package root. Shape: no content registration code exists in this repository; the packaged content is the data under `repository_manager/skills/*/SKILL.md`, `repository_manager/ontology/*.ttl` and, when present, `repository_manager/prompts/*.json`, declared as package data in `pyproject.toml:58`. The package carries no prompt file today, so the prompt listing is empty. Whether the server may drop the explicit `content=` argument and rely on the SDK default is an owner decision. Cross-repository seams: `SCION-CONNECTOR-CONTROL-R071` (identity) and `SCION-CONNECTOR-CONTROL-R073` (default content), both in the SDK. | Test: `tests/test_default_content_surfaces.py::test_default_content_surfaces`. It builds the server through `create_mcp_server` and asserts that `resources/list` includes `skill://` and `ontology://repository-manager/` entries and `prompts/list` includes each `prompts/*.json` stem.",
      "definition_source": "specs/connector-content/requirements.md",
      "definition_line": 5
    },
    {
      "id": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT-R002",
      "kind": "requirement",
      "parent": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT",
      "source": "specs/connector-content/status.json",
      "title": "Serve the repository index tool with incremental state",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT \u2014 The connector serves its packaged content",
      "definition": "**Serve the repository index tool with incremental state.** The connector serves a tool `index_repository` that accepts the previous `RepositoryIndexState` and returns index pages for changed files only, in `syntax` or `typed` mode. The connector owns Git access; the SDK owns state, paging and receipts. Subsystem: connector. Caller chain: the connector worker of the SDK (`scion_sdk/runner/syncing.py::sync_stream`, `SCION-SOURCE-INGEST-R004.15`) calls the tool through `McpToolSourceAdapter.extract`; in this repository the tool is registered by a planned registrar `register_repository_index_tools` in `repository_manager/mcp_tools/repository_index.py` (planned), added as an entry of `MCP_TOOL_REGISTRY` (`repository_manager/mcp_tools/registry.py:105`), which `get_mcp_instance` hands to `register_split_action_tools` (`repository_manager/mcp_server.py:994`). Shape: the planned module holds one tool function that reads files from the registered workspace repository and returns the SDK page types; it reuses the SDK repository walk and never adds a second state or paging implementation. Refusals: `unsupported_language`, `invalid_type_mode`. Writes: none. Depends on: SCION-SOURCE-INGEST-R004.15. The code does not exist yet; `RepositoryIndexState` is a planned SDK type owned by `SCION-SOURCE-INGEST-R004.13`. | Test: `tests/test_index_repository_served.py::test_tool_returns_changed_files_only` (planned). It edits two files of a fixture repository and asserts that the page lists those two files only.",
      "definition_source": "specs/connector-content/requirements.md",
      "definition_line": 6
    },
    {
      "id": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT-R003",
      "kind": "requirement",
      "parent": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT",
      "source": "specs/connector-content/status.json",
      "title": "Serve repository hydration through the SDK transport",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT \u2014 The connector serves its packaged content",
      "definition": "**Serve repository hydration through the SDK transport.** The connector serves a tool `rm_repository_hydrate` with the arguments `repository_id` and `ref`. It builds `LocalGitRepositoryProvider` for the registered workspace repository, resolves the immutable revision, and calls `index_repository_snapshot` with the engine client of the caller. It returns the receipt fields: revision, batch count and manifest digest. The tool carries no read-only hint because it writes to the engine. Refusals: `REPOSITORY_UNKNOWN` for an unregistered repository and `REF_UNRESOLVED` for a ref that does not resolve. Writes: engine records through the SDK only. Subsystem: connector served tools. Caller chain: arbora MCP calls the fleet connector `repository-manager`, whose server is built at `repository_manager/mcp_server.py:973`; the planned registrar `register_repository_hydrate_tools` in `repository_manager/mcp_tools/repository_hydrate.py` (planned), an entry of `MCP_TOOL_REGISTRY` (`repository_manager/mcp_tools/registry.py:105`), registers `rm_repository_hydrate`, which calls `scion_sdk.repository.index_repository_snapshot` (`scion_sdk/repository/transport.py:96` in the SDK). Shape: the repository is resolved through the workspace registry the server already loads (`repository_manager/workspace_manifest.py`); the provider is `scion_sdk.repository.local_git.LocalGitRepositoryProvider(root, repository_id=...)` (`scion_sdk/repository/local_git.py:39`); the connector adds no engine call of its own, as `SCION-REPOSITORY-TRANSPORT-R002` requires. Depends on: SCION-REPOSITORY-TRANSPORT-R001, SCION-REPOSITORY-TRANSPORT-R002, CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT-R002. | Test: `tests/test_repository_hydrate_served.py::test_hydrate_indexes_a_fixture_repository_through_arbora` (planned). It indexes a fixture repository through the arbora MCP path and reads the manifest back from the engine.",
      "definition_source": "specs/connector-content/requirements.md",
      "definition_line": 7
    },
    {
      "id": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT-R004",
      "kind": "requirement",
      "parent": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT",
      "source": "specs/connector-content/status.json",
      "title": "Code reads come from the graph",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT \u2014 The connector serves its packaged content",
      "definition": "**Code reads come from the graph.** The file, tree, blame and search tools read through the graph engine tree read and the code graph (`MEDULLA-SDLC-R012`, `MEDULLA-SCM-R004`) for any repository the engine holds. A local clone is used only for a repository the engine does not hold yet. The ingest tool submits each listed repository through `SourceIngest` (`MEDULLA-SDLC-R012.1`). Caller chain: today `repository_ingest_repositories` (`repository_manager/mcp_tools/misc.py:24`) calls `ingest_repositories` (`repository_manager/kg_ingest.py:92`), which pushes typed `:GitRepository` nodes and no file contents; no file, tree, blame or search tool exists in `repository_manager/mcp_tools/` (`rm_git` at `repository_manager/mcp_tools/git.py:230` offers clone, enumerate, pull, push, add, commit, pre_commit, commit_code, status and cancel only). The planned read tools are registered by `register_code_read_tools` in `repository_manager/mcp_tools/code_reads.py` (planned), an entry of `MCP_TOOL_REGISTRY` (`repository_manager/mcp_tools/registry.py:105`). Shape: the planned module calls the engine through the caller's engine client, falls back to `git` in the registered clone only when the engine reports the repository absent, and changes `ingest_repositories` to submit through `SourceIngest`. The tools are `repository_file`, `repository_tree`, `repository_blame` and `repository_search`, one per operation; each takes `repository`, and the first three take `ref` and `path` while `repository_search` takes `query`. Depends on: CONN-REPOSITORY-MANAGER-CONNECTOR-CONTENT-R003. | Test: `tests/test_graph_reads.py::test_tree_and_blame_read_from_the_engine` (planned). It runs against a recorded engine.",
      "definition_source": "specs/connector-content/requirements.md",
      "definition_line": 8
    },
    {
      "id": "RM-GOVERNANCE",
      "kind": "spec",
      "parent": null,
      "source": "specs/development-governance/status.json",
      "title": "RM-GOVERNANCE \u2014 Repository development governance",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "document": "specs/development-governance/spec.md",
      "component": "Development governance",
      "code_refs": [
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "contracts/meristem-repository-manager.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/development-governance/contracts/meristem-repository-manager.md"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/concept_actions.py:124",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/concept_actions.py#L124"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/gate_ledger.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/gate_ledger.py"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/governance/cli.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/governance/cli.py"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/governance/lanes.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/governance/lanes.py"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/lane_registry.py:648",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/lane_registry.py#L648"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/merge_queue.py:3621",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/merge_queue.py#L3621"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/safe_commit.py:613",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/safe_commit.py#L613"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/worktree.py:140",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/worktree.py#L140"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "scripts/check_complexity_staged.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/scripts/check_complexity_staged.py"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "spec.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/development-governance/spec.md"
        },
        {
          "declared_in": "specs/development-governance/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "tests/governance/test_no_parallel_lane_authority.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "test",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/tests/governance/test_no_parallel_lane_authority.py"
        },
        {
          "declared_in": "specs/development-governance/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/concept_actions.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/concept_actions.py"
        },
        {
          "declared_in": "specs/development-governance/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/gates.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/gates.py"
        },
        {
          "declared_in": "specs/development-governance/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/lane_registry.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/lane_registry.py"
        },
        {
          "declared_in": "specs/development-governance/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/merge_queue.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/merge_queue.py"
        },
        {
          "declared_in": "specs/development-governance/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/merge_queue_runner.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/merge_queue_runner.py"
        },
        {
          "declared_in": "specs/development-governance/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/native_lane_authority.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/native_lane_authority.py"
        },
        {
          "declared_in": "specs/development-governance/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/safe_commit.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/safe_commit.py"
        },
        {
          "declared_in": "specs/development-governance/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/worktree.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/worktree.py"
        },
        {
          "declared_in": "specs/development-governance/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "requirements.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/development-governance/requirements.md"
        }
      ],
      "relations": [
        {
          "declared_in": "specs/development-governance/spec.md",
          "evidence": "file exists; coverage not verified",
          "kind": "references",
          "label": "`RM-CONNECTOR-R001`",
          "repository": "Knuckles-Team/repository-manager",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/connector-boundary/spec.md"
        }
      ],
      "plan_diagrams": [],
      "unparsed_references": []
    },
    {
      "id": "RM-GOVERNANCE-R001",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "repository-manager hosts the Git development-governance modules",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "3af7957a7a03",
        "63c543e980dc",
        "d00c0834551e",
        "f6407b9f45af"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**repository-manager hosts the Git development-governance modules.** The package contains the merge-queue, isolated-checkout lifecycle and concept-reservation modules as its own governance implementation, consumed internally by its commit and queue tooling rather than duplicated elsewhere. Caller chain: the CLI verb `repository-manager-governance` (`pyproject.toml:55`, `repository_manager/governance/cli.py:main`) and the MCP tools in `repository_manager/mcp_tools/` import `repository_manager/governance/lanes.py`, `repository_manager/merge_queue.py`, `repository_manager/worktree.py` and `repository_manager/concept_actions.py` directly. Shape: the modules named above are the only implementation; the retired lane module is not imported by any production module, and the reservation authority is built by `build_default_concept_authority` (`repository_manager/concept_actions.py:65`). Depends on: `RM-GOVERNANCE-R024`. | Test: `tests/governance/test_no_parallel_lane_authority.py::test_the_packages_own_lane_module_is_the_live_implementation` and `tests/governance/test_no_parallel_lane_authority.py::test_concept_reservation_module_is_hosted_as_this_packages_own`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 5
    },
    {
      "id": "RM-GOVERNANCE-R024",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Single authority for Git development governance",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "d84cc3923887"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Single authority for Git development governance.** repository-manager owns branch lifecycle, isolated-checkout identity, merge-queue admission and concept reservations as one authority that other packages call only through bounded APIs. Caller chain: callers reach the lane authority through `LaneRegistry` (`repository_manager/lane_registry.py:648`), the queue through `merge_queue.dispatch` (`repository_manager/merge_queue.py:3621`) and reservations through `concept_actions.dispatch` (`repository_manager/concept_actions.py:124`). Shape: an import scan over `repository_manager/` finds no module that imports the retired lane module; `NativeLaneAuthorityAdapter` (`repository_manager/lane_registry.py:555`) is the one production adapter and `FakeDurableLaneAuthority` (:109) the one test double. Depends on: `RM-GOVERNANCE-R001`. | Test: `tests/governance/test_no_parallel_lane_authority.py::test_no_production_module_imports_the_retired_lane_module`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 6
    },
    {
      "id": "RM-GOVERNANCE-R031",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Export the canonical development lane hook",
      "delivery_state": "VERIFIED",
      "state": "verified",
      "done": true,
      "landed_in": [
        "b8d9c384efdc"
      ],
      "verified_by": [
        "tests/governance/test_lanes.py:1586",
        "tests/governance/test_lanes.py:1660",
        "tests/governance/test_lanes.py:1705",
        "tests/governance/test_lanes.py:1734",
        "tests/governance/test_lanes.py:1754"
      ],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Export the canonical development lane hook.** Consumer repositories install the existing lane guard through an isolated Python pre-commit environment, not a runtime dependency or a duplicated script. They keep their own stages, with `always_run: true` and `pass_filenames: false`. Caller chain: a consumer's `.pre-commit-config.yaml` names this repository and the hook id `lane-guard` of `.pre-commit-hooks.yaml`, whose entry `python3 -m repository_manager.governance.lane_guard` runs `main` (`repository_manager/governance/lane_guard.py:234`). Shape: `main` calls `_check_canonical` (:130), `_check_generated_view` (:153) and `_check_cargo_target_override` (:214) in that order and prints the refusal; the hook carries no `stages:` key so it inherits the consumer's stages; setuptools package discovery and the `governance/*.yaml` package data (`pyproject.toml:58`) ship the module and its resource inventory. Exact installation proof from a published revision is required before rollout. | Test: `tests/governance/test_lanes.py::test_gate_still_refuses_a_canonical_commit_in_a_foreign_repo`, `tests/governance/test_lanes.py::test_gate_refuses_a_hand_edited_generated_ledger_view` and `tests/governance/test_lanes.py::test_gate_detects_a_stray_cargo_target_dir_export_in_a_foreign_cargo_repo`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 7
    },
    {
      "id": "RM-GOVERNANCE-R032",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "The package runs on Windows as well as POSIX",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "d7884e498f08"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**The package runs on Windows as well as POSIX.** Every platform-specific mechanism (descriptor-relative directory operations, `/proc/self/fd` anchors, `pass_fds`, process-group signals, `SIGKILL`, XDG state and config directories, directory symlinks, directory fsync, `O_NOFOLLOW` and `O_BINARY`, shell wrappers, path-prefix containment) lives behind `repository_manager.portable_fs` or an explicit `portable_fs.is_windows()` branch; no module imports a POSIX-only standard module unguarded and no Windows branch swallows an error. Caller chain: every filesystem caller in `repository_manager/` reaches the platform through `portable_fs.is_windows` (`repository_manager/portable_fs.py:48`) and `portable_fs.native_dir_fd` (:43); the `windows-latest` job of `.github/workflows/windows-ci.yml` runs the import-safety script and the fast unit tests. Shape: the Windows branches are exercised on any host by monkeypatching those two functions in `tests/test_windows_portability.py`; `scripts/check_import_safety.py` fails an unguarded POSIX-only import. | Test: `tests/test_windows_portability.py::test_emulated_handles_read_write_and_nest` and the other tests of that module.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 8
    },
    {
      "id": "RM-GOVERNANCE-R033",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "The generated code-enhancement report uses the standard hyphenated name",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "7d94bed1cb90"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**The generated code-enhancement report uses the standard hyphenated name.** `run_enhancer` writes its report to `.specify/reports/code-enhancement-report.md` and never writes an underscore-named report; the tracked report file carries the same name. Caller chain: the console script `run_single_enhancer.py` calls `run_enhancer`, which calls `_write_report` (`run_single_enhancer.py:139`) with the report path. Shape: file `run_single_enhancer.py` holds the one path literal; the tracked `.specify/reports/code_enhancement_report.md` is renamed with `git mv`; the spec standard's lower-case kebab-case file-name rule is the reason, so no exception entry is added. Depends on: none. | Test: `tests/test_run_single_enhancer_analyzer_lifecycle.py::test_report_and_sdd_generators_are_invoked_when_present` asserts the hyphenated path, and `::test_missing_report_and_sdd_generators_do_not_raise` asserts that the old name is never written.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 9
    },
    {
      "id": "RM-GOVERNANCE-R025",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Branch allocation tracks ownership, lease, and lifecycle state",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "78c6baf04778"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Branch allocation tracks ownership, lease, and lifecycle state.** repository-manager allocates an isolated branch record with repository ID, base commit, owner, lease and fence token, path allowlist and lifecycle state, enforcing only legal state transitions and rejecting stale tokens. Caller chain: the CLI `lane` verb (`repository_manager/cli_commands/lane.py`) and the MCP tool in `repository_manager/mcp_tools/lane.py` call `LaneRegistry.allocate` (`repository_manager/lane_registry.py:1317`), which calls `NativeLaneAuthorityAdapter.allocate` (:591) and `NativeLaneAuthority.allocate_lane` (`repository_manager/native_lane_authority.py:519`); heartbeat and finish go through `LaneRegistry.heartbeat` (:1510) and `finish` (:1563). Shape: the typed refusals are `LaneConflictError`, `StaleLaneFence` and `LaneTransitionError` (`repository_manager/lane_registry.py:41`, :67, :49); a refusal changes no stored record. Depends on: `RM-GOVERNANCE-R024`. | Test: `tests/test_native_lane_authority.py::test_allocate_branch_conflict_refused_by_both`, `tests/test_native_lane_authority.py::test_stale_fence_refused_by_both` and `tests/test_lane_registry.py::test_restart_heartbeat_and_fence_refusal_with_injected_clock`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 10
    },
    {
      "id": "RM-GOVERNANCE-R026",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Isolated checkouts never corrupt shared Git config",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "0454cd888aac",
        "e5d187678980"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Isolated checkouts never corrupt shared Git config.** repository-manager creates a real, separate Git checkout for each branch without modifying the shared repository's Git configuration, and serializes operations that touch the common repository so per-checkout state stays isolated. Caller chain: the `worktree` MCP tool (`repository_manager/mcp_tools/worktree.py`) and the CLI call `WorktreeManager.add` (`repository_manager/worktree.py:223`), which takes the add lock `_worktree_add_lock` (:56) and runs plain `git worktree add`. Shape: no code path writes `core.bare`; the shared repository's `core.bare` stays false after concurrent adds. | Test: `tests/test_worktree.py::test_concurrent_worktree_creation_keeps_shared_repo_usable_and_not_bare`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 11
    },
    {
      "id": "RM-GOVERNANCE-R027",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Commits stage only reviewed paths and verified gate identity",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "0454cd888aac",
        "127a8384c249",
        "3af7957a7a03",
        "8a96a9e0cfeb"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Commits stage only reviewed paths and verified gate identity.** A repository-manager commit stages only explicitly reviewed paths, runs its declared local gates, binds the resulting tree and gate identity together, and may enter the merge queue only from a clean, authorized branch checkout. Caller chain: `safe_commit` (`repository_manager/safe_commit.py:613`) takes the per-worktree lease, calls `_stage_paths` (:355), `_run_configured_gate` (:414), `_commit` (:469) and records `_gate_identity` (:504); `merge_queue.enqueue` (`repository_manager/merge_queue.py:802`) refuses a checkout the lane registry has not authorized. Shape: `paths` is required and non-empty; an unrelated untracked file is never staged; the baseline record binds the tree and the gate identity. Depends on: `RM-GOVERNANCE-R025`. | Test: `tests/test_safe_commit.py::test_safe_commit_stages_only_the_reviewed_paths`, `tests/test_safe_commit.py::test_baseline_binds_the_declared_gate_identity_to_the_committed_tree`, `tests/test_safe_commit.py::test_safe_commit_refuses_without_explicit_paths` and `tests/test_merge_queue.py::test_enqueue_refuses_an_unregistered_checkout`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 12
    },
    {
      "id": "RM-GOVERNANCE-R028",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Merge-queue promotion rechecks identity before reporting success",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "269c661d12fa"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Merge-queue promotion rechecks identity before reporting success.** The promotion rechecks the base commit and validation identity before merging, records the outcome, and handles a conflict or a crashed process without reporting a merge that did not happen. Caller chain: `merge-queue-runner.timer` and the `run` action call `run_queue` (`repository_manager/merge_queue.py:3583`), which calls `_drain_batch` (:3489) and `_drain_batch_under_lease` (:3517). Shape: a candidate whose base moved, whose patch conflicts or whose drain times out stays recorded for recovery; a killed drain does not strand the candidate. Depends on: `RM-GOVERNANCE-R027`. | Test: `tests/test_merge_queue.py::test_a_conflict_touching_a_handwritten_file_is_still_rejected`, `tests/test_merge_queue.py::test_a_killed_drain_does_not_strand_the_candidate` and `tests/test_merge_queue.py::test_a_baseline_timeout_is_a_refusal_not_an_empty_baseline`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 13
    },
    {
      "id": "RM-GOVERNANCE-R029",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Cleanup proves containment before deleting a branch checkout",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "e20bbf7b4ff5"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Cleanup proves containment before deleting a branch checkout.** Cleanup proves that a branch's commits are contained in the target before removal, or else keeps a durable recovery anchor, and never deletes an unmerged or dirty branch checkout by default. Caller chain: the `worktree` tool actions `audit` and `prune` call `WorktreeManager.audit` (`repository_manager/worktree.py:1548`) and `WorktreeManager.prune` (:1076), and `remove` (:771) deletes a checkout; `guarded_worktree_prune` (`repository_manager/prune_guard.py:121`) holds back a worktree whose lane holds a lease. Shape: an unmerged or dirty worktree is classified active and kept; a merged one is removed with only its own branch. Depends on: `RM-GOVERNANCE-R026`. | Test: `tests/test_worktree.py::test_audit_unmerged_ahead_is_active`, `tests/test_worktree.py::test_audit_dirty_worktree_is_active`, `tests/test_worktree.py::test_prune_merged_still_removes_a_genuinely_merged_worktree` and `tests/test_worktree.py::test_prune_skips_a_worktree_whose_lane_holds_a_lease`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 14
    },
    {
      "id": "RM-GOVERNANCE-R030",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Concept reservations are scoped and cannot be silently reused",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "0454cd888aac",
        "63c543e980dc"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Concept reservations are scoped and cannot be silently reused.** Each concept reservation is scoped to its repository and candidate identity, expires or releases safely, and is never silently reused by a different actor. Caller chain: the CLI and MCP concept actions call `concept_actions.dispatch` (`repository_manager/concept_actions.py:124`) through `concept_actions_for` (:98), which reaches the authority built by `build_default_concept_authority` (:65). Shape: the reservation types and typed conflicts live in `repository_manager/governance/concept_reservation.py` (`ConceptReservationConflict` :91, `ConceptReservationFenceConflict` :95, `ConceptReservationUnauthorized` :103); a duplicate or stale claim fails with a typed conflict. Depends on: `RM-GOVERNANCE-R024`. | Test: `tests/governance/test_concept_reservation_authority.py::test_fence_owner_and_terminal_visibility_are_enforced`, `tests/governance/test_concept_reservation_authority.py::test_concurrent_clients_have_one_winner_for_one_id` and `tests/governance/test_concept_reservation_authority.py::test_released_id_can_be_reclaimed_but_landed_id_cannot`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 15
    },
    {
      "id": "RM-GOVERNANCE-R003",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Cleanup removes isolated checkouts and scratch only after merge",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Cleanup removes isolated checkouts and scratch only after merge.** After a branch is fast-forwarded and fully contained in main with no uncommitted or untracked files, cleanup removes its isolated checkout, local branch, backup references and any host-local build scratch, and keeps a log of the cleanup run. Caller chain: the `worktree` tool action `prune` calls `WorktreeManager.prune` (`repository_manager/worktree.py:1076`) after `audit` (:1548) classifies the worktree as merged, and `remove` (:771) deletes the checkout and, with `delete_branch`, its branch. Shape: checkout and branch removal exist; removal of `refs/backup/*` references and of host-local build scratch has no code today and attaches to `remove` as a planned step; the cleanup log record is planned beside it. Depends on: `RM-GOVERNANCE-R029`. | Test: `tests/test_worktree.py::test_prune_merged_still_removes_a_genuinely_merged_worktree` covers the checkout and branch; `tests/test_worktree.py::test_cleanup_removes_backup_refs_scratch_and_writes_a_log` (planned) covers the rest.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 17
    },
    {
      "id": "RM-GOVERNANCE-R004",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Workspace check refuses credential-embedded remote URLs",
      "delivery_state": "VERIFIED",
      "state": "verified",
      "done": true,
      "landed_in": [
        "127a8384c249",
        "18fc4b20d3ea"
      ],
      "verified_by": [
        "tests/test_repository_manager.py:1167",
        "tests/test_repository_manager.py:1215"
      ],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Workspace check refuses credential-embedded remote URLs.** repository-manager refuses any Git remote URL embedding a username or token credential, strips such credentials from remote URLs it manages, and directs authentication through a credential helper or SSH deploy keys. Caller chain: `Git.clone_repository` (`repository_manager/repository_manager.py:2811`) calls `Git._credential_embedded_url_refusal` (:2854) before cloning, and managed checkouts have their origin rewritten by `Git._checkout_origin_without_credentials`. Shape: the refusal message redacts the secret; a failed sanitization is refused without secret diagnostics. Depends on: `RM-GOVERNANCE-R026`. | Test: `tests/test_repository_manager.py::test_managed_checkout_origin_is_sanitized_without_other_config_changes` and `tests/test_repository_manager.py::test_managed_checkout_refuses_failed_origin_sanitization_without_secret_diagnostics`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 18
    },
    {
      "id": "RM-GOVERNANCE-R007",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Routine cleanup prunes merged branches and build caches",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Routine cleanup prunes merged branches and build caches.** The cleanup routine removes checkouts and branches once merge containment is verified and prunes the local package-manager build cache as part of the same routine. Caller chain: the `worktree` tool action `prune` calls `WorktreeManager.prune` (`repository_manager/worktree.py:1076`); `repository_manager/disk_policy.py` only requests a bounded GC plan and never deletes files. Shape: checkout and branch pruning exist and the reachability check is `audit` (:1548); no code prunes the package-manager cache today, so that step is planned as a step of `prune`. Depends on: `RM-GOVERNANCE-R003`. | Test: `tests/test_worktree.py::test_worktree_hygiene_prune_removes_only_merged` covers pruning; `tests/test_worktree.py::test_prune_also_prunes_the_package_manager_cache` (planned) covers the cache step.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 21
    },
    {
      "id": "RM-GOVERNANCE-R013",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "A fast rebase must not silently skip the hook suite",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "127a8384c249",
        "8a96a9e0cfeb"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**A fast rebase must not silently skip the hook suite.** A `git rebase` that completes in about a second is treated as evidence that the hook suite did not run, not as a passing result; tooling distinguishes a genuine pass from a skipped hook run. Caller chain: the `worktree` tool action `sync` calls `WorktreeManager.sync` (`repository_manager/worktree.py:984`), which rebases and then runs the repository's declared gates on the result. Shape: a failing declared gate makes `sync` return `ok: False`; a passing gate is reported with its result rather than the rebase alone. Depends on: `RM-GOVERNANCE-R027`. | Test: `tests/test_worktree.py::test_sync_refuses_when_the_synced_tree_fails_its_declared_gates` and `tests/test_worktree.py::test_sync_reports_a_passing_declared_gate`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 27
    },
    {
      "id": "RM-GOVERNANCE-R014",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Completion claims require full hook-run logs as proof",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Completion claims require full hook-run logs as proof.** A claim that quality gates passed is backed by a complete, non-summary log of the hook run, and a run interrupted before completion is never cited as proof of a pass. Caller chain: `run_gate_stage` (`repository_manager/gates.py:686`) runs pre-commit and `_record_gate_run` (:464) writes one ledger row per gate through `GateLedger` (`repository_manager/gate_ledger.py`). Shape: the ledger stores a 4,000-character `output_tail` per hook (`gate_ledger.py:476`), not the full log; a run killed before completion records no passing verdict (`_gate_execution_exception_result` :587). Capturing the full output to a log file is planned. Depends on: `RM-GOVERNANCE-R022`. | Test: `tests/test_gates.py::test_full_hook_output_is_captured_and_an_interrupted_run_is_not_a_pass` (planned).",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 28
    },
    {
      "id": "RM-GOVERNANCE-R015",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Continuous review-and-merge replaces batch integration",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Continuous review-and-merge replaces batch integration.** Finished work is reviewed and merged to the main branch individually, other active contributors are notified, and they rebase onto the updated main branch, rather than accumulating changes for a single batch integration. Caller chain: the merge queue (`merge_queue.enqueue`, `repository_manager/merge_queue.py:802`) admits one candidate per branch and `WorktreeManager.sync` (`repository_manager/worktree.py:984`) rebases a contributor's worktree onto the updated base. Shape: the written protocol is the `Branches and pull requests` section of `AGENTS.md`; the notification step has no code in this repository and stays planned work; the written protocol is its proof. Depends on: `RM-GOVERNANCE-R013`. | Test: `tests/test_governance_protocol.py::test_protocol_names_review_merge_notify_rebase_in_order` (planned).",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 29
    },
    {
      "id": "RM-GOVERNANCE-R016",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Cleanup removes leftover backup references and build scratch",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Cleanup removes leftover backup references and build scratch.** Routine cleanup removes leftover `refs/backup/*` references and any host-local build scratch directories tied to a finished branch, in addition to the checkout and branch themselves. Caller chain: `WorktreeManager.remove` (`repository_manager/worktree.py:771`) is the attach point; no code in the package names `refs/backup` today. Shape: the removal enumerates `git for-each-ref refs/backup/` for the branch and deletes the host-local scratch directories of the branch. Depends on: `RM-GOVERNANCE-R003`. | Test: `tests/test_worktree.py::test_remove_deletes_backup_refs_and_build_scratch_of_the_branch` (planned).",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 30
    },
    {
      "id": "RM-GOVERNANCE-R017",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Build submission is asynchronous, not polling-based",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "127a8384c249",
        "8a96a9e0cfeb"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Build submission is asynchronous, not polling-based.** A contributor submits a build to the shared build queue and continues other work rather than polling for its result, with a bounded number of concurrent contributors matched against available build capacity through the queue. Caller chain: the `build` tool and CLI call `BuildService.submit` (`repository_manager/build_service.py:739`), which returns a direct cache hit or an immediate durable job handle and never waits (`del wait_timeout`). Shape: admission is bounded by the capacity profile in `repository_manager/capacity.py` and `repository_manager/build_queue.py`; the outcome is read later through the job handle. | Test: `tests/test_durable_build_broker.py::test_submission_is_immediate_and_bounded_by_the_same_capacity_profile`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 31
    },
    {
      "id": "RM-GOVERNANCE-R018",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Dependency-readiness hook works from any checkout location",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "3af7957a7a03",
        "d00c0834551e",
        "ff21c02187b0"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Dependency-readiness hook works from any checkout location.** The dependency-readiness pre-commit hook resolves its paths correctly when run from an isolated branch checkout, not only from the primary repository location. Caller chain: the `dependency-readiness` hook of `.pre-commit-config.yaml` runs `python -m repository_manager.dependency_readiness .`, which resolves the manifest through `_find_workspace_manifest` (`repository_manager/dependency_readiness.py:1149`). Shape: the packaged manifest copy resolves first, so a `start` path with no `workspace.yml` above it still resolves. | Test: `tests/test_dependency_readiness.py::test_find_workspace_manifest_resolves_from_a_location_with_no_ancestor_copy` and `tests/test_dependency_readiness.py::test_dependency_readiness_hook_exits_zero_from_an_isolated_worktree`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 32
    },
    {
      "id": "RM-GOVERNANCE-R019",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "A fix is accepted only when all quality gates pass together",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "127a8384c249",
        "8a96a9e0cfeb"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**A fix is accepted only when all quality gates pass together.** repository-manager accepts a change only when complexity, KISS, duplication, clone detection, compiler lint and the test suite all pass together, not individually. Caller chain: `run_gate_stage` (`repository_manager/gates.py:686`) runs `_run_pre_commit` (:235) over the declared hooks and parses the verdicts with `parse_gate_output` (:300); the stage is successful only when every hook passed. Shape: one failing hook makes `result.success` false while every hook's own verdict stays visible in `result.hooks`. | Test: `tests/test_gates.py::test_one_red_check_refuses_admission_even_though_the_rest_are_green`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 33
    },
    {
      "id": "RM-GOVERNANCE-R022",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "The repository passes its own full local gate suite",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "3f64278035a5",
        "b8d9c384efdc",
        "d62a408ce486"
      ],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**The repository passes its own full local gate suite.** repository-manager's codebase passes its own complete local pre-commit and pre-push gate suite at its current state, not a subset of checks. Caller chain: `Git._gate_before_push` (`repository_manager/repository_manager.py`) calls `gates._run_pre_commit` with the `pre-push` hook stage over `.pre-commit-config.yaml`, and `run_gate_stage` (`repository_manager/gates.py:686`) runs the named stages. Shape: the proof is one end-to-end run of the stage over this repository; each hook's verdict is read from the gate ledger. Depends on: `RM-GOVERNANCE-R019`. | Test: `tests/test_pre_push_gate.py::test_gate_runs_the_heavy_pre_push_stage`.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 36
    },
    {
      "id": "RM-GOVERNANCE-R023",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Heavy gates run on a leased slot of an inventory host",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Heavy gates run on a leased slot of an inventory host.** repository-manager runs each heavy gate or test on one host from the tunnel-manager inventory under a counted resource lease, and refuses the run when no host has a free slot. Children `.1` to `.6` deliver it. Production call site: the pre-push heavy gate step of `run_gate_stage` (`repository_manager/gates.py:686`) acquires the lease through the lane lease in `repository_manager/governance/lanes.py`. | Satisfied only when its child rows are verified.",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 37
    },
    {
      "id": "RM-GOVERNANCE-R023.1",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Typed host lease",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Typed host lease.** `HostLease` carries host id, resource name, slot index, capacity and fence token. Caller chain: `_admit_resource_lease` (`repository_manager/governance/lanes.py:2143`) builds the lease record through `_resource_record_base` (:1924), which already holds `host`, `resource`, `slot` and `capacity` as dict keys. Shape: a frozen dataclass `HostLease` is added next to `LeaseUnavailable` in `repository_manager/governance/lanes.py` (planned) and the record builder returns it. The fence token field reuses the lease's existing fence value. Depends on: `RM-GOVERNANCE-R025`. | Test: `tests/test_resource_lease.py::test_host_lease_fields` (planned).",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 38
    },
    {
      "id": "RM-GOVERNANCE-R023.2",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Read capacity from inventory",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Read capacity from inventory.** `load_host_capacity` reads each host's slot capacity for a named resource from the tunnel-manager `inventory.yml` and refuses a host with no declared capacity. Caller chain: `_admit_resource_lease` (`repository_manager/governance/lanes.py:2143`) calls `_validate_host_capacity` (:1568), which calls `_host_resource_capacity` (:1010) for the declared capacity. Shape: today the host identities and roles come from the JSON environment setting read by `_host_inventory` (:880); `load_host_capacity` (planned, same module) reads `inventory.yml` and is owned by tunnel-manager's file format; the planned reader takes the integer capacity the inventory declares per host for the named resource. Depends on: `RM-GOVERNANCE-R023.1`. | Test: `tests/test_resource_lease.py::test_capacity_read_from_inventory` (planned).",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 39
    },
    {
      "id": "RM-GOVERNANCE-R023.3",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Lease a slot per host",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Lease a slot per host.** `_free_resource_slot` counts slots per host, not only per machine, and a lane holds at most one slot of a resource at a time. Caller chain: `_admit_resource_lease` (`repository_manager/governance/lanes.py:2143`) calls `_free_resource_slot` (:1910), which walks `range(capacity)` over `_resource_lease_file` (:1800) in one lease directory. Shape: the lease directory becomes one directory per inventory host (planned), reusing `_resource_lease_file`; the one-slot-per-lane rule extends `_read_current_holder`. Depends on: `RM-GOVERNANCE-R023.2`. | Test: `tests/test_resource_lease.py::test_slot_counted_per_host` (planned).",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 40
    },
    {
      "id": "RM-GOVERNANCE-R023.4",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Refuse when no host has headroom",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Refuse when no host has headroom.** When every inventory host is at capacity, the lane waits in the queue or fails with a typed reason, and never runs the gate on an unleased host. Caller chain: `_admit_resource_lease` (`repository_manager/governance/lanes.py:2143`) raises `_lease_conflict` (:2134) when `_free_resource_slot` returns no candidate. Shape: the conflict is `LeaseUnavailable` today; it keeps that type and names every host's holder. Depends on: `RM-GOVERNANCE-R023.3`. | Test: `tests/test_resource_lease.py::test_all_hosts_full_refuses` (planned).",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 41
    },
    {
      "id": "RM-GOVERNANCE-R023.5",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Release on crash",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Release on crash.** An expired fence releases the slot, and a crashed gate process never keeps a slot beyond the lease time-to-live. Caller chain: the lease reclaim path of `repository_manager/governance/lanes.py` frees a dead or expired holder before `_free_resource_slot` runs. Shape: expiry uses the lease `ttl_seconds` recorded by `_resource_record_base`; a cross-host expiry is not reclaimed locally, as `tests/governance/test_lanes.py::test_cross_host_expiry_is_not_reclaimed_locally` fixes for the current record. Depends on: `RM-GOVERNANCE-R023.3`. | Test: `tests/governance/test_lanes.py::test_expired_lease_is_reclaimed` and `tests/test_resource_lease.py::test_expired_fence_releases_slot` (planned).",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 42
    },
    {
      "id": "RM-GOVERNANCE-R023.6",
      "kind": "requirement",
      "parent": "RM-GOVERNANCE",
      "source": "specs/development-governance/status.json",
      "title": "Wire into the gate runner",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-GOVERNANCE \u2014 Repository development governance",
      "definition": "**Wire into the gate runner.** The pre-push heavy gate step acquires a `HostLease` before it starts and releases it in a `finally` block. Caller chain: the pre-push gate calls `run_gate_stage` (`repository_manager/gates.py:686`), whose process runner `_run_gate_process` (:610) executes the hooks. Shape: the acquisition wraps `_run_gate_process` in a context manager over the lane lease (planned); the existing `_needs_build_reservation` (:573) is the check that decides whether a stage is heavy. Depends on: `RM-GOVERNANCE-R023.1`, `RM-GOVERNANCE-R023.4`. | Test: `tests/test_resource_lease.py::test_gate_runner_acquires_and_releases` (planned).",
      "definition_source": "specs/development-governance/requirements.md",
      "definition_line": 43
    },
    {
      "id": "RM-IDENTITY",
      "kind": "spec",
      "parent": null,
      "source": "specs/fleet-git-identity/status.json",
      "title": "RM-IDENTITY \u2014 Fleet Git identity and history reconciliation",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "document": "specs/fleet-git-identity/spec.md",
      "component": "History identity",
      "code_refs": [
        {
          "declared_in": "specs/fleet-git-identity/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/development/workspace_release.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/development/workspace_release.py"
        },
        {
          "declared_in": "specs/fleet-git-identity/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/governance/cli.py:156",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/governance/cli.py#L156"
        },
        {
          "declared_in": "specs/fleet-git-identity/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/history_identity/cli.py:223",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/history_identity/cli.py#L223"
        },
        {
          "declared_in": "specs/fleet-git-identity/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/merge_queue.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/merge_queue.py"
        },
        {
          "declared_in": "specs/fleet-git-identity/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/worktree.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/worktree.py"
        },
        {
          "declared_in": "specs/fleet-git-identity/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "scripts/check_complexity_staged.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/scripts/check_complexity_staged.py"
        },
        {
          "declared_in": "specs/fleet-git-identity/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "spec.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/fleet-git-identity/spec.md"
        },
        {
          "declared_in": "specs/fleet-git-identity/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "tests/history_identity_git_fixtures.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "test",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/tests/history_identity_git_fixtures.py"
        },
        {
          "declared_in": "specs/fleet-git-identity/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/governance/cli.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/governance/cli.py"
        },
        {
          "declared_in": "specs/fleet-git-identity/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "requirements.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/fleet-git-identity/requirements.md"
        }
      ],
      "relations": [],
      "plan_diagrams": [],
      "unparsed_references": []
    },
    {
      "id": "RM-IDENTITY-R001",
      "kind": "requirement",
      "parent": "RM-IDENTITY",
      "source": "specs/fleet-git-identity/status.json",
      "title": "Rewrite commit identities across public repositories with approval and rollback",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "8ee2778dcc35"
      ],
      "verified_by": [],
      "parent_title": "RM-IDENTITY \u2014 Fleet Git identity and history reconciliation",
      "definition": "**Rewrite commit identities across public repositories with approval and rollback.** An authorized maintainer can preview, and after explicit signed approval apply, a rewrite of every commit and tag author and committer identity across a selected set of public repositories, mapping the recognized maintainer and coding-agent aliases of the approved identity policy to their canonical identity while holding unclassified identities for explicit review. The rewrite preserves every commit's tree bytes, covers all branches and tags, creates a recoverable backup of the original refs, and publishes to each configured remote only after preview and approval succeed. Rollup of the apply path: the preview half is built (`RM-IDENTITY-R002`, `RM-IDENTITY-R003`, `RM-IDENTITY-R004`, `RM-IDENTITY-R005`) and the rewrite half is specified (`RM-IDENTITY-R006` to `RM-IDENTITY-R009`). Caller chain: a planned apply mode of the existing verb (`repository_manager/governance/cli.py:156`, handler `_history_identity` :566) calls a planned `run_rewrite` in `repository_manager/history_identity/rewrite.py` (planned), which runs `discover` (`repository_manager/history_identity/discovery.py:194`), `generate_preview` (`repository_manager/history_identity/preview.py:157`) and `verify_approval` (`repository_manager/history_identity/approval.py:106`) in that order before any mutation. Shape: `rewrite.py` (planned) holds one `run_rewrite` that composes the built discovery, preview and approval functions with the rows below; no second policy evaluator and no second ref enumerator is added; `IdentityPolicy` (`repository_manager/history_identity/policy.py:125`) stays the only policy type. Writes: backup refs, quarantine refs, then local and remote refs, in the order of `RM-IDENTITY-R007` and `RM-IDENTITY-R008`. Depends on: `RM-IDENTITY-R005`, `RM-IDENTITY-R006`, `RM-IDENTITY-R007`, `RM-IDENTITY-R008`, `RM-IDENTITY-R009`. | Test: `tests/test_history_identity_rewrite.py::test_rewrite_preserves_trees_and_backup_refs_restore_history` (planned). It rewrites a fixture repository with a bare remote and restores the original history from the backup refs.",
      "definition_source": "specs/fleet-git-identity/requirements.md",
      "definition_line": 5
    },
    {
      "id": "RM-IDENTITY-R002",
      "kind": "requirement",
      "parent": "RM-IDENTITY",
      "source": "specs/fleet-git-identity/status.json",
      "title": "Reconcile diverged history before identity rewrite",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "8ee2778dcc35"
      ],
      "verified_by": [],
      "parent_title": "RM-IDENTITY \u2014 Fleet Git identity and history reconciliation",
      "definition": "**Reconcile diverged history before identity rewrite.** A repository whose local branches share no common ancestor is refused admission to an identity-rewrite plan until its branch history is reconciled into one coherent history. The check is general; applying it to a particular repository is an operational step outside the code. Caller chain: the shell verb `repository-manager-governance history-identity` is parsed at `repository_manager/governance/cli.py:156`, dispatched through `_COMMAND_HANDLERS` (:593) to `_history_identity` (:566), which calls `run_preview` (`repository_manager/history_identity/cli.py:223`), which calls `check_history_consistency` (`repository_manager/history_identity/consistency.py:70`) and `admit_for_rewrite_plan` (:86) per repository inside `_preview_one_repo` (`repository_manager/history_identity/cli.py:144`); a `HistoryConsistencyError` becomes a report with `exit_code` 1 and no preview. Shape: `check_history_consistency` lists `refs/heads/` through `GitRunner.run` (`discovery.py:56`) and asks `git merge-base` for every branch pair through `itertools.combinations`; the result is a frozen `ConsistencyReport` with `DivergedBranchPair` entries. The reconciliation itself (merging or rebasing a diverged branch) is not part of this row. | Test: `tests/test_history_identity_consistency.py::test_check_history_consistency_detects_an_orphan_branch`, `tests/test_history_identity_consistency.py::test_admit_for_rewrite_plan_raises_on_a_diverged_report` and `tests/test_history_identity_cli.py::test_history_identity_cli_refuses_on_diverged_history`.",
      "definition_source": "specs/fleet-git-identity/requirements.md",
      "definition_line": 6
    },
    {
      "id": "RM-IDENTITY-R003",
      "kind": "requirement",
      "parent": "RM-IDENTITY",
      "source": "specs/fleet-git-identity/status.json",
      "title": "Complete ref and tag discovery before rewrite",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "8ee2778dcc35",
        "9a933f61ad22"
      ],
      "verified_by": [],
      "parent_title": "RM-IDENTITY \u2014 Fleet Git identity and history reconciliation",
      "definition": "**Complete ref and tag discovery before rewrite.** Before any identity rewrite, the tool enumerates every local ref, annotated and lightweight tag, remote-tracking ref, note ref and signed object in the selected repository set, and refuses to proceed when discovery is incomplete or the repository state is divergent. Caller chain: the shell verb `repository-manager-governance history-identity` is parsed at `repository_manager/governance/cli.py:156`, dispatched through `_COMMAND_HANDLERS` (:593) to `_history_identity` (:566), which calls `run_preview` (`repository_manager/history_identity/cli.py:223`), which calls `discover` (`repository_manager/history_identity/discovery.py:194`) through `_preview_one_repo` (`cli.py:144`). Shape: `discover` runs `_reject_divergent_state` (:124: shallow clone, legacy grafts file, divergent ref prefixes), `_enumerate_refs` (:147: `git for-each-ref refs/`, one `RefRecord` per ref with its kind and `signed` flag from `_is_signed` :137, and a refusal for a ref of no known prefix) and `_enumerate_and_verify_remotes` (:171: `git ls-remote --exit-code` per remote), then returns a `RepositoryDiscovery` whose `digest` (`_digest` :185) is a sha256 over the sorted refs and remotes. Git is called only through the injected `GitRunner` (`SubprocessGitRunner` by default). | Test: `tests/test_history_identity_discovery.py::test_discover_enumerates_branches_tags_remotes_and_notes`, `tests/test_history_identity_discovery.py::test_discover_refuses_hidden_ref`, `tests/test_history_identity_discovery.py::test_discover_refuses_unreadable_ref`, `tests/test_history_identity_discovery.py::test_discover_refuses_unreachable_remote`, `tests/test_history_identity_discovery.py::test_discover_refuses_shallow_clone`, `tests/test_history_identity_discovery.py::test_discover_detects_a_signed_commit` and `tests/test_history_identity_cli.py::test_history_identity_cli_refuses_on_incomplete_discovery`.",
      "definition_source": "specs/fleet-git-identity/requirements.md",
      "definition_line": 7
    },
    {
      "id": "RM-IDENTITY-R004",
      "kind": "requirement",
      "parent": "RM-IDENTITY",
      "source": "specs/fleet-git-identity/status.json",
      "title": "Deterministic dry-run identity rewrite plan",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "8ee2778dcc35",
        "9a933f61ad22"
      ],
      "verified_by": [],
      "parent_title": "RM-IDENTITY \u2014 Fleet Git identity and history reconciliation",
      "definition": "**Deterministic dry-run identity rewrite plan.** The tool produces a deterministic dry-run plan mapping old identities to new ones and old refs, commits and tags to their rewritten equivalents, reporting counts, affected authors and committers, unchanged tree digests and any collision warnings. Caller chain: the shell verb `repository-manager-governance history-identity` is parsed at `repository_manager/governance/cli.py:156`, dispatched through `_COMMAND_HANDLERS` (:593) to `_history_identity` (:566), which calls `run_preview` (`repository_manager/history_identity/cli.py:223`), which calls `build_policy` (`repository_manager/history_identity/policy.py:193`) and `generate_preview` (`repository_manager/history_identity/preview.py:157`) through `_preview_one_repo` (`cli.py:144`) and renders `_preview_report` (:160). Shape: `generate_preview` lists every commit of `git log --all` (`_enumerate_commits` :85), resolves author and committer through `IdentityPolicy.resolve` (`policy.py:166`; exact name and email only, an unmatched identity resolves to `None`), records `signed_shas` from the discovery, warns per unmapped identity in `_collision_warnings` (:120), and folds the discovery digest, the policy digest, the remotes and the expiry into the plan `digest` (:134). The plan lists identity mappings per commit; the old-to-new commit, tag and ref maps and the tree digests belong to the rewrite engine of `RM-IDENTITY-R006`, which computes them. Depends on: `RM-IDENTITY-R003`. | Test: `tests/test_history_identity_preview.py::test_generate_preview_is_deterministic_across_runs`, `tests/test_history_identity_preview.py::test_generate_preview_digest_changes_when_source_mutates`, `tests/test_history_identity_preview.py::test_generate_preview_surfaces_collision_warning_for_unmapped_identity`, `tests/test_history_identity_preview.py::test_generate_preview_folds_policy_digest_and_is_sensitive_to_policy_change`, `tests/test_history_identity_cli.py::test_history_identity_cli_output_is_deterministic_across_two_runs` and `tests/test_history_identity_cli.py::test_history_identity_cli_surfaces_unmapped_identity_without_refusing`.",
      "definition_source": "specs/fleet-git-identity/requirements.md",
      "definition_line": 8
    },
    {
      "id": "RM-IDENTITY-R005",
      "kind": "requirement",
      "parent": "RM-IDENTITY",
      "source": "specs/fleet-git-identity/status.json",
      "title": "Signed approval required before any rewrite",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "8ee2778dcc35",
        "9a933f61ad22"
      ],
      "verified_by": [],
      "parent_title": "RM-IDENTITY \u2014 Fleet Git identity and history reconciliation",
      "definition": "**Signed approval required before any rewrite.** The rewrite only runs after a signed or otherwise authenticated approval that is bound to the exact repository set, source ref digests, identity policy digest, target remotes and an expiry time. Caller chain: the shell verb `repository-manager-governance history-identity` is parsed at `repository_manager/governance/cli.py:156`, dispatched through `_COMMAND_HANDLERS` (:593) to `_history_identity` (:566), which calls `run_preview` (`repository_manager/history_identity/cli.py:223`), which, when `--approval` is given, calls `_verify_approval_or_refusal` (`repository_manager/history_identity/cli.py:184`) and `verify_approval` (`repository_manager/history_identity/approval.py:106`) with the key read from the environment variable named by `--approval-key-env` (default `RM_HISTORY_IDENTITY_APPROVAL_KEY`). Shape: `ApprovalBinding` (`approval.py:27`) holds the sorted repository IDs, the combined source digest (`_combined_source_digest` `cli.py:119`), the policy digest, the sorted remotes and the expiry; `verify_approval` checks the binding (`_reject_if_unbound` :79), the expiry (`_reject_if_expired` :92) and an HMAC-SHA256 signature compared with `hmac.compare_digest` (`_reject_if_forged` :100), in that order, and any `ApprovalError` becomes a refusal with `exit_code` 1. The signature mechanism is an HMAC over a shared key; a different authenticated mechanism is an owner decision. Depends on: `RM-IDENTITY-R004`. | Test: `tests/test_history_identity_approval.py::test_verify_approval_accepts_a_valid_matching_signature`, `tests/test_history_identity_approval.py::test_verify_approval_rejects_missing_approval`, `tests/test_history_identity_approval.py::test_verify_approval_rejects_expired_approval`, `tests/test_history_identity_approval.py::test_verify_approval_rejects_a_forged_signature`, `tests/test_history_identity_approval.py::test_verify_approval_rejects_the_wrong_key`, `tests/test_history_identity_cli.py::test_history_identity_cli_refuses_on_a_missing_approval_key` and `tests/test_history_identity_cli.py::test_history_identity_cli_refuses_an_approval_bound_to_a_different_plan`. The rewrite-side proof that a refused approval performs zero mutations, `tests/test_history_identity_rewrite.py::test_missing_expired_or_altered_approval_mutates_nothing`, is planned.",
      "definition_source": "specs/fleet-git-identity/requirements.md",
      "definition_line": 9
    },
    {
      "id": "RM-IDENTITY-R006",
      "kind": "requirement",
      "parent": "RM-IDENTITY",
      "source": "specs/fleet-git-identity/status.json",
      "title": "Byte-identical trees and preserved history topology",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "8ee2778dcc35"
      ],
      "verified_by": [],
      "parent_title": "RM-IDENTITY \u2014 Fleet Git identity and history reconciliation",
      "definition": "**Byte-identical trees and preserved history topology.** Every rewritten commit keeps a byte-identical tree object and preserves its parent order, message and timestamp, and tag payload semantics are preserved where possible; a signed commit or tag is rewritten only when the approval for that run explicitly authorizes re-signing, and otherwise it is reported and left unchanged. Caller chain: planned `run_rewrite` (`repository_manager/history_identity/rewrite.py`, planned; see `RM-IDENTITY-R001`) calls a planned independent verifier `verify_rewrite` in `repository_manager/history_identity/verify.py` (planned) after the quarantined rewrite and before the local ref update of `RM-IDENTITY-R007`. Shape: `verify.py` (planned) compares every old and new commit with `git rev-parse <sha>^{tree}`, the parent list and the message and timestamps, using `GitRunner` (`repository_manager/history_identity/discovery.py:56`) and the `signed_shas` already recorded by `HistoryPreview` (`repository_manager/history_identity/preview.py:63`); it shares no code with the rewrite function so the engine cannot grade its own output. Refusals: a mismatch stops the run before any ref update. Depends on: `RM-IDENTITY-R004`. | Test: `tests/test_history_identity_verify.py::test_every_rewritten_commit_keeps_tree_parents_message_and_timestamps` (planned). It covers merges with several parents, author and committer aliases and annotated tags.",
      "definition_source": "specs/fleet-git-identity/requirements.md",
      "definition_line": 10
    },
    {
      "id": "RM-IDENTITY-R007",
      "kind": "requirement",
      "parent": "RM-IDENTITY",
      "source": "specs/fleet-git-identity/status.json",
      "title": "Quarantined staging with backup refs before ref update",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-IDENTITY \u2014 Fleet Git identity and history reconciliation",
      "definition": "**Quarantined staging with backup refs before ref update.** Before updating any ref, the tool writes immutable, collision-safe backup refs and a durable object map, stages the rewritten refs in quarantine, verifies their reachability, and only then updates each repository's refs atomically. Caller chain: planned `run_rewrite` (`repository_manager/history_identity/rewrite.py`, planned) calls a planned `stage_and_update` in `repository_manager/history_identity/transaction.py` (planned) after `verify_rewrite` of `RM-IDENTITY-R006` passes. Shape: `transaction.py` (planned) creates the backup namespace and the quarantine namespace with `git update-ref --stdin` batches through the injected `GitRunner` (`repository_manager/history_identity/discovery.py:56`), writes the object map as a content-addressed file, and applies the final ref update as one `update-ref --stdin` transaction with expected old values; a failure before that transaction removes only quarantine refs. Backup refs are never deleted by this change. Depends on: `RM-IDENTITY-R006`. | Test: `tests/test_history_identity_transaction.py::test_failure_before_update_leaves_old_refs_and_backups_restore_after_update` (planned).",
      "definition_source": "specs/fleet-git-identity/requirements.md",
      "definition_line": 11
    },
    {
      "id": "RM-IDENTITY-R008",
      "kind": "requirement",
      "parent": "RM-IDENTITY",
      "source": "specs/fleet-git-identity/status.json",
      "title": "Lease-protected per-remote publication receipts",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-IDENTITY \u2014 Fleet Git identity and history reconciliation",
      "definition": "**Lease-protected per-remote publication receipts.** Publication to each configured remote uses a lease-protected ref update and records a per-remote outcome receipt, and the tool never reports fleet-wide success when any remote publication is only partially complete. A protected ref that rejects the update is reported as refused for that remote; the tool never lifts branch protection. Caller chain: planned `run_rewrite` (`repository_manager/history_identity/rewrite.py`, planned) calls a planned `publish_remotes` in `repository_manager/history_identity/publish.py` (planned) after the local transaction of `RM-IDENTITY-R007`. Shape: `publish.py` (planned) runs `git push --force-with-lease=<ref>:<expected old sha>` per ref and per remote through `GitRunner` (`repository_manager/history_identity/discovery.py:56`), takes the expected old values from the `RepositoryDiscovery` (`discovery.py:108`) bound by the approval, and returns one receipt per remote with the states complete, partial, refused or pending plus reconciliation instructions. Depends on: `RM-IDENTITY-R007`. | Test: `tests/test_history_identity_publish.py::test_remote_drift_and_rejected_branch_yield_partial_receipt_not_success` (planned).",
      "definition_source": "specs/fleet-git-identity/requirements.md",
      "definition_line": 12
    },
    {
      "id": "RM-IDENTITY-R009",
      "kind": "requirement",
      "parent": "RM-IDENTITY",
      "source": "specs/fleet-git-identity/status.json",
      "title": "Coordinated merge-queue pause and resync during rewrite",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-IDENTITY \u2014 Fleet Git identity and history reconciliation",
      "definition": "**Coordinated merge-queue pause and resync during rewrite.** While a rewrite is in flight, the tool pauses active merge queues, notifies and refreshes open pull-request branches and forks, and resynchronizes release baselines, resuming queue activity only after remote and CI verification confirm the new history. Caller chain: planned `run_rewrite` (`repository_manager/history_identity/rewrite.py`, planned) calls the merge queue through `merge_queue.dispatch` (`repository_manager/merge_queue.py:3621`), whose action table (:3626) has no pause action today. Shape: `pause` and `resume` are two explicit queue operations: two planned rows join that table beside `enqueue`, `status`, `withdraw`, `run` and `config`, each with one implementation, one CLI verb and, through the per-action split of the queue tool, one MCP tool (`rm_merge_queue_pause`, `rm_merge_queue_resume`); while paused, `run_queue` (:3583) and `enqueue` (:802) refuse a candidate based on the pre-rewrite history. Notifying contributors and refreshing open pull-request branches and forks has no existing helper (`repository_manager/forge_status.py` reads hosted CI status only); the notice channel, its wording and the branch refresh mechanism are an owner decision. Depends on: `RM-IDENTITY-R008`. | Test: `tests/test_history_identity_coordination.py::test_no_queued_candidate_merges_against_stale_history` (planned).",
      "definition_source": "specs/fleet-git-identity/requirements.md",
      "definition_line": 13
    },
    {
      "id": "RM-RELEASE",
      "kind": "spec",
      "parent": null,
      "source": "specs/fleet-release/status.json",
      "title": "RM-RELEASE \u2014 Dependency aware fleet release",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "document": "specs/fleet-release/spec.md",
      "component": "Fleet release",
      "code_refs": [
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "contracts/downstream-readiness.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/fleet-release/contracts/downstream-readiness.md"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/cli_commands/parser.py:46",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/cli_commands/parser.py#L46"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/cli_commands/rollout.py:57",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/cli_commands/rollout.py#L57"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/development/fleet_evidence_provider.py:33",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/development/fleet_evidence_provider.py#L33"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/development/fleet_manifest.py:418",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/development/fleet_manifest.py#L418"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/development/fleet_release_gate.py:250",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/development/fleet_release_gate.py#L250"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/development/workspace_release.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/development/workspace_release.py"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/development/workspace_release.py:1967",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/development/workspace_release.py#L1967"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/development/workspace_release_plan.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/development/workspace_release_plan.py"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/development/workspace_release_plan.py:4513",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/development/workspace_release_plan.py#L4513"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_tools/rollout.py:23",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_tools/rollout.py#L23"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/rollout.py:962",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/rollout.py#L962"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/workspace_manifest.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/workspace_manifest.py"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "scripts/check_complexity_staged.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/scripts/check_complexity_staged.py"
        },
        {
          "declared_in": "specs/fleet-release/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "spec.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/fleet-release/spec.md"
        },
        {
          "declared_in": "specs/fleet-release/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/dependency_readiness.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/dependency_readiness.py"
        },
        {
          "declared_in": "specs/fleet-release/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/rollout.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/rollout.py"
        },
        {
          "declared_in": "specs/fleet-release/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "requirements.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/fleet-release/requirements.md"
        }
      ],
      "relations": [],
      "plan_diagrams": [],
      "unparsed_references": []
    },
    {
      "id": "RM-RELEASE-R001",
      "kind": "requirement",
      "parent": "RM-RELEASE",
      "source": "specs/fleet-release/status.json",
      "title": "Dependency-ordered fleet release planning",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "c930dfd5c01a"
      ],
      "verified_by": [],
      "parent_title": "RM-RELEASE \u2014 Dependency aware fleet release",
      "definition": "**Dependency-ordered fleet release planning.** A maintainer can release a selected set of repositories in an order derived from declared and observed dependency edges, producing a census of each repository's package, version source and dependency group and rejecting cycles before any mutation. Caller chain: the release planner is a library path with no CLI or MCP verb: `capture_complete_manifest_census` (`repository_manager/development/fleet_manifest.py:418`) builds the census, `build_dependency_graph` (`repository_manager/development/workspace_release.py:1967`) builds the graph, `build_frozen_release_plan` (`repository_manager/development/workspace_release_plan.py:4513`) freezes the plan, and `ReadOnlyFleetEvidenceProvider` (`repository_manager/development/fleet_evidence_provider.py:33`) calls `prepare_fleet_release` (`repository_manager/development/fleet_release_gate.py:250`), which refuses while `FLEET_RELEASE_ACTIVATION` (:31) is not `open`. Shape: the types are `DependencyGraph` and `WorkspaceReleasePlan` (`workspace_release.py:1070`, :721) and `FrozenReleasePlan`; one planner exists and no second ordering is added. Depends on: `RM-RELEASE-R002`, `RM-RELEASE-R003`, `RM-RELEASE-R004`. | Test: `tests/test_fleet_release_gate.py::test_incomplete_census_refuses_before_any_live_release_authority` and `tests/test_fleet_evidence_provider.py::test_current_manifest_without_verified_metadata_refuses`.",
      "definition_source": "specs/fleet-release/requirements.md",
      "definition_line": 5
    },
    {
      "id": "RM-RELEASE-R002",
      "kind": "requirement",
      "parent": "RM-RELEASE",
      "source": "specs/fleet-release/status.json",
      "title": "Complete per-repository dependency census",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "c930dfd5c01a"
      ],
      "verified_by": [],
      "parent_title": "RM-RELEASE \u2014 Dependency aware fleet release",
      "definition": "**Complete per-repository dependency census.** The census records each selected repository's package identity, version source, dependency group and production source observations across Python, Rust and JavaScript/TypeScript, makes any missing or contradictory metadata explicit, and derives expected agent identities from the canonical repository manifest, rejecting identity drift before generating documentation. Caller chain: `capture_census` (`repository_manager/development/fleet_census.py:551`) reads each source through `_read_source` (:114) and returns a `CensusReceipt` (:79) whose `complete` flag stays false without an independent proof from `capture_source_universe` (`repository_manager/development/fleet_source_universe.py:162`); the documentation-readiness action reaches the manifest identities through `repository_manager/docs_readiness.py` from the CLI `run_docs_readiness_cli` and the MCP docs-readiness tool. Shape: one `EdgeObservation` per observed edge with its dependency class; the independent Git-tree proof is `verify_source_universe` (:200); identity drift is refused before the generator runs. Depends on: `RM-RELEASE-R001`. | Test: `tests/test_fleet_census.py::test_bounded_census_captures_four_evidence_families`, `tests/test_fleet_source_universe.py::test_extra_tracked_source_refuses_manifest_self_attestation` and `tests/test_docs_readiness_fleet_action.py::test_manifest_selection_drift_fails_closed_before_generator`.",
      "definition_source": "specs/fleet-release/requirements.md",
      "definition_line": 6
    },
    {
      "id": "RM-RELEASE-R003",
      "kind": "requirement",
      "parent": "RM-RELEASE",
      "source": "specs/fleet-release/status.json",
      "title": "Acyclic, typed dependency graph per release scope",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "c930dfd5c01a"
      ],
      "verified_by": [],
      "parent_title": "RM-RELEASE \u2014 Dependency aware fleet release",
      "definition": "**Acyclic, typed dependency graph per release scope.** The planner builds a directed dependency graph with edges classified as runtime, build, development, optional, deployment or frontend, and rejects any cycle within a declared release scope rather than silently dropping an edge to force acyclicity. Caller chain: `build_dependency_graph` (`repository_manager/development/workspace_release.py:1967`) runs `_topological_groups` (:2107) and raises through `_cycle_diagnostic` (:2077) before it returns a graph; the fleet order raises `FleetCycleError` (:2366) from `build_fleet_order_receipt` (:2605); the per-repository phase direction is checked by `check_phase_direction` (`repository_manager/dependency_readiness.py:2016`). Shape: the diagnostics are typed `Diagnostic` values (`workspace_release.py:73`) with a `GraphDiagnosticCode` (:54); no edge is dropped to reach acyclicity. Depends on: `RM-RELEASE-R002`. | Test: `tests/test_workspace_release_dag.py::test_cycle_refuses_before_a_graph_is_returned`, `tests/test_fleet_order_receipt.py::test_fleet_scc_census_reports_each_exact_component` and `tests/test_phase_direction.py::test_phase4_runtime_dependency_on_phase5_package_fails`.",
      "definition_source": "specs/fleet-release/requirements.md",
      "definition_line": 7
    },
    {
      "id": "RM-RELEASE-R004",
      "kind": "requirement",
      "parent": "RM-RELEASE",
      "source": "specs/fleet-release/status.json",
      "title": "Immutable, content-addressed release plan digest",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "c930dfd5c01a"
      ],
      "verified_by": [],
      "parent_title": "RM-RELEASE \u2014 Dependency aware fleet release",
      "definition": "**Immutable, content-addressed release plan digest.** The release plan binds the selected repository identities, their source revisions, the manifest and census digests, the dependency-edge evidence, the stage order and any version-floor rewrite into one immutable plan digest. Caller chain: `build_frozen_release_plan` (`repository_manager/development/workspace_release_plan.py:4513`) builds the plan and `plan_digest` (`repository_manager/development/workspace_release.py:1381`) computes the digest; `bind_fleet_release_plan` (`workspace_release_plan.py:4600`) is called by `prepare_fleet_release` (`fleet_release_gate.py:250`) to bind the fleet order to the plan. Shape: canonical payloads are sorted before hashing through `_canonical_json` (`workspace_release.py:1377`) and one digest serializer serves every route; a stale or tampered plan is rejected on reconstruction. Depends on: `RM-RELEASE-R001`. | Test: `tests/test_workspace_release_plan.py::test_plan_digest_and_stages_are_independent_of_input_order`, `tests/test_workspace_release_plan.py::test_profile_source_and_consent_changes_change_exact_digest` and `tests/test_fleet_order_receipt.py::test_fleet_plan_binding_rejects_stale_or_tampered_order`.",
      "definition_source": "specs/fleet-release/requirements.md",
      "definition_line": 8
    },
    {
      "id": "RM-RELEASE-R005",
      "kind": "requirement",
      "parent": "RM-RELEASE",
      "source": "specs/fleet-release/status.json",
      "title": "Dependency-ordered execution with trusted gating",
      "delivery_state": "VERIFIED",
      "state": "verified",
      "done": true,
      "landed_in": [
        "6af745687490",
        "c930dfd5c01a"
      ],
      "verified_by": [
        "tests/test_dependency_readiness.py:648",
        "tests/test_dependency_readiness.py:667",
        "tests/test_dependency_readiness.py:687",
        "tests/test_dependency_readiness.py:736",
        "tests/test_dependency_readiness.py:751"
      ],
      "parent_title": "RM-RELEASE \u2014 Dependency aware fleet release",
      "definition": "**Dependency-ordered execution with trusted gating.** Setup, install, validation, build, publication and downstream-readiness steps execute in dependency order, and no stage mutates a repository unless it holds a complete, current plan and trusted publication evidence from its predecessors. Downstream readiness follows the pipelines wheel rule (`PIPE-RELEASE-R008`): a dependency version is available when it has a wheel compatible with the target interpreter or platform; a missing sdist on that version is the advisory `sdist_missing`, not a failure; a version with only an sdist, or with no compatible wheel, fails unless the consumer lists the package in `[tool.pipelines] allow-source-build`; `partial_publish` applies only while the forge reports that version's release run as in progress. Caller chain: the `dependency-readiness` hook of `.pre-commit-config.yaml` and the release barrier call `check_constraint` (`repository_manager/dependency_readiness.py:2523`), which applies `_WheelRule` (:2247) and asks `forge_release_run_probe` (:2721) for a run in progress; stage permits come from `authorize_fleet_stage` (`repository_manager/development/fleet_release_gate.py:300`). Shape: the staged executor that runs each stage is not built; the permit and the readiness check are the built gates. Depends on: `RM-RELEASE-R004`. | Test: `tests/test_dependency_readiness.py::test_wheel_without_sdist_passes_with_the_sdist_missing_advisory`, `tests/test_dependency_readiness.py::test_sdist_only_version_fails`, `tests/test_dependency_readiness.py::test_sdist_only_version_on_the_allow_list_passes`, `tests/test_dependency_readiness.py::test_in_progress_release_run_reports_partial_publish` and `tests/test_dependency_readiness.py::test_concluded_run_with_a_wheel_passes_without_asking_the_forge`. The stage-blocking proof `tests/test_fleet_release_gate.py::test_stale_predecessor_blocks_dependent_stage` is planned.",
      "definition_source": "specs/fleet-release/requirements.md",
      "definition_line": 9
    },
    {
      "id": "RM-RELEASE-R006",
      "kind": "requirement",
      "parent": "RM-RELEASE",
      "source": "specs/fleet-release/status.json",
      "title": "One shared admission contract across release routes",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "d418380165cf"
      ],
      "verified_by": [],
      "parent_title": "RM-RELEASE \u2014 Dependency aware fleet release",
      "definition": "**One shared admission contract across release routes.** The Git, CLI and MCP release routes all share the same admission and executor contract, and a failed activation leaves the prior route fully in place with no partially switched entry point. Caller chain: every legacy route calls `require_legacy_release_route` (`repository_manager/development/fleet_release_gate.py:38`) before an effect: the setup route (`repository_manager/repository_manager.py:865`), the install route (:1832), `Git.push_project`, the MCP workspace tool (`repository_manager/mcp_tools/workspace.py:48`) and the MCP projects tool (`repository_manager/mcp_tools/projects.py:22`); the CLI reaches the same `Git` methods. Shape: while activation is `closed_pending_source_universe_proof` the legacy selection is preserved; once open, the legacy route raises `FleetReleaseGateError` before creating a job and only a stage permit executes. The route registry switch itself is not built. | Test: `tests/test_fleet_release_gate.py::test_open_cutover_refuses_legacy_git_routes_before_effect` and `tests/test_fleet_release_gate.py::test_closed_cutover_preserves_legacy_route_selection`.",
      "definition_source": "specs/fleet-release/requirements.md",
      "definition_line": 10
    },
    {
      "id": "RM-RELEASE-R007",
      "kind": "requirement",
      "parent": "RM-RELEASE",
      "source": "specs/fleet-release/status.json",
      "title": "Per-stage receipts with retry and rollback evidence",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "c930dfd5c01a"
      ],
      "verified_by": [],
      "parent_title": "RM-RELEASE \u2014 Dependency aware fleet release",
      "definition": "**Per-stage receipts with retry and rollback evidence.** Each release stage records the exact artifact and repository identity it acted on, its outcome, a retry key and the rollback or repair action available for it. Caller chain: the durable job service `RepositoryJobService` (`repository_manager/development/jobs.py:1384`) records each job's identity and outcome, `retry` derives the key `retry:<job_id>:<attempt>` (:1248) and `reconcile` (:1711) proposes an idempotent repair with the key `repair:<digest>` (:1749). Shape: the retry key, the repair proposal and the reconciliation classes exist for repository jobs; a release-stage receipt type that carries the artifact digest and the rollback action is not built, and injected push failures are covered through the job path. Depends on: `RM-RELEASE-R005`. | Test: `tests/test_repository_job_service.py::test_reconcile_enqueues_idempotent_follow_up_without_inline_mutation`, `tests/test_repository_job_service.py::test_retry_chain_consumes_the_original_budget_without_replenishing_it` and `tests/test_durable_build_broker.py::test_worker_surfaces_release_reconciliation_without_rerunning`.",
      "definition_source": "specs/fleet-release/requirements.md",
      "definition_line": 11
    },
    {
      "id": "RM-RELEASE-R008",
      "kind": "requirement",
      "parent": "RM-RELEASE",
      "source": "specs/fleet-release/status.json",
      "title": "Publish this package only from version tags",
      "delivery_state": "VERIFIED",
      "state": "verified",
      "done": true,
      "landed_in": [
        "14869f0f7de5",
        "bbd7f22f1b5a"
      ],
      "verified_by": [
        "tests/test_package_publication_workflow.py:9"
      ],
      "parent_title": "RM-RELEASE \u2014 Dependency aware fleet release",
      "definition": "**Publish this package only from version tags.** Repository Manager invokes the shared Python publication workflow only for pushed v-prefixed tags, requires its tag admission check, and retains its exact-source and conflicting-tag and secret checks unchanged. Ordinary main pushes and pull requests run source CI without publishing. Caller chain: a push event on GitHub runs `.github/workflows/connector.yml`, whose `pipeline` job delegates to the shared connector pipeline; the tag filter `v*` selects publication and the branch filter `main` selects source CI. Shape: `connector.yml` is the only source CI caller besides `windows-ci.yml`; the secrets wiring is left unchanged. Release tags are created by the bumper and the owner, and existing tags stay immutable. | Test: `tests/test_package_publication_workflow.py::test_source_ci_still_validates_main_and_pull_requests` and `tests/test_package_publication_workflow.py::test_connector_workflow_is_the_only_source_ci_caller`.",
      "definition_source": "specs/fleet-release/requirements.md",
      "definition_line": 12
    },
    {
      "id": "RM-RELEASE-R009",
      "kind": "requirement",
      "parent": "RM-RELEASE",
      "source": "specs/fleet-release/status.json",
      "title": "Deterministic, resumable dependency-floor rollout through PRs",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "387008605a4c",
        "459ef9f61397",
        "a64b95f87b4e"
      ],
      "verified_by": [],
      "parent_title": "RM-RELEASE \u2014 Dependency aware fleet release",
      "definition": "**Deterministic, resumable dependency-floor rollout through PRs.** `repository-manager rollout --dependency D --floor X` (MCP `rm_rollout`, actions plan, apply, status and release; one shared core `rollout.run_rollout_action`) selects the workspace manifest group (selector or subdirectory prefix, default `agent-connectors`) intersected with the forge's non-archived repositories and with repositories whose default-branch `pyproject.toml` declares D. It plans each repository from the forge into an append-only JSONL ledger under the XDG state directory keyed by (dependency, floor, repository). Apply, in a fresh `git worktree add` off `origin/<default>` with bounded parallelism, sets `>=X,<next-minor`, runs `uv lock --upgrade-package D --refresh` and fails the row unless the lock resolves D at X or above, patch-bumps through the bumpversion config and Dockerfile pins, adds a CHANGELOG entry, regenerates `specs/*/status.json` with `pipelines-hook spec-status --write`, runs pre-commit, commits an explicit file list with the repository's configured identity (never a coding-agent identity), pushes, opens a PR and arms `gh pr merge --auto --rebase`. It never pushes to main, never stashes and never uses `git add -A`. A re-run resumes: an open or merged rollout PR or an already-pushed branch is adopted, never duplicated or re-bumped. `status` reports merged, failing with failing check names, or pending. `release` tags `v<version>` on main's HEAD only after the PR merged and main's floor is at X or above, skipping existing tags. Caller chain: the console script `repository-manager` dispatches `rollout` at `repository_manager/cli_commands/parser.py:46` to `run_rollout_cli` (`repository_manager/cli_commands/rollout.py:57`); the MCP tool `rm_rollout` (`repository_manager/mcp_tools/rollout.py:23`) calls the same `run_rollout_action` (`repository_manager/rollout.py:962`), which drives `Rollout.plan` (:554), `apply` (:578), `status` (:842) and `release` (:877). Shape: all process calls go through the injectable `Runner` protocol (:72) with `subprocess_runner` (:82) as the default, so the fakes of the tests replace git, gh, uv and pre-commit; the ledger is `Ledger` (:317); the default runtime manifest is the arbora runtime copy, with no fallback to a former location. After the patch bump the apply step re-runs `uv lock` without upgrade so `uv.lock` records the package's new own version, runs the repository's full pre-commit (also the relocated `.config/pre-commit.yaml`, through `uvx` when absent) and stages every hook-rewritten file by explicit path. | Test: `tests/test_rollout.py::test_apply_opens_one_pr_with_bump_changelog_and_status_regen`, `tests/test_rollout.py::test_resume_is_idempotent_no_duplicate_pr_or_double_bump`, `tests/test_rollout.py::test_lock_that_misses_the_floor_fails_the_row`, `tests/test_rollout.py::test_release_tags_only_after_merge_and_floor_met`, `tests/test_rollout.py::test_refuses_claude_identity` and `tests/test_rollout.py::test_default_manifest_path_is_arbora`.",
      "definition_source": "specs/fleet-release/requirements.md",
      "definition_line": 13
    },
    {
      "id": "RM-MATERIALIZE",
      "kind": "spec",
      "parent": null,
      "source": "specs/proposal-materialization/status.json",
      "title": "RM-MATERIALIZE \u2014 Governed proposal to Git materialization",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "document": "specs/proposal-materialization/spec.md",
      "component": "Materialization",
      "code_refs": [
        {
          "declared_in": "specs/proposal-materialization/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/cli_commands/parser.py:781",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/cli_commands/parser.py#L781"
        },
        {
          "declared_in": "specs/proposal-materialization/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/development/serialization.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/development/serialization.py"
        },
        {
          "declared_in": "specs/proposal-materialization/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/materialization/service.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/materialization/service.py"
        },
        {
          "declared_in": "specs/proposal-materialization/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/materialization/service.py:156",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/materialization/service.py#L156"
        },
        {
          "declared_in": "specs/proposal-materialization/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_tools/registry.py:105",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_tools/registry.py#L105"
        },
        {
          "declared_in": "specs/proposal-materialization/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/merge_queue_runner.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/merge_queue_runner.py"
        },
        {
          "declared_in": "specs/proposal-materialization/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "scripts/check_complexity_staged.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/scripts/check_complexity_staged.py"
        },
        {
          "declared_in": "specs/proposal-materialization/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "spec.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/proposal-materialization/spec.md"
        },
        {
          "declared_in": "specs/proposal-materialization/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/merge_queue.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/merge_queue.py"
        },
        {
          "declared_in": "specs/proposal-materialization/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/safe_commit.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/safe_commit.py"
        },
        {
          "declared_in": "specs/proposal-materialization/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/worktree.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/worktree.py"
        },
        {
          "declared_in": "specs/proposal-materialization/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "requirements.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/proposal-materialization/requirements.md"
        }
      ],
      "relations": [],
      "plan_diagrams": [],
      "unparsed_references": []
    },
    {
      "id": "RM-MATERIALIZE-R001",
      "kind": "requirement",
      "parent": "RM-MATERIALIZE",
      "source": "specs/proposal-materialization/status.json",
      "title": "Repository-manager materializes an approved proposal into a commit",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-MATERIALIZE \u2014 Governed proposal to Git materialization",
      "definition": "**Repository-manager materializes an approved proposal into a commit.** Repository-manager alone creates an isolated working copy at the approved base, applies only the approved patch, runs the declared gates, stages the reviewed files explicitly, creates one commit with approved attribution, and submits the result to the existing merge queue rather than reporting it merged directly; it returns an immutable materialization receipt that must be re-ingested before the originating proposal can resolve. Subsystem: governed materialization. Entry: `MaterializationService.materialize` (`repository_manager/materialization/service.py:156`). Caller chain: a planned CLI verb `run_materialize_cli` (`repository_manager/cli_commands/materialization.py`, planned; dispatched beside `run_merge_queue_cli` at `repository_manager/cli_commands/parser.py:781`) and a planned MCP adapter `register_materialization_tools` (`repository_manager/mcp_tools/materialization.py`, planned; added as an entry of `MCP_TOOL_REGISTRY` at `repository_manager/mcp_tools/registry.py:105`) both call `MaterializationService.materialize`, which runs `_check_idempotent_replay` (:206), `_admit` (:220), `_create_worktree` (:237), `_apply_and_commit` (:264) and `_submit` (:292) in that order, then `_finish` (:361). No production module outside `repository_manager/materialization/` calls the service today; the two adapters are the delivery of this row. Shape: types are `ChangeProposal`, `ApprovalProof` and `MaterializationReceipt` in `repository_manager/materialization/models.py`; the three injected ports are `ApprovalAuthority`, `MaterializationReceiptStore` and `MergeQueuePort` in `repository_manager/materialization/ports.py`; the service composes the existing `WorktreeManager` (`repository_manager/worktree.py`), `safe_commit` (`repository_manager/safe_commit.py:613`) and `merge_queue.enqueue` through `GitMergeQueueAdapter` (`ports.py:110`) and adds no second Git-mutating function. Writes: one isolated worktree, one commit on branch `materialize/<proposal_id>`, one queue entry, one receipt through `MaterializationReceiptStore.put`. Depends on: `RM-MATERIALIZE-R002`, `RM-MATERIALIZE-R003`, `RM-MATERIALIZE-R004`, `RM-MATERIALIZE-R005`, `RM-MATERIALIZE-R006`. | Test: `tests/materialization/test_service.py::test_a_passing_gate_commits_with_exactly_the_reviewed_paths` and `tests/materialization/test_service.py::test_queue_acceptance_is_reported_as_queued_never_merged` cover the composed path with a fake Git, fake approval authority and fake queue. The adapter tests `tests/test_materialization_cli.py::test_materialize_verb_returns_the_receipt` and `tests/test_materialization_mcp.py::test_materialize_tool_returns_the_receipt` are planned.",
      "definition_source": "specs/proposal-materialization/requirements.md",
      "definition_line": 5
    },
    {
      "id": "RM-MATERIALIZE-R002",
      "kind": "requirement",
      "parent": "RM-MATERIALIZE",
      "source": "specs/proposal-materialization/status.json",
      "title": "Approval verification gates every Git materialization request",
      "delivery_state": "LANDED",
      "state": "landed",
      "done": false,
      "landed_in": [
        "c52511ddd596"
      ],
      "verified_by": [],
      "parent_title": "RM-MATERIALIZE \u2014 Governed proposal to Git materialization",
      "definition": "**Approval verification gates every Git materialization request.** Repository-manager accepts a versioned change proposal carrying its proposal ID, repository ID, exact base commit, approved path allowlist, patch digest, decision identity and expiry, and verifies caller authorization and a signed, verified approval before creating any isolated working copy. Entry: `MaterializationService.materialize` (`service.py:156`). Caller chain: `materialize` calls `_admit` (`service.py:220`) before `_create_worktree`; `_admit` calls the pure `check_binding` (`service.py:74`) for expiry, digest, repository, tenant and actor binding, then `ApprovalAuthority.verify` (`ports.py:77`) for signature authenticity and caller authorization. Shape: `ChangeProposal` (`models.py:113`) is a frozen strict model whose validators reject a malformed ID, a base that is not 40 hex characters, a patch digest that does not match `patch_text`, a patch over `MAX_PATCH_BYTES` and a non-aware `expires_at`; `ChangeProposal.digest` (`models.py:183`) is `canonical_digest` from `repository_manager/development/serialization.py:110`, which `ApprovalProof.proposal_digest` must equal. A binding failure containing `expired` maps to `expired_approval`, every other binding or authority failure to `unauthorized`, and both produce a `refused` receipt before any Git effect. Depends on: `RM-MATERIALIZE-R006`. | Test: `tests/materialization/test_service.py::test_expired_approval_refuses_without_any_worktree`, `tests/materialization/test_service.py::test_approval_bound_to_a_different_proposal_is_unauthorized`, `tests/materialization/test_service.py::test_approval_for_a_different_repository_is_unauthorized`, `tests/materialization/test_service.py::test_approval_from_the_wrong_actor_is_unauthorized`, `tests/materialization/test_service.py::test_approval_authority_rejection_is_unauthorized` and `tests/materialization/test_service.py::test_check_binding_is_pure_and_lists_every_structural_reason`.",
      "definition_source": "specs/proposal-materialization/requirements.md",
      "definition_line": 6
    },
    {
      "id": "RM-MATERIALIZE-R003",
      "kind": "requirement",
      "parent": "RM-MATERIALIZE",
      "source": "specs/proposal-materialization/status.json",
      "title": "Patch application is isolated and restricted to approved paths",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-MATERIALIZE \u2014 Governed proposal to Git materialization",
      "definition": "**Patch application is isolated and restricted to approved paths.** Repository-manager resolves the target repository from a portable registry, creates an isolated working copy at the approved base commit, and applies only the approved path allowlist, rejecting path traversal, symlink escapes, unexpected binary content, oversized patches and base drift. Entry: `MaterializationService.materialize` (`service.py:156`). Caller chain: `materialize` calls `_create_worktree` (`service.py:237`), which resolves the repository with `WorktreeManager.resolve_repo`, compares `proposal.base_ref` to `proposal.base_sha` through `_current_ref_sha` (:128) and raises `stale_base` on drift, then calls `WorktreeManager.add` at the approved base; `_apply_and_commit` (:264) calls `apply_patch` (`repository_manager/materialization/patch.py:116`), and a `PatchRejected` becomes `path_rejected` after `_abandon_worktree` (:308) removes the worktree. Shape: `apply_patch` runs `changed_paths_in_patch` (`patch.py:77`) and `_reject_unsafe_paths` (:57) and `_reject_outside_allowlist` (:66) on the header paths, rejects any symlink-mode line with `_SYMLINK_MODE_RE`, then `git apply --check`, re-checks the paths `git apply --numstat` reports through `_numstat_paths` (:93), applies, and re-checks the result with `_reject_symlink_targets` (:109); the size bound is `MAX_PATCH_BYTES` (2 MiB) in `models.py`, enforced when the proposal is built, before any worktree exists. The canonical checkout is read through `run_git` (`patch.py:37`) and never written. Depends on: `RM-MATERIALIZE-R002`. | Test: `tests/materialization/test_service.py::test_valid_patch_touches_only_the_approved_path`, `tests/materialization/test_service.py::test_patch_touching_an_unapproved_path_is_rejected`, `tests/materialization/test_service.py::test_patch_header_with_traversal_is_rejected_statically`, `tests/materialization/test_service.py::test_patch_declaring_a_new_symlink_is_rejected`, `tests/materialization/test_service.py::test_binary_patch_content_is_rejected`, `tests/materialization/test_service.py::test_oversized_patch_is_rejected_before_any_git_mutation_can_start`, `tests/materialization/test_service.py::test_stale_base_is_rejected_before_any_worktree_is_created` and `tests/materialization/test_service.py::test_unknown_repository_is_rejected_as_stale_base`.",
      "definition_source": "specs/proposal-materialization/requirements.md",
      "definition_line": 7
    },
    {
      "id": "RM-MATERIALIZE-R004",
      "kind": "requirement",
      "parent": "RM-MATERIALIZE",
      "source": "specs/proposal-materialization/status.json",
      "title": "Validation gates and explicit staging precede every commit",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-MATERIALIZE \u2014 Governed proposal to Git materialization",
      "definition": "**Validation gates and explicit staging precede every commit.** Repository-manager runs the declared local validation checks against the resulting tree, stages an explicit path list, and creates one commit carrying the approved attribution and exact tree identity. Entry: `MaterializationService.materialize` (`service.py:156`). Caller chain: `materialize` calls `_apply_and_commit` (`service.py:264`), which calls `safe_commit` (`repository_manager/safe_commit.py:613`) with `paths=list(proposal.approved_paths)` and the service's `gate`; a result without `ok` becomes `gate_failed` after `_abandon_worktree`, and `_tree_sha` (:133) records `HEAD^{tree}` of the worktree for the receipt. Shape: the commit message is `materialize <proposal_id> (approved by <decision_identity>)` (`service.py:276`); the gate is the constructor argument `gate` (a command or a callable taking the worktree path), so the declared profile of the proposal (`ChangeProposal.validation_profile`) is recorded on the receipt as `gate_profile` and the caller chooses the gate when it builds the service. Binding `validation_profile` to a named gate set is not built; it needs the gate-profile vocabulary of `repository_manager/validation_policy.py` and is an owner decision. Depends on: `RM-MATERIALIZE-R003`. | Test: `tests/materialization/test_service.py::test_a_failing_gate_blocks_both_commit_and_queue` and `tests/materialization/test_service.py::test_a_passing_gate_commits_with_exactly_the_reviewed_paths`. The profile-to-gate binding test `tests/materialization/test_service.py::test_validation_profile_selects_the_declared_gate` is planned.",
      "definition_source": "specs/proposal-materialization/requirements.md",
      "definition_line": 8
    },
    {
      "id": "RM-MATERIALIZE-R005",
      "kind": "requirement",
      "parent": "RM-MATERIALIZE",
      "source": "specs/proposal-materialization/status.json",
      "title": "Merge queue submission never claims landing before verification",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-MATERIALIZE \u2014 Governed proposal to Git materialization",
      "definition": "**Merge queue submission never claims landing before verification.** Repository-manager submits the resulting commit to the existing merge queue and reports it as submitted, never as merged, until the queue independently verifies the base, gate results and merge outcome. Entry: `MaterializationService.materialize` (`service.py:156`) and `MaterializationService.reconcile` (`service.py:186`). Caller chain: `materialize` calls `_submit` (`service.py:292`), which calls `MergeQueuePort.submit`; the production adapter `GitMergeQueueAdapter.submit` (`ports.py:119`) calls `merge_queue.enqueue` and never drains the queue. A refusal by the queue becomes `queue_conflict`; an accepted submission yields a `queued` receipt. `reconcile` calls `_reconcile_queued` (`service.py:398`), which calls `GitMergeQueueAdapter.status` (`ports.py:135`); only `merge_queue.LANDED` moves the receipt to `merged`, `merge_queue.REJECTED` moves it to `refused` with `queue_conflict`, and any other state leaves it `queued`. Shape: no code path outside `reconcile` writes `merged`; `reconcile` performs no Git mutation and re-reads the report that `merge-queue-runner.timer` fills. Depends on: `RM-MATERIALIZE-R004`. | Test: `tests/materialization/test_service.py::test_queue_acceptance_is_reported_as_queued_never_merged`, `tests/materialization/test_service.py::test_queue_conflict_is_reported_as_refused_not_success`, `tests/materialization/test_service.py::test_reconcile_promotes_a_landed_candidate_to_merged` and `tests/materialization/test_service.py::test_reconcile_reports_a_rejected_candidate_as_refused`.",
      "definition_source": "specs/proposal-materialization/requirements.md",
      "definition_line": 9
    },
    {
      "id": "RM-MATERIALIZE-R006",
      "kind": "requirement",
      "parent": "RM-MATERIALIZE",
      "source": "specs/proposal-materialization/status.json",
      "title": "An immutable receipt binds every materialization outcome",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-MATERIALIZE \u2014 Governed proposal to Git materialization",
      "definition": "**An immutable receipt binds every materialization outcome.** Repository-manager returns an immutable materialization receipt bound to the proposal, approval, base commit, resulting commit and tree, gate profile and results, merge queue result and an idempotency key, and reconciles uncertain delivery before any retry. Entry: `MaterializationService.materialize` (`service.py:156`). Caller chain: every phase outcome ends in `_finish` (`service.py:361`) or `_pending_receipt` (:378), both calling `_build_receipt` (:328), which builds a `MaterializationReceipt` and stores it through `_persist` (:388) and `MaterializationReceiptStore.put`; a repeated call enters `_check_idempotent_replay` (:206), which returns the stored receipt for the same `proposal_digest` and refuses a different digest under the same key with `unauthorized`. Shape: `MaterializationReceipt` (`models.py:237`) is frozen and strict, carries digests and identities but no patch bytes and no filesystem path, and its validator `_validate_terminal_shape` (`models.py:281`) allows an error code only on `refused` or on `pending` with `uncertain_delivery`; `MaterializationReceipt.digest` uses `canonical_digest`. The gate result digest, the queue result record, the monotonic transition event and the receipt signature of the target design are not fields of the receipt today; adding them is a schema change and an owner decision (see the owner decisions in the pull request). The states `applied`, `validated` and `committed` exist in `MaterializationState` (`models.py:89`) and no code path emits them. Depends on: `RM-MATERIALIZE-R002`, `RM-MATERIALIZE-R005`. | Test: `tests/materialization/test_service.py::test_a_replayed_request_returns_the_same_receipt_without_a_second_commit`, `tests/materialization/test_service.py::test_an_altered_replay_under_the_same_key_is_rejected` and `tests/materialization/test_service.py::test_materialization_receipt_contract_round_trips_through_canonical_serialization`. The receipt-signature and gate-result-digest tests `tests/materialization/test_receipt_contract.py::test_receipt_carries_gate_result_digest_and_signature` are planned.",
      "definition_source": "specs/proposal-materialization/requirements.md",
      "definition_line": 10
    },
    {
      "id": "RM-MATERIALIZE-R007",
      "kind": "requirement",
      "parent": "RM-MATERIALIZE",
      "source": "specs/proposal-materialization/status.json",
      "title": "No caller has a direct Git fallback when the service is unavailable",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-MATERIALIZE \u2014 Governed proposal to Git materialization",
      "definition": "**No caller has a direct Git fallback when the service is unavailable.** No caller may bypass repository-manager with a direct Git fallback; when repository-manager, the authorization check, or receipt delivery is unavailable, the request remains pending rather than completing through another path. Entry: `MaterializationService.materialize` (`service.py:156`). Caller chain: `materialize` catches `_UNAVAILABLE_ERRORS` (`service.py:66`: `ApprovalAuthorityUnavailable`, `ReceiptStoreUnavailable`, `MergeQueueUnavailable`, `RepositoryManagerUnavailable`) around all phases and returns `_pending_receipt` (:378), a `pending` receipt with `uncertain_delivery`; `_persist` (:388) logs and still returns the receipt when the store is down; `reconcile` (:186) re-raises `ReceiptStoreUnavailable` and marks a queued receipt pending again when the queue status is unavailable. Shape: the service is the only function in the package that creates a worktree, applies a patch or commits for a proposal; `repository_manager/materialization/__init__.py` exports no other Git-mutating function. Removing direct Git routes from callers is the migration step of the planned adapters of `RM-MATERIALIZE-R001`. Depends on: `RM-MATERIALIZE-R001`. | Test: `tests/materialization/test_service.py::test_unavailable_approval_authority_leaves_the_request_pending`, `tests/materialization/test_service.py::test_unavailable_receipt_store_leaves_the_request_pending` and `tests/materialization/test_service.py::test_unavailable_merge_queue_leaves_a_committed_candidate_pending`.",
      "definition_source": "specs/proposal-materialization/requirements.md",
      "definition_line": 11
    },
    {
      "id": "RM-SCM",
      "kind": "spec",
      "parent": null,
      "source": "specs/source-changesets/status.json",
      "title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "document": "specs/source-changesets/spec.md",
      "component": "Source control",
      "code_refs": [
        {
          "declared_in": "specs/source-changesets/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/development/serialization.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/development/serialization.py"
        },
        {
          "declared_in": "specs/source-changesets/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/materialization/models.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/materialization/models.py"
        },
        {
          "declared_in": "specs/source-changesets/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_server.py:973",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_server.py#L973"
        },
        {
          "declared_in": "specs/source-changesets/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_tools/merge_queue.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_tools/merge_queue.py"
        },
        {
          "declared_in": "specs/source-changesets/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_tools/registry.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_tools/registry.py"
        },
        {
          "declared_in": "specs/source-changesets/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/mcp_tools/registry.py:105",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/mcp_tools/registry.py#L105"
        },
        {
          "declared_in": "specs/source-changesets/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/repository_manager.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/repository_manager.py"
        },
        {
          "declared_in": "specs/source-changesets/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "requirements.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/source-changesets/requirements.md"
        },
        {
          "declared_in": "specs/source-changesets/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "scripts/check_complexity_staged.py",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/scripts/check_complexity_staged.py"
        },
        {
          "declared_in": "specs/source-changesets/plan.md",
          "evidence": "file exists; coverage not verified",
          "label": "spec.md",
          "repository": "Knuckles-Team/repository-manager",
          "role": "documentation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/specs/source-changesets/spec.md"
        },
        {
          "declared_in": "specs/source-changesets/spec.md",
          "evidence": "file exists; coverage not verified",
          "label": "repository_manager/repository_manager.py:2462",
          "repository": "Knuckles-Team/repository-manager",
          "role": "implementation",
          "url": "https://github.com/Knuckles-Team/repository-manager/blob/5d12e2fa908616f1afcc622b1b617d03224fd56a/repository_manager/repository_manager.py#L2462"
        }
      ],
      "relations": [],
      "plan_diagrams": [],
      "unparsed_references": []
    },
    {
      "id": "RM-SCM-R001",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Import git history into engine changesets (rollup)",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Import git history into engine changesets (rollup).** The tool must import the full history of one repository into engine changesets. Each commit becomes one changeset with the same tree hash, per `MEDULLA-SCM-R010`. Children `.1` to `.6` deliver it. Production call site: `rm_source_import` registered in `MCP_TOOL_REGISTRY` (`repository_manager/mcp_tools/registry.py:105`). | Satisfied only when its child rows are verified.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 5
    },
    {
      "id": "RM-SCM-R001.1",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Model",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Model.** `ImportPlan{repo, remote, refs, first_commit, last_commit}` and `ImportReceipt{repo, commits, changesets, tree_hash_matches}` are frozen pydantic models, as in `repository_manager/materialization/models.py:113`. Caller chain: `rm_source_import` (planned, `repository_manager/mcp_tools/source.py`) parses its arguments into `ImportPlan`, and `import_history` (planned, `repository_manager/source_changesets/importer.py`) returns `ImportReceipt`. Shape: both types live in `repository_manager/source_changesets/models.py` (planned) with `extra=\"forbid\"` and `frozen=True`, and the canonical digest of a receipt reuses `canonical_digest` (`repository_manager/development/serialization.py:110`). The package `repository_manager/source_changesets/` does not exist yet. | Test: `tests/source_changesets/test_models.py::test_import_models_round_trip` (planned). It round-trips both models.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 6
    },
    {
      "id": "RM-SCM-R001.2",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Behavior",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Behavior.** The import walks commits in topological order and submits one changeset per commit through the SDK source client of `SCION-SCM-R001`. A re-run imports only new commits. Each changeset keeps the author, the message and the trailers. Caller chain: `import_history` (planned, `repository_manager/source_changesets/importer.py`) lists commits with `git rev-list --topo-order --reverse` through `Git.git_action` (`repository_manager/repository_manager.py:2462`), reads each commit's tree id, and calls `SourceClient` (`scion_sdk/source/client.py:84` in the SDK) `.commit` (:160) with the commit's message, which keeps the trailers. Shape: the already-imported set comes from the SDK client's `history` read (:108) so no second store exists; the engine side of the same mapping is `MEDULLA-SCM-R010`, whose served `ImportGitHistory` stream method is the alternative path and the choice between the two is an owner decision. Depends on: `RM-SCM-R001.1`. | Test: `tests/source_changesets/test_import.py::test_import_is_incremental` (planned). It imports a 50-commit fixture twice and asserts 50 changesets, then 0.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 7
    },
    {
      "id": "RM-SCM-R001.3",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Wiring",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Wiring.** The served tool `rm_source_import` calls the import. arbora serves it as a connector tool behind admission (`ARBORA-OPS-R848`). Caller chain: arbora MCP calls the fleet connector `repository-manager`, whose server is built at `repository_manager/mcp_server.py:973`; `register_source_tools` (planned, `repository_manager/mcp_tools/source.py`) is an entry of `MCP_TOOL_REGISTRY` (`repository_manager/mcp_tools/registry.py:105`), reached through `register_split_action_tools` (`repository_manager/mcp_server.py:994`), and registers `rm_source_import`, which calls `import_history`. Shape: the registrar follows `register_merge_queue_tools` (`repository_manager/mcp_tools/merge_queue.py:16`): one `@mcp.tool` with typed arguments, the engine client of the caller passed to the SDK client, no engine call of its own. Depends on: `RM-SCM-R001.2`. | Test: `tests/source_changesets/test_import_served.py::test_rm_source_import_returns_receipt` (planned). It calls `rm_source_import` through the MCP client and reads the receipt.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 8
    },
    {
      "id": "RM-SCM-R001.4",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Refusal",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Refusal.** A tree hash mismatch stops the import with `IMPORT_TREE_MISMATCH` and keeps prior changesets. A shallow clone refuses with `IMPORT_SHALLOW_HISTORY`. Caller chain: `import_history` (planned, `repository_manager/source_changesets/importer.py`) checks `git rev-parse --is-shallow-repository` before the walk and compares the returned changeset tree id with the commit tree id after each submission. Shape: both codes are members of one `ImportRefusal` string enum in `repository_manager/source_changesets/models.py` (planned), raised as a typed refusal and rendered by the tool; the check reuses the shallow detection idea of `_reject_divergent_state` (`repository_manager/history_identity/discovery.py:124`). Writes: none after the refusal. Depends on: `RM-SCM-R001.2`. | Test: `tests/source_changesets/test_import.py::test_refusals_leave_no_partial_changeset` (planned). It asserts each code and no partial changeset.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 9
    },
    {
      "id": "RM-SCM-R001.5",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Evidence",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Evidence.** The receipt names the repository, the commit range, the changeset count and the tree hash result for each commit. Caller chain: `import_history` (planned) builds `ImportReceipt` from the per-commit results and `rm_source_import` returns it. Shape: the fields are those of `ImportReceipt` in `repository_manager/source_changesets/models.py` (planned); `tree_hash_matches` holds one boolean per commit in walk order. Depends on: `RM-SCM-R001.1`. | Test: `tests/source_changesets/test_import.py::test_receipt_fields` (planned). It reads the receipt fields.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 10
    },
    {
      "id": "RM-SCM-R001.6",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Hot-path proof",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Hot-path proof.** The entry point is the served `rm_source_import`. The test imports a 1,000-commit fixture and must finish under 120 s and 512 MiB. Caller chain: the MCP client calls `rm_source_import` (`RM-SCM-R001.3`), then `import_history`, then the SDK client against a recorded engine. Shape: the fixture is built with temporary Git repositories as `tests/history_identity_git_fixtures.py` does. Depends on: `RM-SCM-R001.3`. | Test: `tests/source_changesets/test_import_served.py::test_import_full_history` (planned). It asserts the time and memory bounds.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 11
    },
    {
      "id": "RM-SCM-R002",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Mirror sync to the public git hosts (rollup)",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Mirror sync to the public git hosts (rollup).** The tool must export each landed changeset to the public and internal git mirrors and pull a commit made on a mirror back as a changeset. Children `.1` to `.6` deliver it. Production call site: `rm_source_land` (`RM-SCM-R003.1`) calls `mirror_changeset` after a landed receipt. | Satisfied only when its child rows are verified.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 12
    },
    {
      "id": "RM-SCM-R002.1",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Model",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Model.** `MirrorTarget{repo, host, remote, branch}` and `MirrorReceipt{changeset_id, commit_sha, tree_hash, host}` are frozen pydantic models. Caller chain: `mirror_changeset` (planned, `repository_manager/source_changesets/mirror.py`) takes `MirrorTarget` values and returns one `MirrorReceipt` per host. Shape: both types live in `repository_manager/source_changesets/models.py` (planned), shaped like the models of `RM-SCM-R001.1`. Depends on: `RM-SCM-R001.1`. | Test: `tests/source_changesets/test_models.py::test_mirror_models_round_trip` (planned). It round-trips both models.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 13
    },
    {
      "id": "RM-SCM-R002.2",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Behavior",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Behavior.** After `source.land`, the sync pushes the exported commit to each mirror within 60 s. A commit made on a mirror imports as one changeset through `RM-SCM-R001`. The commit tree hash equals the changeset tree hash. Caller chain: `rm_source_land` (planned, `repository_manager/mcp_tools/source.py`) calls `SourceClient` (`scion_sdk/source/client.py:84` in the SDK) `.land` (:163) and, on a landed receipt, `mirror_changeset` (planned, `repository_manager/source_changesets/mirror.py`), which fetches the commit from the git bridge (`ARBORA-OPS-R851`) and runs `git push` without `--force` to each target through `Git.git_action` (`repository_manager/repository_manager.py:2462`); the pull-back runs `import_history` on the mirror's new commits. Shape: a landing made through another client than `rm_source_land` is not seen by this trigger; how such landings reach the sync (event or poll) is an owner decision. Depends on: `RM-SCM-R001.2`, `RM-SCM-R002.1`. | Test: `tests/source_changesets/test_mirror.py::test_land_pushes_and_mirror_commit_imports_back` (planned). It lands one changeset and pulls one mirror commit back.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 14
    },
    {
      "id": "RM-SCM-R002.3",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Wiring",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Wiring.** The sync reads landed changesets through the SDK source client and uses the git bridge export of `ARBORA-OPS-R851` for the push. Caller chain: `mirror_changeset` (planned) calls `SourceClient` (`scion_sdk/source/client.py:84` in the SDK) `.history` (:108) and fetches over the bridge route `GET /git/{repository}/info/refs` and `POST /git/{repository}/git-upload-pack` that `ARBORA-OPS-R851` defines. Shape: the module reuses `Git.git_action` for every Git process and adds no HTTP client of its own beyond the bridge fetch through Git itself. Depends on: `RM-SCM-R002.2`. | Test: `tests/source_changesets/test_mirror_sync_served.py::test_land_through_arbora_observes_mirror_push` (planned). It lands through arbora and observes the mirror push.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 15
    },
    {
      "id": "RM-SCM-R002.4",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Refusal",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Refusal.** A mirror that holds a diverged commit stops the sync with `MIRROR_DIVERGED`. The sync never force-pushes. Caller chain: `mirror_changeset` (planned) runs `git ls-remote` for the target branch and refuses when the remote tip is not an ancestor of the commit to push. Shape: `MIRROR_DIVERGED` is a member of a `MirrorRefusal` string enum in `repository_manager/source_changesets/models.py` (planned); the push argument list never contains `--force` or `--force-with-lease`. Writes: none after the refusal. Depends on: `RM-SCM-R002.2`. | Test: `tests/source_changesets/test_mirror.py::test_diverged_mirror_refuses_without_push` (planned). It diverges a fixture mirror and asserts the code and no push.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 16
    },
    {
      "id": "RM-SCM-R002.5",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Evidence",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Evidence.** Each push writes one receipt per host with the changeset id, the commit SHA and the tree hash. Caller chain: `mirror_changeset` (planned) returns the `MirrorReceipt` list to `rm_source_land`, which returns it to the caller. Shape: fields as in `RM-SCM-R002.1`. Depends on: `RM-SCM-R002.1`. | Test: `tests/source_changesets/test_mirror.py::test_receipts_per_host` (planned). It reads the receipts.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 17
    },
    {
      "id": "RM-SCM-R002.6",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Hot-path proof",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Hot-path proof.** The entry point is a served `source.land`. The test observes the mirror commit within 60 s with an equal tree hash. Caller chain: the MCP client calls `rm_source_land` (`RM-SCM-R003.1`), then `mirror_changeset`, then a local bare repository standing for the mirror. Shape: the mirror is a temporary bare repository. Depends on: `RM-SCM-R002.3`. | Test: `tests/source_changesets/test_mirror_sync_served.py::test_land_then_mirror` (planned). It asserts the 60 s bound and the equal tree hash.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 18
    },
    {
      "id": "RM-SCM-R003",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Served source development tools (rollup)",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Served source development tools (rollup).** The connector must serve one tool per `source.*` operation: tree, blob, diff, history, blame, commit, land and revert. Each tool composes the SDK source client. Children `.1` to `.3` deliver it. Production call site: `register_source_tools` in `MCP_TOOL_REGISTRY` (`repository_manager/mcp_tools/registry.py:105`). | Satisfied only when its child rows are verified.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 19
    },
    {
      "id": "RM-SCM-R003.1",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Tools",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Tools.** `rm_source_tree`, `rm_source_blob`, `rm_source_diff`, `rm_source_history`, `rm_source_blame`, `rm_source_commit`, `rm_source_land` and `rm_source_revert` are registered. Reads carry the read-only hint; writes carry the destructive hint. Caller chain: arbora MCP calls the connector (`repository_manager/mcp_server.py:973`), whose `MCP_TOOL_REGISTRY` entry `register_source_tools` (planned, `repository_manager/mcp_tools/source.py`) registers the eight tools. Shape: each tool is a thin adapter over the matching method of `SourceClient` (`scion_sdk/source/client.py:84` in the SDK): `tree` (:102), `diff` (:105), `history` (:108), `blame` (:111), `blob` (:114), `commit` (:160), `land` (:163), `revert` (:166); the registrar follows `register_merge_queue_tools` (`repository_manager/mcp_tools/merge_queue.py:16`), and the tool-schema fingerprints in `repository_manager/connectors/tool_schema_fingerprints.json` gain the eight entries. Depends on: `RM-SCM-R001.3`. | Test: `tests/source_changesets/test_dev_tools.py::test_eight_tools_and_their_hints` (planned). It lists the eight tools and their hints.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 20
    },
    {
      "id": "RM-SCM-R003.2",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Refusal",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Refusal.** Each tool passes the typed refusal of `SCION-SCM-R001.4` through unchanged. A `conflict` refusal names the conflicting paths. Caller chain: the tool adapters of `RM-SCM-R003.1` catch the SDK refusal type and return it as the tool result. Shape: the closed reason codes are those of `SCION-SCM-R001.4` (`unauthorized`, `not_found`, `conflict`, `path_denied`, `oversized`, `deadline_exceeded`, `transport_unavailable`); the adapters map no code to another. Depends on: `RM-SCM-R003.1`. | Test: `tests/source_changesets/test_dev_tools.py::test_conflict_refusal_passes_through_with_paths` (planned). It asserts a passed-through `conflict` with paths.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 21
    },
    {
      "id": "RM-SCM-R003.3",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Hot-path proof",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Hot-path proof.** The entry point is arbora MCP. An agent edits one file through `rm_source_commit` and lands it through `rm_source_land`, per `MERISTEM-SCM-R001`. Caller chain: the MCP client calls `rm_source_commit`, then `rm_source_land`. Shape: one recorded engine; the assertion reads the landed file back through `rm_source_blob`. Depends on: `RM-SCM-R003.1`. | Test: `tests/source_changesets/test_dev_tools_served.py::test_commit_and_land_through_arbora` (planned). It commits and lands one file and reads it back.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 22
    },
    {
      "id": "RM-SCM-R004",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "One migration wave step for one repository (rollup)",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**One migration wave step for one repository (rollup).** The connector must move one repository to engine-primary for a wave of `PIPE-GATES-R006` and back to git-primary. Children `.1` to `.3` deliver it. Production call site: a planned `rm_source_wave_step` tool in `register_source_tools`. | Satisfied only when its child rows are verified.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 23
    },
    {
      "id": "RM-SCM-R004.1",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Behavior",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Behavior.** The step imports history (`RM-SCM-R001`), starts the mirror sync (`RM-SCM-R002`) and records the repository as engine-primary. The reverse step stops intake and records git-primary. Caller chain: `rm_source_wave_step` (planned, `repository_manager/mcp_tools/source.py`) calls `wave_step` (planned, `repository_manager/source_changesets/wave.py`), which calls `import_history` and then enables `mirror_changeset` for the repository. Shape: the primary side is recorded in the wave receipt only; the store that holds it across restarts is an owner decision (no state file exists in this package today). Depends on: `RM-SCM-R001.2`, `RM-SCM-R002.2`. | Test: `tests/source_changesets/test_wave_step.py::test_step_and_reverse_on_a_fixture_repository` (planned). It runs the step and the reverse step.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 24
    },
    {
      "id": "RM-SCM-R004.2",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Refusal",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Refusal.** The step refuses with `WAVE_ENTRY_UNMET` when the wave entry criteria of `PIPE-GATES-R006` do not hold. Caller chain: `wave_step` (planned) evaluates the criteria before any import. Shape: how the criteria reach this connector (a passed argument or a read of the pipelines wave definition) is an owner decision; the refusal is a member of a `WaveRefusal` string enum in `repository_manager/source_changesets/models.py` (planned). Writes: none after the refusal. Depends on: `RM-SCM-R004.1`. | Test: `tests/source_changesets/test_wave_step.py::test_unmet_entry_criterion_refuses` (planned). It asserts the refusal for an unmet criterion.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 25
    },
    {
      "id": "RM-SCM-R004.3",
      "kind": "requirement",
      "parent": "RM-SCM",
      "source": "specs/source-changesets/status.json",
      "title": "Evidence",
      "delivery_state": "SPECIFIED",
      "state": "specified",
      "done": false,
      "landed_in": [],
      "verified_by": [],
      "parent_title": "RM-SCM \u2014 Git import, export and mirror sync for engine changesets",
      "definition": "**Evidence.** The step writes a receipt with the wave, the repository, the primary side and the import receipt digest. Caller chain: `wave_step` (planned) returns the receipt to `rm_source_wave_step`. Shape: the receipt is a frozen model in `repository_manager/source_changesets/models.py` (planned) whose digest uses `canonical_digest` (`repository_manager/development/serialization.py:110`). Depends on: `RM-SCM-R004.1`. | Test: `tests/source_changesets/test_wave_step.py::test_step_and_reverse_receipts` (planned). It asserts both receipts.",
      "definition_source": "specs/source-changesets/requirements.md",
      "definition_line": 26
    }
  ],
  "github": {
    "issues": {
      "available": true,
      "items": []
    },
    "pull_requests": {
      "available": true,
      "items": []
    }
  },
  "spec_edges": [
    [
      "RM-CONNECTOR",
      "references",
      "RM-GOVERNANCE"
    ],
    [
      "RM-GOVERNANCE",
      "references",
      "RM-CONNECTOR"
    ]
  ]
}
