<!-- Written per the the-loop:writing skill. -->

Tasks: split /the-loop:init into /init, /init-cli and /init-gateway

The tasks-breakdown node was skipped at phase-selection, so this list is design.md § Implementation order turned into checkboxes. The implementation node's exit checks those boxes. The design (locked at design-approval) stays the source; testing-plan.md was skipped as well, so each _Test:_ names a check from design § Testing strategy.

Task list

• [x] 1. Tests first (red)
  • New cli/tests/test_init_commands.py with the three scenarios from design § Testing strategy:
    • every command is listed in the command reference and the skill;
    • /init sets up no daemon;
    • each init command offers both modes.
  • In cli/tests/test_migrations.py, the two Jira assertions expect /the-loop:init-cli.
  • Depends on: none
  • Requirements: R1.2, R1.3, R2.1, R3.1, R4.1, R5.1
  • Test: uv run pytest cli/tests/test_init_commands.py cli/tests/test_migrations.py. Red before task 2.
• [x] 2. The three command files
  • Rewrite commands/init.md (repository only, hand-off paragraph).
  • Add commands/init-cli.md and commands/init-gateway.md, with each of today's steps carried to the owner design's mapping table names.
  • Depends on: 1
  • Requirements: R1, R2, R3, R4
  • Test: the test_init_commands.py scenarios turn green.
• [x] 3. Onboarding reference and skill
  • skills/the-loop/reference/onboarding.md: reorganise by config file and command.
  • SKILL.md: § Commands and the reference-list line.
  • Depends on: 2
  • Requirements: R5.1
  • Test: the "listed in the skill" scenario; markdownlint.
• [x] 4. Strings outside the prose
  • cli/the_loop/migrations.py: the two Jira messages.
  • .the-loop/manifest.yaml: the two comments.
  • Both copies of cli-config.schema.json: the x-onboarding.description string only.
  • Depends on: 1
  • Requirements: R5.2; design § Trade-offs
  • Test: test_migrations.py turns green; test_onboarding_schema.py, test_manifest_schemas.py and the schema parity checks stay green.
• [x] 5. User docs, capability doc, decision
  • The docs the design's Other edits table lists: guides, the command reference, the config docs, the operating-model index, upgrade-the-loop.md.
  • docs/capabilities/distribution.md with an issue-514 history row.
  • docs/decisions/decision-149.md plus its index row.
  • Depends on: 2, 3
  • Requirements: R5.1, R5.3, R5.4
  • Test: the "listed in the command reference" scenario; markdownlint; the docs-parity tests.
• [x] 6. Checkpoint: the full suite
  • Run pre-commit: ruff, pyright, pytest, markdownlint, config validation.
  • Depends on: 1–5
  • Requirements: all
  • Test: uv run pre-commit run --all-files green.

Dependency graph (DAG)

1 → 2 → 3 → 5 → 6, and 1 → 4 → 6.

Checkpoints

• After task 2: the new test file is green.
• After task 4: the migrations and schema tests are green.
• Task 6: the full suite.
• Verification: the dry-run walkthroughs of design § Testing strategy, committed as evidence/dry-runs.md.