@synap-core/workspace-templates 0.24.1 → 0.25.0

package/src/builder.yaml

@@ -1030,6 +1030,38 @@ profiles:
         label: Session Key
         valueType: string
 
+  # `issue` is a CORE kind: the pod seeds it on every pod (ensure-system-profiles.ts,
+  # "an open bug or problem" → issue) with its ONE lifecycle `issueStatus`
+  # (ensure-system-lifecycles.ts). Declared here to match the seed exactly, the way
+  # research-base declares `research`, so the Fix a bug playbook can name its
+  # statusProperty. Pod-local extras (severity, night-shift-run) are not core: not here.
+  # ONE deviation from the seed: `wont_fix` is humanOnly (a person decides an issue
+  # is not worth fixing), which the playbook's humanOnlyStatuses below requires.
+  - slug: issue
+    displayName: Issue
+    icon: bug
+    color: "#EF4444"
+    description: An open bug or problem, titled as the problem itself. Moves open → investigating → fixed or won't fix.
+    lifecycle:
+      property: issueStatus
+      options:
+        - { key: open, category: open }
+        - { key: investigating, category: active }
+        - { key: fixed, category: done }
+        - { key: wont_fix, category: lost, humanOnly: true }
+    properties:
+      - slug: issueStatus
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [open, investigating, fixed, wont_fix]
+        constraints: { defaultValue: open }
+      - slug: description
+        label: Description
+        valueType: string
+        inputType: textarea
+        constraints: { maxLength: 5000 }
+
   - slug: skill
     displayName: Skill
     icon: zap
@@ -2086,6 +2118,741 @@ playbooks:
         statement: Each Ship a change session covered got its dogfooded evidence, passed only when every path works.
         check: { kind: judge }
 
