Commit fdf3749e authored by Vacaliuc, Bogdan's avatar Vacaliuc, Bogdan
Browse files

prompts/initialization: v2.1 — Developer triage cleanup, /effort medium, §2.5 split 



Developer-prompt.md (v2.1 ref cleanup):
- Add step 6: git push --delete {remote} triage/{slug}[-v{N}]
  after merging into the analysis branch (with explicit-exit check
  so a failed delete doesn't lose progress); also delete the local
  tracking branch.
- Renumber the existing /clear + ScheduleWakeup step from 6 → 7.
- Extend the in-prompt allowlist to include the triage --delete
  per orchestration.md §8 v2.1.

Initialization-prompt.md (v2.1 fallback role expanded):
- /effort default → /effort medium (default is not a valid CLI
  option). Add a one-line CLI note.
- §0 banner: explicit "v2.1 canonical path for write-capability
  verification (initialization.md §2.5)" — Administrator is
  read-only on the repository in v2.1, so this v1 fallback session
  is the canonical agent-driven path for the §2.5 push test.
  Reorder the use-cases list so write-capability verification is #1.

initialization.md §0 banner (v2.1 split):
- Document the v2.1 split: read-only checks (§1, §2.1-§2.4, §3-§11)
  → Administrator phase 1; §2.5 write-capability verification →
  user-manual or v1 Initialization-prompt.md fallback.
- Cross-reference orchestration.md §3 / §8 v2.1 contract.

Co-Authored-By: default avatarClaude Opus 4.7 (1M context) <noreply@anthropic.com>
parent 98ec73e7

plan/Developer-prompt.md

+11 −1
Original line number Diff line number Diff line
@@ -154,7 +154,16 @@ Every TD seconds: 
         plans/{slug}-learning.md

       on the analysis branch. Structure: rule → Why → How to apply.

       Commit it. Push the analysis branch to {remote}.

    6. Update agent-state-Developer.json with lastAction,

    6. Delete the triage branch from {remote} (v2.1 cleanup —

       minimize ref detritus per orchestration.md §8 end-state

       contract):

         if git push --delete {remote} triage/{slug}[-v{N}]; then : ; else

           # If the delete fails (already gone, network blip),

           # don't lose progress. Log it; the

           # cleanup-dry-run-refs.sh helper picks up stragglers.

         fi

         git branch -D triage/{slug}[-v{N}] 2>/dev/null || true

    7. Update agent-state-Developer.json with lastAction,

       lastActionTs. Context lifecycle: /clear, then ScheduleWakeup

       (prompt="/poll", delaySeconds=5*TD) and return to the poll

       loop.
@@ -164,6 +173,7 @@ without asking, per §8 of the meta-plan: 
  feature/{slug}

  qa/{slug} tag

  analysis/new_workflow-repairs-2026-04

  --delete on triage/{slug}[-v{N}] (post-merge cleanup, v2.1)

Any other push still requires explicit user approval.



For dry-run mode (DRY_RUN=1 with {dry-run-prefix}, {dry-run-remote},

plan/Initialization-prompt.md

+23 −10
Original line number Diff line number Diff line
@@ -12,17 +12,27 @@ 
>

> **When to use this file (not Administrator-prompt.md):**

>

> 1. You are constrained to three concurrent sessions total and

> 1. **Write-capability verification (v2.1 canonical path).**

>    Administrator is read-only on the repository in v2.1, so it

>    cannot perform initialization.md §2.5 (push/delete a scratch

>    `init-check-*` ref to verify the credential grants write

>    capability). This Initialization-prompt.md session retains the

>    `init-check-*` push allowlist and is the canonical

>    agent-driven path for §2.5. Run it once after each credential

>    rotation; afterwards Administrator phase 1 just asks the user

>    to confirm "verified" before entering phase 2.

> 2. You are constrained to three concurrent sessions total and

>    cannot afford a fourth session for the Administrator.

> 2. You want to re-run the Initialization checklist alone (after a

>    credential rotation, machine move, or `{base-branch}` switch)

>    without disturbing the Administrator's in-flight phase 2 loop.

> 3. You are deliberately walking the v1 deployment path documented

> 3. You want to re-run the full initialization checklist alone

>    (after a machine move or `{base-branch}` switch) without

>    disturbing the Administrator's in-flight phase 2 loop.

> 4. You are deliberately walking the v1 deployment path documented

>    in `plan/orchestration.md` §13.1 "Fallback (v1 standalone

>    Initialization)".

>

> **For all other deployments,** start the Administrator agent first

> per `plan/orchestration.md` §13.1.

> **For routine startup,** start the Administrator agent first per

> `plan/orchestration.md` §13.1; use this v1 fallback session only

> for §2.5 write verification or the other cases above.



This file (when used) is the prompt for a one-shot Initialization

session that walks the [initialization.md](initialization.md)
@@ -35,12 +45,15 @@ Developer, Integrator) per the v1 deployment path. 
Before pasting this prompt, set the session's model and effort:

