arreio 1.1.0 → 1.2.1

package/skills/work/references/id-generation.md

@@ -12,7 +12,7 @@ Shared ID algorithm for the `triage`, `prepare`, `execute`, and `review` phases,
 
 ## ID Format by Phase
 
-| Phase    | ID format                            | Saved to                         |
+| Phase    | ID format                            | Saved to (detailed only)                         |
 | -------- | ----------------------------------- | -------------------------------- |
 | Triage   | `YYYY-MM-DD-NNN-triage`             | `docs/plans/.work/.triage/<id>.md`   |
 | Prepare  | `YYYY-MM-DD-NNN-prepare`            | `docs/plans/.work/.prepare/<id>.md`  |
@@ -35,6 +35,8 @@ The `work-id` is the key that ties all four phase artifacts together and locates
 
 > **Work branch name:** the git branch for a run is `work/<short-description>` — a kebab-case slug derived from the plan name or work description (Triage Step 2d), **not** the `work-id` itself. The Work Manifest records the `work-branch` ↔ `work-id` pairing; see `skills/work/modules/triage.md` Step 2d.
 
+> **Persistence by mode.** The "Saved to" column and the directory-listing algorithm below apply **only in `detailed` mode**. In `smart`/`autopilot` mode phase artifacts are not written, so no directory is listed: Triage/Prepare/Execute ids are `<work-id>-<phase>` (in-memory labels). Only the Work Report `review-id` is persisted, so it still counts existing files in `docs/plans/.work/.review/`. See [Artifact Persistence](interaction-mode-propagation.md#artifact-persistence).
+
 ## Algorithm (new phase artifact)
 
 ```

package/skills/work/references/interaction-mode-propagation.md

@@ -77,4 +77,24 @@ The two never override one another; the orchestrator's quality gate #2 cross-che
 | Invalid mode value          | Reject; re-prompt Orchestrator        |
 | Artifact missing mode field | Assume "smart"; log warning; continue |
 | User selects "Abort"        | Stop immediately; inform Orchestrator |
-| Timeout/connection lost     | Pause; ask user to retry or abort     |
+| Timeout/connection lost     | Pause; ask user to retry or abort     |
+
+## Artifact Persistence
+
+Phase artifacts (Triage, Prepare, Execute) are **handoff data between phases**, not deliverables. Whether they are written to disk depends on `interactionMode`:
+
+| Mode          | Phase artifacts (`docs/plans/.work/.triage/`, `.prepare/`, `.execute/`)          | Phase handoff                                  |
+| ------------- | ---------------------------------------- | ---------------------------------------------- |
+| **Detailed**  | Written to the hidden directories (audit trail; creating the directory on first use) | Artifact is written, shown, then passed on     |
+| **Smart**     | **Not written**                          | Artifact is held in context and passed in-memory to the next phase |
+| **Autopilot** | **Not written**                          | Artifact is held in context and passed in-memory to the next phase |
+
+**Always written, in every mode:** the Work Report in `docs/plans/.work/.review/<review-id>.md` (a cross-skill handoff read by `/review` and `/learn`), the task files/index in `docs/tasks/<work-id>/`, and the work branch.
+
+**Rules:**
+
+- The artifact schema, quality gates, cross-phase ID checks, and pause triggers are **unchanged** — only the disk write is skipped. Validate and pass the in-memory artifact exactly as you would the file.
+- Never create the hidden directories in `smart`/`autopilot`; no placeholder or empty files.
+- **ID allocation without files:** Triage/Prepare/Execute ids are `<work-id>-<phase>` (in-memory labels). Only the Work Report `review-id` is persisted, so it still counts existing files in `docs/plans/.work/.review/`.
+- If the user switches to `detailed` mid-run, write the artifacts produced so far, then continue writing.
+- Because nothing is on disk, **Edit & Retry** reuses the in-memory artifact and its id (no file to overwrite).

package/skills/work/references/templates/artifacts/execution-log.md

@@ -52,7 +52,7 @@ final-index-state:
   uncompleted-rows: [<task-id>, ...]       # rows still - [] (blocked/skipped)
 ```
 
-Also save the Execution Log to `docs/plans/.work/.execute/<execute-id>.md`.
+In `detailed` mode only, also save the Execution Log to `docs/plans/.work/.execute/<execute-id>.md`. In `smart`/`autopilot` mode, do not write it; pass it to the next phase in context.
 
 ## Validation Rules
 

package/skills/work/references/templates/artifacts/execution-plan.md

@@ -55,7 +55,7 @@ policy:                                  # recorded read-only from task-executio
 work-state: ready | nothing-ready         # echoes the Work Manifest if carried through
 ```
 
-Also save the Execution Plan to `docs/plans/.work/.prepare/<prepare-id>.md`.
+In `detailed` mode only, also save the Execution Plan to `docs/plans/.work/.prepare/<prepare-id>.md`. In `smart`/`autopilot` mode, do not write it; pass it to the next phase in context.
 
 ## Validation Rules
 

package/skills/work/references/templates/artifacts/work-manifest.md

@@ -56,7 +56,7 @@ dependency-warning: null | proceeded-without-upstream | expanded-to-upstream   #
 work-state: ready | nothing-ready              # nothing-ready if no task is runnable
 ```
 
-Also save the manifest to `docs/plans/.work/.triage/<triage-id>.md` for future reference or reuse.
+In `detailed` mode only, also save the manifest to `docs/plans/.work/.triage/<triage-id>.md` for future reference or reuse. In `smart`/`autopilot` mode, do not write it; pass it to the next phase in context.
 
 ## Validation Rules