+  # THE SIX DEV PLAYBOOKS (decision d05, founder instruction 2026-11-05): Build a
+  # change, Fix a bug, Investigate, Review a change, Maintain, Fix main red.
+  # Mirrored field by field from the six draft playbook proposals filed on the Builder
+  # pod (stored shape; humanOnlyStatuses lifted to the top-level wire spelling).
+  # ALL `status: draft` and NO activators: a pod keeps its own draft/active
+  # choice on later template updates, and a person turns each on.
+
+  # --- Build a change ---
+  - name: Build a change
+    description: 'Dev set (decision d05), key: build. Works one feature (devplane_feature) from shaped criteria to a verified change on main; its stages follow the feature''s lifecycle (spec, in_progress, in_review, done), and a cancelled or failed session puts the feature back to spec so nothing is left half-claimed. One feature per session, never two subjects (founder default, 2026-11-05). A quick change is this playbook with size small (no plan); a night shift run is this playbook with unattended true. No activators until binding is turned on; the shape would be {on: enters_status, status: spec, size: per_thing, mode: propose}, the trigger Ship a change uses today. Reuses Ship a change (2c5aa553) stage text and evidence keys; absorbs AI Dev Session and Quick change once they are re-pointed. Draft until the founder activates it.'
+    goalTemplate: 'Build {feature} through one session and one PR per repo (or gated commits on main in a private repo), size {size}. SHAPE: write the end state and 2-5 binary criteria on this session (plan skill, skipped when size is small). BUILD: branch <type>/<slug> from origin/main in your own worktree, commit in verified slices, run the smallest gate that answers with its negative control, quote the output. LAND: follow the land stages (Change proposed, Checks green, Landed on main, Deployed to lab, Dogfooded, Criteria verified). Unattended: {unattended}. When unattended is true, ask no person, stop at a draft PR or a gated branch, never merge, push main or deploy, and post one "Look at first:" paragraph in the room.'
+    scope: session
+    subjectProfile:
+      onEnd:
+        failed: spec
+        cancelled: spec
+      profileSlug: devplane_feature
+      statusProperty: featureStatus
+    humanOnlyStatuses:
+    - backlog
+    - cancelled
+    params:
+    - name: feature
+      type: entity
+      label: Feature
+      required: true
+    - name: size
+      type: choice
+      label: How big is the change?
+      default: normal
+      options:
+      - small
+      - normal
+    - name: unattended
+      type: boolean
+      label: Run without a person (night shift)?
+      default: false
+    executor: is-agent
+    status: draft
+    stages:
+    - key: shape
+      goal: Write the end state and 2-5 binary criteria on the session, set the feature's change type, and name the repos the change touches.
+      name: Shaped
+      category: planned
+      criteria:
+      - key: shape-criteria-written
+        check:
+          kind: judge
+        statement: The session states the end state and 2-5 binary criteria a check, a judge or a person can grade.
+      - key: shape-change-typed
+        check:
+          kind: judge
+        statement: The feature's change type is set (feature, refactor or chore) and the repos it touches are named.
+      description: 'Load the plan skill; skip it when size is small (criteria alone are enough). Recall first: synap_ask "<area> gotchas". Tools: read only (code, pod). Gate: none. Model tier: deep (advisory until a tier field exists).'
+      subjectStatus: spec
+      expectedOutputs:
+      - kind: document
+        label: Plan (skipped when size is small)
+        optional: true
+        relationToSubject: relates_to
+    - key: build
+      goal: Build on a branch named after the work, from origin/main in your own worktree; commit in verified slices and run the smallest gate that answers for each finished slice, with its negative control.
+      name: Building
+      category: started
+      criteria:
+      - key: build-gates-quoted
+        check:
+          kind: judge
+        statement: Each finished slice was gated once (the smallest gate that answers) and its output is quoted in the room, red lines attributed against main.
+      - key: build-negative-control
+        check:
+          kind: judge
+        statement: Every new test was run with its fix reverted and failed.
+      description: 'Load the verified-wave skill. Commit a checkpoint about every 30 minutes and post it in the room. Never run git checkout --, restore, stash or a working-tree reset in a shared tree (rule shared-tree). Tools: edit, git in your own worktree, devbox gates (rule devbox-gates). Gate: none here; the Checks green stage sends a red back to this stage. Model tier: standard (advisory until a tier field exists).'
+      subjectStatus: in_progress
+      expectedOutputs:
+      - kind: commit
+        label: Gated commit sha
+    - key: pr-opened
+      goal: 'Record the change as one outcome with its url: a draft PR in a public repo, or a pushed branch gated at its exact sha in a private repo.'
+      name: Change proposed
+      category: started
+      criteria:
+      - key: change-recorded
+        check:
+          kind: judge
+        statement: 'The change is recorded on the session as an outcome with its url: pr-<repo>-<number> for a public repo, commit-<repo>-<sha8> for a private repo.'
+      - key: pr-names-session
+        check:
+          kind: judge
+        statement: A pull request body, when there is one, carries the line naming this Pod session.
+      description: 'Shared land stage. Public repo (backend, synap-cli): open a DRAFT pull request whose body carries the line "Pod session: <session id>", then record the outcome pr-<repo>-<number> (kind pull_request, ref url). Private repo (app-bases, browser, relay-app, control-plane-api, control-plane-dashboard, synap-bridge): no PR; rebase on origin/main, push the branch and queue the smallest devbox gate on its full sha with GATE_POD_SESSION set. One session, one PR per repo. Done by the ship flow and the outcome verbs, not by free reasoning. Rules: work-units, github-ci, devbox-gates. Tools: git, gh, devbox queue, synap_update_session. Gate: none. Model tier: quick (advisory until a tier field exists).'
+      subjectStatus: in_review
+      expectedOutputs:
+      - kind: pull_request
+        label: Draft pull request (outcome pr-<repo>-<number>, ref = its url); public repo only
+        optional: true
+    - key: checks
+      gate:
+        kind: check
+      goal: 'Every required check on the exact head is green: the 4 required backend checks, or the devbox gate on the private repo''s sha.'
+      name: Checks green
+      onFail:
+        toStage: build
+      category: started
+      criteria:
+      - key: checks-green
+        check:
+          hint: Posted by the ci.finished automation, by the worker after github_pr_checks on the head sha, or with the devbox summary of the exact sha for a private repo.
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: Every required check on the head finished green (the 4 required backend checks, or the devbox gate on the exact sha in a private repo).
+      description: 'Shared land stage. Backend: mark the draft ready once, when the slice is done and gated; it is done when Release gate, Full suite, API e2e and Reference docs are current are green on its head (github_pr_checks or the ci.finished event). Private repo: the devbox gate on that full sha is green with no INFRA result. A red you did not cause is not yours: read main''s latest run or the [vs main] mark first. A red that is yours goes back to the work stage; push the fix once. Done by CI, the devbox and the ci.finished automation, not by free reasoning. Tools: gh read, devbox status. Model tier: quick (advisory until a tier field exists).'
+    - key: merge
+      goal: 'The change reaches main through its door: the merge bot for backend, a fast-forward push of the gated sha for a private repo.'
+      name: Landed on main
+      category: started
+      criteria:
+      - key: merged
+        check:
+          hint: Posted by the dev.pr_merged automation, by the worker after github_pr_get (merged true), or with the commit url on main for a private repo.
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The change is on main and its outcome is marked complete.
+      description: 'Shared land stage. Backend: never run gh pr merge (with or without --auto, never --admin) and never enqueue the PR yourself; the merge bot enqueues a ready, green PR whose body names the session. A PR touching CI or test infrastructure waits 2 h after green unless the founder runs prcheck --merge backend <n>: say so. Private repo: git push origin <sha>:main of the exact gated sha, fast-forward only, never --force; if main moved, only a clean rebase touching none of your files may go, otherwise gate again. Then completeOutput on the outcome. An unattended run stops before this stage. Done by the merge bot, the bridge and the outcome verbs. Tools: git push (private repo only), synap_update_session. Gate: none (the bridge and the merge bot hold the evidence). Model tier: quick (advisory until a tier field exists).'
+    - key: deploy
+      gate:
+        kind: human
+      goal: A person approves the lab deploy of the merged build; record the deployed sha.
+      name: Deployed to lab
+      onFail:
+        toStage: build
+      category: started
+      criteria:
+      - key: deployed
+        check:
+          hint: The deployed sha contains the merge commit (github_compare base merge commit, head deployed sha, status identical or ahead).
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The lab runs a build that contains the merge commit.
+      description: 'Shared land stage. Ask with synap_request_deploy_approval; the deploy is the person''s call and releases stay the founder''s. Skip with a one-line reason in the room when the change never reaches a running pod (CI, tests, docs, tooling). Never in an unattended run. Tools: synap_request_deploy_approval, github_compare. Model tier: quick (advisory until a tier field exists).'
+    - key: dogfood
+      gate:
+        kind: check
+      goal: Walk the change in the running lab as a person would, entering through the doors a person enters through, and report WORKS, BROKEN or CANNOT-TELL with what was seen.
+      name: Dogfooded
+      onFail:
+        toStage: build
+      category: started
+      criteria:
+      - key: dogfooded
+        check:
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The dogfood walk reports WORKS on every path the change touches.
+      description: 'Shared land stage. Load the dogfood skill, or start Dogfood a change (08a4929c) as a child session for a deployed change. A BROKEN path becomes a finding and the run goes back to the work stage. Skip with a one-line reason when nothing a person sees changed. Tools: browser automation, screenshots, read. Model tier: standard (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: document
+        label: Dogfood report (each path WORKS, BROKEN or CANNOT-TELL, with what was seen)
+        optional: true
+        relationToSubject: relates_to
+    - key: verify
+      goal: Grade every criterion of the session with its evidence, separating VERIFIED (gate or check output quoted) from NEEDS-DOGFOOD, capture what was learned, and close the session.
+      name: Criteria verified
+      category: completed
+      criteria:
+      - key: criteria-verified
+        check:
+          kind: judge
+        statement: Every criterion of the session is graded with its evidence, and nothing unverified is reported as verified.
+      description: 'Shared land stage. Never report unverified work as verified. File the lesson, decision or finding the work produced (engineering-memory skill, rule dogfood-journal). Close what you opened: asks answered or withdrawn, worktree removed once merged, then synap_complete_session. Moving the feature to done is a proposal the person approves. Tools: synap_update_session, synap_capture, synap_complete_session. Gate: none. Model tier: quick (advisory until a tier field exists).'
+      subjectStatus: done
+
+  # --- Fix a bug ---
+  - name: Fix a bug
+    description: 'Dev set (decision d05), key: fix. Works an issue at its root: reproduce it with a failing test, fix the canonical path, a clean-context review, then the shared land stages. Its stages follow the issue''s lifecycle (open, investigating, fixed); a cancelled or failed session puts the issue back to open, as Fix a finding does. Small fixes may be batched (founder default, 2026-11-05): several issues in one session, one as the subject and the rest as session targets; today a stage moves only the subject, and the session end moves the subject and every target still open. No activators until binding is turned on; a batch would be {on: count, status: open, min: 3} or {on: schedule, cron, status: open} (both one session per moment). A night shift run is this playbook with unattended true. Reuses Bugfix (8c335e2e), Night shift: build an issue (c101dd75) and Ship a change (2c5aa553). Draft until the founder activates it.'
+    goalTemplate: 'Fix the issue {issue} at its root and prove it with a test that fails before the fix and passes after. REPRODUCE (recall first, smallest reproduction, root cause file:line), FIX on the canonical path in your own worktree, a clean-context REVIEW, then LAND through the shared land stages (Change proposed, Checks green, Landed on main, Deployed to lab, Dogfooded, Criteria verified). Unattended: {unattended}. When unattended is true, ask no person, stop at a draft PR or a gated branch, never merge, push main or deploy; if no code fix is right, write the root cause as a pod document; post one "Look at first:" paragraph in the room.'
+    scope: session
+    subjectProfile:
+      onEnd:
+        failed: open
+        cancelled: open
+      profileSlug: issue
+      statusProperty: issueStatus
+    # Added to the pod draft (it has none; the catalog's lifecycle-coverage check
+    # needs every option owned): `open` is where an issue starts and a failed or
+    # cancelled session returns it (onEnd), `wont_fix` is a person's call.
+    humanOnlyStatuses:
+      - open
+      - wont_fix
+    params:
+    - name: issue
+      type: entity
+      label: Issue
+      required: true
+    - name: unattended
+      type: boolean
+      label: Run without a person (night shift)?
+      default: false
+    executor: is-agent
+    status: draft
+    stages:
+    - key: reproduce
+      goal: Show the bug happening with the smallest reproduction (a failing test or the exact steps) and name its root cause with file:line.
+      name: Reproduce
+      category: planned
+      criteria:
+      - key: repro-shown
+        check:
+          kind: judge
+        statement: A test or exact reproduction shows the bug, and the root cause is named with file:line.
+      description: 'Load the engineering-memory skill and recall first: synap_ask "<area> gotchas". Name the root cause, not the symptom. Tools: read, devbox (one test file at the smallest rung). Gate: none. Model tier: standard (advisory until a tier field exists).'
+      subjectStatus: investigating
+      suggestedTasks:
+      - recall known gotchas for the area
+      - write the failing test or the exact repro steps
+      - name the root cause, not the symptom
+      expectedOutputs:
+      - kind: note
+        label: 'Reproduction: failing test path or exact steps, and the root cause (file:line)'
+    - key: fix
+      gate:
+        kind: check
+      goal: Fix the root cause on the canonical path; the reproduction test now passes and was seen failing with the fix reverted.
+      name: Fix
+      onFail:
+        toStage: reproduce
+      category: started
+      criteria:
+      - key: fix-negative-control
+        check:
+          kind: judge
+        statement: The reproduction test passes with the fix and fails with the fix reverted; the gate output is quoted in the room.
+      description: 'Load the verified-wave skill. Branch fix/<slug> from origin/main in your own worktree. The entry check judges Reproduce: no reproduction sends the run back. Tools: edit, git in your own worktree, devbox (be-file or *-touched). Model tier: standard (advisory until a tier field exists).'
+      suggestedTasks:
+      - fix the root cause
+      - 'negative control: revert the fix, see the test fail'
+      - run the smallest gate yourself and quote it
+      expectedOutputs:
+      - kind: commit
+        label: Gated fix commit sha
+    - key: review
+      gate:
+        kind: check
+      goal: A separate session with a clean context reads the fix and lists must-fix findings apart from justified-keep ones.
+      name: Review
+      onFail:
+        toStage: fix
+      category: started
+      criteria:
+      - key: review-clean
+        check:
+          kind: judge
+        statement: The review lists no open must-fix finding.
+      description: 'Load the pr-review skill in a review child session, never the author. The author answers every finding; a must-fix finding sends the run back to Fix before landing. The entry check judges Fix (test green, negative control seen red). Tools: read only. Model tier: deep (advisory until a tier field exists).'
+      suggestedTasks:
+      - start a review child session (not the author)
+      - author answers every finding
+      expectedOutputs:
+      - kind: document
+        label: Review note (must-fix and justified-keep, with file:line)
+        relationToSubject: relates_to
+    - key: pr-opened
+      goal: 'Record the change as one outcome with its url: a draft PR in a public repo, or a pushed branch gated at its exact sha in a private repo.'
+      name: Change proposed
+      category: started
+      criteria:
+      - key: change-recorded
+        check:
+          kind: judge
+        statement: 'The change is recorded on the session as an outcome with its url: pr-<repo>-<number> for a public repo, commit-<repo>-<sha8> for a private repo.'
+      - key: pr-names-session
+        check:
+          kind: judge
+        statement: A pull request body, when there is one, carries the line naming this Pod session.
+      description: 'Shared land stage. Public repo (backend, synap-cli): open a DRAFT pull request whose body carries the line "Pod session: <session id>", then record the outcome pr-<repo>-<number> (kind pull_request, ref url). Private repo (app-bases, browser, relay-app, control-plane-api, control-plane-dashboard, synap-bridge): no PR; rebase on origin/main, push the branch and queue the smallest devbox gate on its full sha with GATE_POD_SESSION set. One session, one PR per repo. Done by the ship flow and the outcome verbs, not by free reasoning. Rules: work-units, github-ci, devbox-gates. Tools: git, gh, devbox queue, synap_update_session. Gate: none. Model tier: quick (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: pull_request
+        label: Draft pull request (outcome pr-<repo>-<number>, ref = its url); public repo only
+        optional: true
+    - key: checks
+      gate:
+        kind: check
+      goal: 'Every required check on the exact head is green: the 4 required backend checks, or the devbox gate on the private repo''s sha.'
+      name: Checks green
+      onFail:
+        toStage: fix
+      category: started
+      criteria:
+      - key: checks-green
+        check:
+          hint: Posted by the ci.finished automation, by the worker after github_pr_checks on the head sha, or with the devbox summary of the exact sha for a private repo.
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: Every required check on the head finished green (the 4 required backend checks, or the devbox gate on the exact sha in a private repo).
+      description: 'Shared land stage. Backend: mark the draft ready once, when the slice is done and gated; it is done when Release gate, Full suite, API e2e and Reference docs are current are green on its head (github_pr_checks or the ci.finished event). Private repo: the devbox gate on that full sha is green with no INFRA result. A red you did not cause is not yours: read main''s latest run or the [vs main] mark first. A red that is yours goes back to the work stage; push the fix once. Done by CI, the devbox and the ci.finished automation, not by free reasoning. Tools: gh read, devbox status. Model tier: quick (advisory until a tier field exists).'
+    - key: merge
+      goal: 'The change reaches main through its door: the merge bot for backend, a fast-forward push of the gated sha for a private repo.'
+      name: Landed on main
+      category: started
+      criteria:
+      - key: merged
+        check:
+          hint: Posted by the dev.pr_merged automation, by the worker after github_pr_get (merged true), or with the commit url on main for a private repo.
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The change is on main and its outcome is marked complete.
+      description: 'Shared land stage. Backend: never run gh pr merge (with or without --auto, never --admin) and never enqueue the PR yourself; the merge bot enqueues a ready, green PR whose body names the session. A PR touching CI or test infrastructure waits 2 h after green unless the founder runs prcheck --merge backend <n>: say so. Private repo: git push origin <sha>:main of the exact gated sha, fast-forward only, never --force; if main moved, only a clean rebase touching none of your files may go, otherwise gate again. Then completeOutput on the outcome. An unattended run stops before this stage. Done by the merge bot, the bridge and the outcome verbs. Tools: git push (private repo only), synap_update_session. Gate: none (the bridge and the merge bot hold the evidence). Model tier: quick (advisory until a tier field exists).'
+    - key: deploy
+      gate:
+        kind: human
+      goal: A person approves the lab deploy of the merged build; record the deployed sha.
+      name: Deployed to lab
+      onFail:
+        toStage: fix
+      category: started
+      criteria:
+      - key: deployed
+        check:
+          hint: The deployed sha contains the merge commit (github_compare base merge commit, head deployed sha, status identical or ahead).
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The lab runs a build that contains the merge commit.
+      description: 'Shared land stage. Ask with synap_request_deploy_approval; the deploy is the person''s call and releases stay the founder''s. Skip with a one-line reason in the room when the change never reaches a running pod (CI, tests, docs, tooling). Never in an unattended run. Tools: synap_request_deploy_approval, github_compare. Model tier: quick (advisory until a tier field exists).'
+    - key: dogfood
+      gate:
+        kind: check
+      goal: Walk the change in the running lab as a person would, entering through the doors a person enters through, and report WORKS, BROKEN or CANNOT-TELL with what was seen.
+      name: Dogfooded
+      onFail:
+        toStage: fix
+      category: started
+      criteria:
+      - key: dogfooded
+        check:
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The dogfood walk reports WORKS on every path the change touches.
+      description: 'Shared land stage. Load the dogfood skill, or start Dogfood a change (08a4929c) as a child session for a deployed change. Re-run the original reproduction where the issue was reported. A BROKEN path becomes a finding and the run goes back to the work stage. Skip with a one-line reason when nothing a person sees changed. Tools: browser automation, screenshots, read. Model tier: standard (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: document
+        label: Dogfood report (each path WORKS, BROKEN or CANNOT-TELL, with what was seen)
+        optional: true
+        relationToSubject: relates_to
+    - key: verify
+      goal: Grade every criterion of the session with its evidence, separating VERIFIED (gate or check output quoted) from NEEDS-DOGFOOD, capture what was learned, and close the session.
+      name: Criteria verified
+      category: completed
+      criteria:
+      - key: criteria-verified
+        check:
+          kind: judge
+        statement: Every criterion of the session is graded with its evidence, and nothing unverified is reported as verified.
+      description: 'Shared land stage. Never report unverified work as verified. File the lesson, decision or finding the work produced (engineering-memory skill, rule dogfood-journal). Close what you opened: asks answered or withdrawn, worktree removed once merged, then synap_complete_session. Moving the issue to fixed is a proposal the person approves. Tools: synap_update_session, synap_capture, synap_complete_session. Gate: none. Model tier: quick (advisory until a tier field exists).'
+      subjectStatus: fixed
+
+  # --- Investigate ---
+  - name: Investigate
+    description: 'Dev set (decision d05), key: investigate. Works a feature (devplane_feature) before anyone builds it, usually while it is an idea (backlog): frame the question, measure, and conclude with a recommendation (continue, cut or reshape) in one pod document. It moves no status itself: taking the feature to spec or dropping it stays the person''s call. Changes no code. One feature per session. No activators until binding is turned on. Absorbs Evaluate Feature (11b3acd8) once it is re-pointed; reuses the stage shape of Research a Question (418e862a). Draft until the founder activates it.'
+    goalTemplate: 'Investigate {question} and answer it with evidence. FRAME: restate the question so it can be answered and say what evidence would answer it. MEASURE: read the code at the installed version, measure on real data, keep rejected sources with their reason, and label every number MEASURED, READ or ESTIMATED. CONCLUDE: write the answer, its confidence and a recommendation (for a feature: continue, cut or reshape, with the reasoning) as one pod document; a choice only the founder can make goes into a decision brief. Change no code.'
+    scope: session
+    subjectProfile:
+      profileSlug: devplane_feature
+    params:
+    - name: question
+      type: text
+      label: What question should this answer?
+      required: true
+    - name: feature
+      type: entity
+      label: Feature it is about
+    executor: is-agent
+    status: draft
+    stages:
+    - key: frame
+      goal: Restate the question so it can be answered and say what evidence would answer it.
+      name: Framed
+      category: planned
+      criteria:
+      - key: question-answerable
+        check:
+          kind: judge
+        statement: The question is restated so it can be answered, and the evidence that would answer it is named.
+      description: 'Recall first: synap_ask on the area, and read what the pod already settled. Load research-decision-room when options must be compared, decision-brief when the answer is a founder decision. Tools: read only (code, pod, web). Gate: none. Model tier: deep (advisory until a tier field exists).'
+    - key: measure
+      goal: 'Gather the evidence: read the code at the installed version, measure on real data, and keep rejected sources with their reason.'
+      name: Measured
+      category: started
+      criteria:
+      - key: sources-kept
+        check:
+          kind: judge
+        statement: Every source or measure used is cited, and rejected ones are kept with their reason.
+      description: 'Label every number MEASURED, READ or ESTIMATED. No code change and no write except pod captures. Tools: read only; a devbox read gate only when a measure needs one (smallest rung). Gate: none. Model tier: deep (advisory until a tier field exists).'
+    - key: conclude
+      gate:
+        kind: check
+      goal: Write the answer, its confidence and a recommendation as one pod document linked to the session.
+      name: Concluded
+      onFail:
+        toStage: measure
+      category: completed
+      criteria:
+      - key: every-number-labeled
+        check:
+          kind: judge
+        statement: Every number in the document is labeled MEASURED, READ or ESTIMATED, and the recommendation follows from the evidence.
+      description: 'The entry check judges Measure: an unlabeled number or an uncited claim sends the run back. Open choices only a person can settle go into a decision brief (decision-brief skill), each with a recommendation. Capture what stays true as knowledge. Tools: synap_create_document, synap_capture. Model tier: deep (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: document
+        label: Investigation (question, measured evidence, recommendation)
+        relationToSubject: relates_to
+
+  # --- Review a change ---
+  - name: Review a change
+    description: 'Dev set (decision d05), key: review. Works a feature in review (devplane_feature at in_review): a read-only, clean-context review of its change; every finding is must-fix or justified-keep, with its reason and file:line, and goes to the author''s session. Moves no status. Never the author; the author applies the fixes. Reviewing a fix runs as the review child of a Fix a bug session. There is no pull request kind: a PR is an outcome url, not an object. No activators until binding is turned on. Reuses the review stage of Bugfix (8c335e2e) and Quick change (63552bed). Draft until the founder activates it.'
+    goalTemplate: 'Review {target} with a clean context and give a verdict. READ the change, the rules it touches and what it can break. VERDICT: list every finding as must-fix (why it is real) or justified-keep (why it stays), each with file:line, in one review document, and post it to the author''s session. Read only: apply nothing.'
+    scope: session
+    subjectProfile:
+      profileSlug: devplane_feature
+    params:
+    - name: target
+      type: text
+      label: What to review (a PR url, a branch, a sha or a document)
+      required: true
+    - name: feature
+      type: entity
+      label: Feature under review
+    executor: is-agent
+    status: draft
+    stages:
+    - key: read
+      goal: 'Read the change with a clean context: the diff, the rules it touches, and what it can break.'
+      name: Read
+      category: started
+      criteria:
+      - key: read-whole-change
+        check:
+          kind: judge
+        statement: The whole change and the rules it touches were read; nothing was edited.
+      description: 'Load pr-review for one pull request, parallel-review for a substantial build (independent read-only lenses). Never review your own work. Tools: read only (gh read, code, pod). Gate: none. Model tier: deep (advisory until a tier field exists).'
+    - key: verdict
+      goal: List findings as must-fix (why it is real) or justified-keep (why it stays), each with file:line, and post the verdict to the author's session.
+      name: Verdict
+      category: completed
+      criteria:
+      - key: findings-justified
+        check:
+          kind: judge
+        statement: Every finding is classed must-fix or justified-keep with its reason and file:line.
+      description: 'Send the document to the author''s session (synap_post_message with toSessionId, intent handoff); the author answers every finding and applies the fixes. Gate: none (the author''s own playbook gates on an empty must-fix list). Tools: synap_create_document, synap_post_message. Model tier: deep (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: document
+        label: Review (must-fix and justified-keep, with file:line)
+        relationToSubject: relates_to
+
+  # --- Maintain ---
+  - name: Maintain
+    description: 'Dev set (decision d05), key: maintain. Works a task (one bounded chore: a dependency bump, a cleanup, a prune) in your own worktree, gated at the smallest rung, then the shared land stages when something changed. Nothing to change ends the session with a one-line reason. Small chores may be batched: several tasks in one session, one as the subject and the rest as targets. It writes no task status yet: the task lifecycle property is not confirmed (Builder''s task-status is a plain select with no declared lifecycle). No activators until binding is turned on. Draft until the founder activates it.'
+    goalTemplate: 'Do this chore: {chore} (repo: {repo}). DO it in your own worktree and run the smallest gate that answers; if there is nothing to change, say why in one line and close. LAND it through the shared land stages only when something changed.'
+    scope: session
+    subjectProfile:
+      profileSlug: task
+    params:
+    - name: chore
+      type: text
+      label: What chore (bump, clean, prune)?
+      required: true
+    - name: repo
+      type: text
+      label: Which repo?
+      default: any
+    - name: task
+      type: entity
+      label: Task it works, if any
+    executor: is-agent
+    status: draft
+    stages:
+    - key: do
+      goal: Do the bounded chore in your own worktree, or show there is nothing to do.
+      name: Done in a worktree
+      category: started
+      criteria:
+      - key: chore-gated
+        check:
+          kind: judge
+        statement: The chore is done and its smallest gate is green and quoted, or the session says in one line why nothing changed.
+      description: 'Rules: devbox-gates (smallest gate that answers) and shared-tree (never checkout --, restore, stash or a working-tree reset). Remove only what the chore names or what your change made unused. Tools: edit, git in your own worktree, devbox. Gate: none; nothing to change ends the session with a one-line reason and skips the land stages. Model tier: quick (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: commit
+        label: Gated commit sha (none when nothing changed)
+        optional: true
+    - key: pr-opened
+      goal: 'Record the change as one outcome with its url: a draft PR in a public repo, or a pushed branch gated at its exact sha in a private repo.'
+      name: Change proposed
+      category: started
+      criteria:
+      - key: change-recorded
+        check:
+          kind: judge
+        statement: 'The change is recorded on the session as an outcome with its url: pr-<repo>-<number> for a public repo, commit-<repo>-<sha8> for a private repo.'
+      - key: pr-names-session
+        check:
+          kind: judge
+        statement: A pull request body, when there is one, carries the line naming this Pod session.
+      description: 'Shared land stage. Public repo (backend, synap-cli): open a DRAFT pull request whose body carries the line "Pod session: <session id>", then record the outcome pr-<repo>-<number> (kind pull_request, ref url). Private repo (app-bases, browser, relay-app, control-plane-api, control-plane-dashboard, synap-bridge): no PR; rebase on origin/main, push the branch and queue the smallest devbox gate on its full sha with GATE_POD_SESSION set. One session, one PR per repo. Done by the ship flow and the outcome verbs, not by free reasoning. Rules: work-units, github-ci, devbox-gates. Tools: git, gh, devbox queue, synap_update_session. Gate: none. Model tier: quick (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: pull_request
+        label: Draft pull request (outcome pr-<repo>-<number>, ref = its url); public repo only
+        optional: true
+    - key: checks
+      gate:
+        kind: check
+      goal: 'Every required check on the exact head is green: the 4 required backend checks, or the devbox gate on the private repo''s sha.'
+      name: Checks green
+      onFail:
+        toStage: do
+      category: started
+      criteria:
+      - key: checks-green
+        check:
+          hint: Posted by the ci.finished automation, by the worker after github_pr_checks on the head sha, or with the devbox summary of the exact sha for a private repo.
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: Every required check on the head finished green (the 4 required backend checks, or the devbox gate on the exact sha in a private repo).
+      description: 'Shared land stage. Backend: mark the draft ready once, when the slice is done and gated; it is done when Release gate, Full suite, API e2e and Reference docs are current are green on its head (github_pr_checks or the ci.finished event). Private repo: the devbox gate on that full sha is green with no INFRA result. A red you did not cause is not yours: read main''s latest run or the [vs main] mark first. A red that is yours goes back to the work stage; push the fix once. Done by CI, the devbox and the ci.finished automation, not by free reasoning. Tools: gh read, devbox status. Model tier: quick (advisory until a tier field exists).'
+    - key: merge
+      goal: 'The change reaches main through its door: the merge bot for backend, a fast-forward push of the gated sha for a private repo.'
+      name: Landed on main
+      category: started
+      criteria:
+      - key: merged
+        check:
+          hint: Posted by the dev.pr_merged automation, by the worker after github_pr_get (merged true), or with the commit url on main for a private repo.
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The change is on main and its outcome is marked complete.
+      description: 'Shared land stage. Backend: never run gh pr merge (with or without --auto, never --admin) and never enqueue the PR yourself; the merge bot enqueues a ready, green PR whose body names the session. A PR touching CI or test infrastructure waits 2 h after green unless the founder runs prcheck --merge backend <n>: say so. Private repo: git push origin <sha>:main of the exact gated sha, fast-forward only, never --force; if main moved, only a clean rebase touching none of your files may go, otherwise gate again. Then completeOutput on the outcome. An unattended run stops before this stage. Done by the merge bot, the bridge and the outcome verbs. Tools: git push (private repo only), synap_update_session. Gate: none (the bridge and the merge bot hold the evidence). Model tier: quick (advisory until a tier field exists).'
+    - key: deploy
+      gate:
+        kind: human
+      goal: A person approves the lab deploy of the merged build; record the deployed sha.
+      name: Deployed to lab
+      onFail:
+        toStage: do
+      category: started
+      criteria:
+      - key: deployed
+        check:
+          hint: The deployed sha contains the merge commit (github_compare base merge commit, head deployed sha, status identical or ahead).
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The lab runs a build that contains the merge commit.
+      description: 'Shared land stage. Ask with synap_request_deploy_approval; the deploy is the person''s call and releases stay the founder''s. Skip with a one-line reason in the room when the change never reaches a running pod (CI, tests, docs, tooling). Never in an unattended run. Tools: synap_request_deploy_approval, github_compare. Model tier: quick (advisory until a tier field exists).'
+    - key: dogfood
+      gate:
+        kind: check
+      goal: Walk the change in the running lab as a person would, entering through the doors a person enters through, and report WORKS, BROKEN or CANNOT-TELL with what was seen.
+      name: Dogfooded
+      onFail:
+        toStage: do
+      category: started
+      criteria:
+      - key: dogfooded
+        check:
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The dogfood walk reports WORKS on every path the change touches.
+      description: 'Shared land stage. Load the dogfood skill, or start Dogfood a change (08a4929c) as a child session for a deployed change. A BROKEN path becomes a finding and the run goes back to the work stage. Skip with a one-line reason when nothing a person sees changed. Tools: browser automation, screenshots, read. Model tier: standard (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: document
+        label: Dogfood report (each path WORKS, BROKEN or CANNOT-TELL, with what was seen)
+        optional: true
+        relationToSubject: relates_to
+    - key: verify
+      goal: Grade every criterion of the session with its evidence, separating VERIFIED (gate or check output quoted) from NEEDS-DOGFOOD, capture what was learned, and close the session.
+      name: Criteria verified
+      category: completed
+      criteria:
+      - key: criteria-verified
+        check:
+          kind: judge
+        statement: Every criterion of the session is graded with its evidence, and nothing unverified is reported as verified.
+      description: 'Shared land stage. Never report unverified work as verified. File the lesson, decision or finding the work produced (engineering-memory skill, rule dogfood-journal). Close what you opened: asks answered or withdrawn, worktree removed once merged, then synap_complete_session. Tools: synap_update_session, synap_capture, synap_complete_session. Gate: none. Model tier: quick (advisory until a tier field exists).'
+
+  # --- Fix main red ---
+  - name: Fix main red
+    description: 'Dev set (decision d05), key: main-red. Own one red on main, once: claim it or join its owner, read the failing step, fix forward on fix/main-red-<sha8>, then the shared land stages. No subject kind: a session titled "main red: <repo> <check> @<sha8>" (the title the github-ci rule mandates) is how it is started. Stage text comes from the github-ci rule section "Never". Draft until the founder activates it.'
+    goalTemplate: 'Fix main red on {repo}: check {check} at {sha8}. CLAIM it once or join its owner. READ the failing step and recall what the pod knows. FIX forward on branch fix/main-red-{sha8} with a PR titled "fix: main red", gated at the smallest rung; never revert-war. LAND it through the shared land stages and close this session once the fix is on main.'
+    scope: session
+    params:
+    - name: repo
+      type: text
+      label: Which repo is red?
+      required: true
+    - name: check
+      type: text
+      label: Which check is red?
+      required: true
+    - name: sha8
+      type: text
+      label: First 8 characters of the red main commit
+      required: true
+    executor: is-agent
+    status: draft
+    stages:
+    - key: claim
+      goal: 'Own the red once: look for an owner first, else claim it.'
+      name: Claimed
+      category: planned
+      criteria:
+      - key: one-owner
+        check:
+          kind: judge
+        statement: No older owner exists for this red, and the claim is posted in the wave's room.
+      description: 'Look for an owner: an open session titled "main red: <repo> ..." (synap_list_sessions), an open PR from fix/main-red-* or titled "fix: main red", or a pushed fix/main-red-* branch. An owner exists: send it what you know (synap_post_message, intent fyi) and stop. No owner: this session is titled "main red: <repo> <check> @<sha8>"; post "fixing main red <sha8>: <session id>" in the wave''s room, list sessions again, and cancel yours if an older one shows. Rule: github-ci. Tools: synap_list_sessions, synap_post_message, gh read. Gate: none. Model tier: quick (advisory until a tier field exists).'
+    - key: read-step
+      goal: Read the failing step (gh run view <run> --log-failed) and recall what the pod knows (synap_ask "<check name> red").
+      name: Failing step read
+      category: started
+      criteria:
+      - key: culprit-named
+        check:
+          kind: judge
+        statement: The failing step is quoted and the commit that caused it is named.
+      description: 'Attribute before acting: name the commit that turned main red. A red you did not cause in a lane is not this session''s work. Tools: gh read, synap_ask. Gate: none. Model tier: standard (advisory until a tier field exists).'
+    - key: fix
+      gate:
+        kind: check
+      goal: Fix forward on branch fix/main-red-<sha8>, gated at the smallest rung; never revert-war.
+      name: Fixed forward
+      onFail:
+        toStage: read-step
+      category: started
+      criteria:
+      - key: red-check-green
+        check:
+          kind: judge
+        statement: The red check passes on the fix branch, with the gate output quoted.
+      description: 'Load the verified-wave skill. If CI''s revert PR fix/main-red-revert-<pr>-<sha8> lands first, let it land and redo the change in a new PR. The entry check judges Read: no quoted failing step sends the run back. Tools: edit, git in your own worktree, devbox. Model tier: standard (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: commit
+        label: Gated fix commit sha on fix/main-red-<sha8>
+    - key: pr-opened
+      goal: 'Record the change as one outcome with its url: a draft PR in a public repo, or a pushed branch gated at its exact sha in a private repo.'
+      name: Change proposed
+      category: started
+      criteria:
+      - key: change-recorded
+        check:
+          kind: judge
+        statement: 'The change is recorded on the session as an outcome with its url: pr-<repo>-<number> for a public repo, commit-<repo>-<sha8> for a private repo.'
+      - key: pr-names-session
+        check:
+          kind: judge
+        statement: A pull request body, when there is one, carries the line naming this Pod session.
+      description: 'Shared land stage. Public repo (backend, synap-cli): open a DRAFT pull request whose body carries the line "Pod session: <session id>", then record the outcome pr-<repo>-<number> (kind pull_request, ref url). Private repo (app-bases, browser, relay-app, control-plane-api, control-plane-dashboard, synap-bridge): no PR; rebase on origin/main, push the branch and queue the smallest devbox gate on its full sha with GATE_POD_SESSION set. One session, one PR per repo. Done by the ship flow and the outcome verbs, not by free reasoning. Rules: work-units, github-ci, devbox-gates. Tools: git, gh, devbox queue, synap_update_session. Gate: none. Model tier: quick (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: pull_request
+        label: Draft pull request (outcome pr-<repo>-<number>, ref = its url); public repo only
+        optional: true
+    - key: checks
+      gate:
+        kind: check
+      goal: 'Every required check on the exact head is green: the 4 required backend checks, or the devbox gate on the private repo''s sha.'
+      name: Checks green
+      onFail:
+        toStage: fix
+      category: started
+      criteria:
+      - key: checks-green
+        check:
+          hint: Posted by the ci.finished automation, by the worker after github_pr_checks on the head sha, or with the devbox summary of the exact sha for a private repo.
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: Every required check on the head finished green (the 4 required backend checks, or the devbox gate on the exact sha in a private repo).
+      description: 'Shared land stage. Backend: mark the draft ready once, when the slice is done and gated; it is done when Release gate, Full suite, API e2e and Reference docs are current are green on its head (github_pr_checks or the ci.finished event). Private repo: the devbox gate on that full sha is green with no INFRA result. A red you did not cause is not yours: read main''s latest run or the [vs main] mark first. A red that is yours goes back to the work stage; push the fix once. Done by CI, the devbox and the ci.finished automation, not by free reasoning. Tools: gh read, devbox status. Model tier: quick (advisory until a tier field exists).'
+    - key: merge
+      goal: 'The change reaches main through its door: the merge bot for backend, a fast-forward push of the gated sha for a private repo.'
+      name: Landed on main
+      category: started
+      criteria:
+      - key: merged
+        check:
+          hint: Posted by the dev.pr_merged automation, by the worker after github_pr_get (merged true), or with the commit url on main for a private repo.
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The change is on main and its outcome is marked complete.
+      description: 'Shared land stage. Backend: never run gh pr merge (with or without --auto, never --admin) and never enqueue the PR yourself; the merge bot enqueues a ready, green PR whose body names the session (while main is red it enqueues only a main-red fix). A PR touching CI or test infrastructure waits 2 h after green unless the founder runs prcheck --merge backend <n>: say so. Private repo: git push origin <sha>:main of the exact gated sha, fast-forward only, never --force; if main moved, only a clean rebase touching none of your files may go, otherwise gate again. Then completeOutput on the outcome. An unattended run stops before this stage. Done by the merge bot, the bridge and the outcome verbs. Tools: git push (private repo only), synap_update_session. Gate: none (the bridge and the merge bot hold the evidence). Model tier: quick (advisory until a tier field exists).'
+    - key: deploy
+      gate:
+        kind: human
+      goal: A person approves the lab deploy of the merged build; record the deployed sha.
+      name: Deployed to lab
+      onFail:
+        toStage: fix
+      category: started
+      criteria:
+      - key: deployed
+        check:
+          hint: The deployed sha contains the merge commit (github_compare base merge commit, head deployed sha, status identical or ahead).
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The lab runs a build that contains the merge commit.
+      description: 'Shared land stage. Ask with synap_request_deploy_approval; the deploy is the person''s call and releases stay the founder''s. Skip with a one-line reason in the room when the change never reaches a running pod (CI, tests, docs, tooling). Never in an unattended run. Tools: synap_request_deploy_approval, github_compare. Model tier: quick (advisory until a tier field exists).'
+    - key: dogfood
+      gate:
+        kind: check
+      goal: Walk the change in the running lab as a person would, entering through the doors a person enters through, and report WORKS, BROKEN or CANNOT-TELL with what was seen.
+      name: Dogfooded
+      onFail:
+        toStage: fix
+      category: started
+      criteria:
+      - key: dogfooded
+        check:
+          kind: evidence
+          evidenceKey: '[CREDENTIAL REDACTED: Secret assignment]'
+        statement: The dogfood walk reports WORKS on every path the change touches.
+      description: 'Shared land stage. Load the dogfood skill, or start Dogfood a change (08a4929c) as a child session for a deployed change. A BROKEN path becomes a finding and the run goes back to the work stage. Skip with a one-line reason when nothing a person sees changed. Tools: browser automation, screenshots, read. Model tier: standard (advisory until a tier field exists).'
+      expectedOutputs:
+      - kind: document
+        label: Dogfood report (each path WORKS, BROKEN or CANNOT-TELL, with what was seen)
+        optional: true
+    - key: verify
+      goal: Grade every criterion of the session with its evidence, separating VERIFIED (gate or check output quoted) from NEEDS-DOGFOOD, capture what was learned, and close the session.
+      name: Criteria verified
+      category: completed
+      criteria:
+      - key: criteria-verified
+        check:
+          kind: judge
+        statement: Every criterion of the session is graded with its evidence, and nothing unverified is reported as verified.
+      description: 'Shared land stage. Never report unverified work as verified. File the lesson, decision or finding the work produced (engineering-memory skill, rule dogfood-journal). Close what you opened: asks answered or withdrawn, worktree removed once merged, then synap_complete_session. Tools: synap_update_session, synap_capture, synap_complete_session. Gate: none. Model tier: quick (advisory until a tier field exists).'
+
 onboarding:
   goal: Capture the real engineering surface — the apps that are shipped, where their code lives, what runs behind them, where they deploy, and what's in flight — so the workspace mirrors what the team actually builds and runs, not a generic template.
   framing: >