```

  /model claude-sonnet-4-6

  /effort default

  /effort medium

```



(Robust default per `plan/orchestration.md` §9.5 — procedural

verification with diagnostic suggestions on failure. Haiku 4.5 is a

viable cost-efficient alternative if the environment is stable.)

verification with diagnostic suggestions on failure. Haiku 4.5 /

`medium` is a viable cost-efficient alternative if the environment

is stable. The CLI accepts `low | medium | high | xhigh | max | auto`

for `/effort`; the v1 docs used `default` colloquially — that is

*not* a valid CLI option.)



If you are conducting a "dry-run" verification test, add the

following to the end of the prompt below before pasting it to the

plan/initialization.md

+22 −15
Original line number Diff line number Diff line 
# {tasking-branch} — Initialization agent checklist



## 0. v2 deprecation banner

## 0. v2 deprecation banner (updated for v2.1)



> **In v2 the standalone Initialization agent is deprecated.** Its

> work is now performed by **phase 1 of the Administrator agent**;

> see [Administrator-prompt.md](Administrator-prompt.md) and

> **In v2 the standalone Initialization session is deprecated for

> routine startup.** Most of its work is now performed by **phase 1

> of the Administrator agent**; see

> [Administrator-prompt.md](Administrator-prompt.md) and

> `plan/orchestration.md` §6.4 / §9.6 / §13.1.

>

> This file remains **canonical for the checklist content** —

> Administrator phase 1 walks §1-§10 below, plus the §11

> Target-branch dependency verification block (added in v2 to catch

> the `pytest-timeout` gap that leaked into the dry-run delta cycle —

> see `dry-run-Analyst-findings.md` F1). Re-init flows (credentials

> rotated, machine moved, `{base-branch}` switched) re-walk this

> document the same way.

> **v2.1 split** (per orchestration.md §3 / §8 v2.1 contract):

>

> - **Read-only checks** (§1, §2.1-§2.4, §3-§11): performed by

>   Administrator phase 1.

> - **§2.5 write-capability verification (push + delete a scratch

>   `init-check-*` ref):** **NOT** performed by Administrator,

>   because v2.1 makes Administrator read-only on the repository.

>   The user runs §2.5's commands manually OR launches the v1

>   standalone [Initialization-prompt.md](Initialization-prompt.md)

>   session (which retains its narrow `init-check-*` push allowlist).

>   Administrator phase 1 then asks the user to confirm "verified"

>   before entering phase 2 monitoring.

>

> The v1 standalone Initialization session remains an acceptable

> fallback — see [Initialization-prompt.md](Initialization-prompt.md).

> New deployments should start the Administrator agent first per

> `plan/orchestration.md` §13.1 instead.

> This file remains **canonical for the checklist content** —

> Administrator phase 1 walks §1-§11 (skipping §2.5), and the v1

> Initialization-prompt.md fallback or a manual user invocation

> covers §2.5. Re-init flows (credentials rotated, machine moved,

> `{base-branch}` switched) re-walk this document the same way.



---