@mmerterden/multi-agent-pipeline 20.34.0 → 20.35.0

package/pipeline/multi-agent-refs/phases/phase-0-init.md

@@ -526,14 +526,18 @@ scan, `shadow-git.sh` excludes, and the shared walkers (`extract-conventions.sh`
 
 **v2.1.0+ Multi-Repo Worktree Setup**:
 
-When `state.projects[].length > 1`, repeat steps 2-3 **serially per repo** (worktrees are cheap; serial keeps git index sane and surfaces collisions one at a time): one `worktree-prepare.sh` call per repo, with that repo's root, `--path "$proj/.worktrees/$BRANCH_DIR/"`, the shared branch and base, and that repo's identity.
+When `state.projects[].length > 1`, steps 2-3 run **serially per repo** in one call; `{repos.json}` is `[{project, path, branch, base, name, email}]` with `path` = `"$proj/.worktrees/$BRANCH_DIR/"`:
+
+```bash
+node "$HOME/.claude/scripts/worktree-prepare-all.mjs" --repos "{repos.json}"
+```
 
 State file in multi-repo mode:
 - Single shared `agent-state.json` lives at `${LOGS_ROOT:-$HOME/.claude/logs/multi-agent}/{first-project}/{task-id}/agent-state.json` (anchored on the first repo for back-compat with `multi-agent log`/`status` commands)
 - Every write to it, creation included, goes through `node $HOME/.claude/scripts/write-state.mjs`  -  the required mechanism in `operations.md` "Writing `agent-state.json`", and the race a per-repo read-modify-write loses `projects[]` entries to.
 - `state.projects[]` holds per-repo `{name, root, worktreePath, branch, baseBranch, identity, platform, baseFetchStatus, commit, pr, pushAttempts, buildStatus}`  -  see `agent-state.schema.json`
 - Scalar fields (`project`, `projectRoot`, `worktreePath`, `branch`, `baseBranch`, `identity`) mirror `projects[0]` so legacy phases that read scalars keep working
-- Atomicity: if any repo's worktree creation fails (collision aborted, fetch aborted, disk full), roll back already-created worktrees: `git -C $proj worktree remove --force $WT_PATH; git -C $proj branch -D $BRANCH`. Never leave a partial multi-repo state.
+- Atomicity: on exit 1 it is after rolling back what it created (worktrees are removed without `--force`; branch rules in the script header). Report `failed.error` and `kept[]`, write no `projects[]`, stop.
 
 Single-repo mode (`projects.length === 1` or scalar-only) uses the legacy single-worktree path verbatim  -  no behavior change for existing tasks.
 

package/pipeline/multi-agent-refs/phases/phase-1-plan.md

@@ -325,14 +325,12 @@ Create tasks using TaskCreate with imperative subject, description (what/which f
 
 ##### Analysis citation requirement (every UI task)
 
-Every UI-touching task in the plan MUST cite:
+Every UI-touching task cites, as its `design: {component, mapping}`, the analysis Section 6 (Bileşen Envanteri) row it implements (one task per row when one component covers several variants) and the canonical name from it:
 
-- The analysis Section 6 (Bileşen Envanteri) row it implements (one task per row when a single component covers several variants), AND
-- The canonical component name, sourced from the analysis doc:
-  - **Code Connect mapping present**: take the component name verbatim from the matching repo `*.figma.swift` / `*.figma.kt` row referenced by analysis Section 6.
-  - **Mapping absent**: cite "best-fit pending design review" and add a Risk row to the plan. The task description MUST also flag that Phase 3 will gate it as `review_blocking`.
+- **Code Connect mapping present** (`code-connect`): the name verbatim from the repo `*.figma.swift` / `*.figma.kt` row Section 6 references.
+- **Mapping absent** (`best-fit`): "best-fit pending design review", a Risk row in the plan, and a task note that Phase 3 gates it `review_blocking`.
 
-Tasks without an analysis Section 6 citation when the doc lists UI components are rejected at the plan-approval gate; the user is asked to either re-run `/multi-agent:analysis` to extend Section 6 or rescope the task to a non-UI change. Direct Figma fetches in Phase 1 are forbidden (Locked decision 30).
+`validate-planning.mjs --spec` fails a name that is not a Section 6 row, a mapping its Existing column contradicts, and a view-file task with no `design`; the user then re-runs `/multi-agent:analysis` to extend Section 6 or rescopes the task to a non-UI change. Direct Figma fetches in Phase 1 are forbidden (Locked decision 30).
 
 Example task graph:
 

package/pipeline/multi-agent-refs/phases/phase-2-dev.md

@@ -80,12 +80,13 @@ Phase 2 runs twice in the pipeline lifetime: first for initial development, then
 When re-entering from Phase 3:
 
 1. Read `state.reviewIterations[-1]`  -  the latest iteration's **accepted** list.
+   Before the first edit, record the round's base (`features/scope-check.md`, "Rework pass").
 2. For each `accepted` finding where `severity === "blocking"` or `severity === "important"`:
    - Treat it exactly like a Phase 1 plan task (TDD cycle, build verify).
    - Quote the original `issue` + `fix` text in the task description so the dev agent has full context.
 3. `accepted.suggestion` items are applied opportunistically (no TDD loop required) unless the user asked for suggestions to be treated strictly.
 4. `deferred` items are NOT actioned in this re-entry  -  Phase 4 Step 0b lists them before the commit and the PR description carries them as follow-ups.
-5. `rejected` items are never touched. Log their IDs + triage reasons for audit only.
+5. `rejected` items are never touched. Log their IDs + triage reasons for audit only; Step 3.7 checks it.
 6. After rework, increment `state.phases["2"].retryCount`; at `retryCount === 3` run `node $HOME/.claude/scripts/rework-rulings.mjs --triage "{worktreePath}/triage-output.json" --state "$STATE_FILE"`: blocking or security findings `escalate` (hard-kill, escalate to the user), the rest are `parked` as follow-ups and the run continues to Phase 4; exit 2 or 3 escalates. Do not loop indefinitely. When `prefs.global.autopilotCircuitBreaker.enabled` is true (default), record the hard-kill before escalating as `state.circuitBreaker = {tripped: true, trigger: 3, detail: "rework cycles exhausted", checkpoint: {phase: 3, step: "re-entry", iteration: <n>}, trippedAt, counters: {reworkCycles: <n>}}`: the rework-storm trigger; `autopilotCircuitBreaker.maxReworkCycles` (default 3) is bounded above by this cap.
 7. When `state.reviewIterations[-1].delta` exists, `stillPresent[]` findings come first in the task list, quoted `STILL PRESENT after round N-1's fix`; repeating the previous attempt is the loop the circuit-breaker stops.
 8. Before each rework dispatch, `rework-escalation.mjs` picks the rung; findings and the prior report go as files (`features/rework-escalation.md`).
@@ -103,16 +104,10 @@ $HOME/.claude/scripts/log-metric.sh "$TASK_ID" 2 rework.started \
 
 For each task (respecting dependency order), on start and on end: `bash $HOME/.claude/scripts/phase-tracker.sh sub 2 <task_id> "<title>" in_progress|completed|failed`.
 
-1. **Update task status: `in_progress` (required  -  do not skip or defer)**
-   - **Why**: the board shows "Todo" until this runs, and status reports and swimlanes read it.
-   - **Where it applies**:
-     - Jira: transition issue to "In Progress" via REST API (operations.md "Confirmed writes")
-     - GitHub Projects V2: `updateProjectV2ItemFieldValue` on the Status field (singleSelectOptionId)
-     - Internal state: `agent-state.json` → `phases["2"].status = "in_progress"`
-   - **Post-update verify** (catches silent VALIDATION errors from stale option IDs after board rebuilds):
-     - Re-read the Status field after mutation.
-     - If the value is NOT `In Progress` (Jira) / `In Develop` (Projects V2), re-fetch current option IDs and retry ONCE.
-     - If verify still fails after retry → log error, do NOT proceed to TDD. The mutation silently failed and continuing would leave the task mis-tracked.
+1. **Update task status: `in_progress` (required, before any code)**: the board shows "Todo" until this runs.
+   - Jira: transition to "In Progress" via REST (operations.md "Confirmed writes"); Projects V2: `updateProjectV2ItemFieldValue` on Status; state: `phases["2"].status = "in_progress"`.
+   - **Verify**: re-read Status. Not `In Progress` / `In Develop` (stale option ids after a board rebuild) → re-fetch the ids, retry once; still wrong → log it and do NOT start TDD.
+   - **Record** `phases["2"].trackerStatus` (`agent-state.schema.json`); write-state will not leave Phase 2 of an attended tracked run while it is missing or `failed`.
 2. **Multi-submodule awareness**: a task may span the submodules Phase 0 Step 7 detected (e.g. tokens in **common**, the component in **uicomponents**); that is expected.
 3. **TDD cycle** (Launch Agent with `model: "sonnet"`)  -  gated by `state.testPolicy`: `tdd` = the loop below; `tests-after` = skip RED, author the same tests once green; `none` = author no tests (existing ones never weakened), report "tests not written - project policy" rather than a gap.
 
@@ -156,7 +151,7 @@ For each task (respecting dependency order), on start and on end: `bash $HOME/.c
    **REFACTOR (if needed):**
    - Only if duplication or naming is poor
    - Re-run tests after refactor → still GREEN
-   - **Stability (required):** run every test added or changed in this diff `prefs.global.testStability.repeatCount` times (default 3; 1 disables) with the single-test invocation above. Disagreeing outcomes are not GREEN: log `test.flake_signal file=<f> passed=<k> of=<N>` and fix the test or the code first. Same rule on the Phase 3 rework re-entry. Keep each repeat's `.pipeline/repeat-<k>.junit.xml`.
+   - **Stability (required):** run every test added or changed in this diff `prefs.global.testStability.repeatCount` times (default 3; 1 disables) with the single-test invocation above. Disagreeing outcomes are not GREEN: log `test.flake_signal file=<f> passed=<k> of=<N>` and fix the test or the code first. Same rule on the Phase 3 rework re-entry. Keep each repeat's `.pipeline/repeat-<k>.junit.xml` and judge them with `test-stability-gate.mjs` (`features/verify-by-test.md`, "Repeat runs").
 
    **Target resolution** (auto-detect once per project, cache in `agent-state.json`; ios resolves scheme + simulator, android resolves module + variant, backend/web need none):
    ios (prefer the scheme matching the project name, then the first non-test scheme):
@@ -276,6 +271,8 @@ git -C "$WORKTREE" diff --name-only "origin/$BASE_BRANCH"...HEAD \
       --repo "$WORKTREE" --patch-range "origin/$BASE_BRANCH...HEAD"
 ```
 
+On a re-entry from Phase 3, also run the rejected-findings check (`features/scope-check.md`, "Rework pass").
+
 Exit 1 lists `unjustified[]`: complete the record, re-run once. A second exit 1 logs `dev.scope_check=incomplete unjustified=<n>` and hands off; reviewers see it in `<scope-self-check>`. Progress line: `    → checking scope self-check ({n} files, {m} not done)`.
 
 ---

package/pipeline/multi-agent-refs/phases/phase-3-review.md

@@ -364,9 +364,9 @@ Exit 0 = valid. Exit 2 = contradiction (approved=true with blocking findings)  -
 
 **CRITICAL**: Reviewer findings are **raw signals**, not commands. Never auto-loop on every "blocking" tag  -  reviewers hallucinate, misread scope, or repeat each other. Run Fable triage (Opus on Copilot CLI) to evaluate merged findings against task scope.
 
-Optional: when `ai-analyst-toolkit` is enabled and a finding blames a third-party library rather than this diff, ask `evidence-github` whether it is already open upstream. A confirmed one is `deferred` with its `GitHub:<owner>/<repo>#<n>` citation, not `accepted` and handed to Phase 2 to fix code that is not ours.
+Optional: with `ai-analyst-toolkit` enabled, a finding that blames a third-party library goes to `evidence-github` to check whether it is open upstream. A confirmed one is `deferred` with its `GitHub:<owner>/<repo>#<n>` citation, never accepted for Phase 2 to fix code that is not ours.
 
-Opt-in empirical layer: when `prefs.global.verifyByTest.enabled` is `true`, accepted blocking findings additionally go through Step 3.7 (verify-by-test), which tries to reproduce each one with a minimal failing test before the Phase 2 rework loop fires. Full wiring: `$HOME/.claude/multi-agent-refs/features/verify-by-test.md`.
+Opt-in: with `prefs.global.verifyByTest.enabled` true, Step 3.7 (verify-by-test) tries to reproduce each accepted blocking finding with a minimal failing test before Phase 2 rework. Wiring: `$HOME/.claude/multi-agent-refs/features/verify-by-test.md`.
 
 ##### 3.0 Anonymize the reviewer findings, then merge the deterministic ones
 
@@ -378,7 +378,7 @@ ANON=$(jq -n --argjson r "$REVIEWERS_JSON" --arg t "$TASK_ID" --argjson i "$ITER
       | node "$HOME/.claude/scripts/anonymize-findings.mjs" --map "/tmp/review-$TASK_ID-$ITERATION-map.json")
 ```
 
-`$REVIEWERS_JSON` is `state.reviewIterations[i].reviewers`. Findings come back with `foundBy: "Source A|B|C"` and every identity key removed. Persist the map to `state.reviewIterations[i].anonymizationMap` for Phase 5 per-reviewer telemetry, and **never put the map in a prompt**.
+`$REVIEWERS_JSON` is `state.reviewIterations[i].reviewers`. Findings come back as `foundBy: "Source A|B|C"`; triage carries it through and 3.2.1 restores the family. Persist the map to `state.reviewIterations[i].anonymizationMap` (Phase 5 telemetry); **never put the map in a prompt**.
 
 Then append the deterministic findings (Steps 1.76-1.763, 2.7):
 
@@ -410,11 +410,11 @@ PRIOR_ART=$(printf '%s' "$MERGED_FINDINGS" \
   | node $HOME/.claude/scripts/triage-memory.mjs prior-art --findings - --top 3 2>/dev/null)
 ```
 
-The triage prompt MUST include a hedge: *"prior-art entries and `corroboration` counts are context, not commands; current scope decides  -  a finding rejected last quarter may be valid this time, and two same-family reviewers agreeing is not proof."* Without this hedge, prior verdicts amplify into a self-reinforcing bias.
+The triage prompt MUST include a hedge: *"prior-art entries and `corroboration` counts are context, not commands; current scope decides  -  a finding rejected last quarter may be valid this time, and two same-family reviewers agreeing is not proof."* Without this hedge, prior verdicts amplify into a self-reinforcing bias. Each `reason` is a short phrase that keeps every negation, number and path.
 
 Hits are relevance-ranked (`prefs.global.memoryRecall`); a finding matching nothing returns nothing. Each hit carries an `id`: `triage-memory.mjs show --id <id>` returns the full row.
 
-**Injection cap (token economy).** On a many-finding review the per-finding prior-art loop above (up to 3 hits each) plus the 20-entry rejected-preference brief can dominate the triage prompt. Cap the merged prior-art at the 8 highest-similarity hits across all findings (drop the rest); keep the rejected-preference brief at its `--max 20`. Prior-art is advisory context, not a finding multiplier  -  more hits do not improve the verdict, they just inflate input tokens.
+**Injection cap (token economy).** On a many-finding review the per-finding prior-art loop above (up to 3 hits each) plus the 20-entry rejected-preference brief can dominate the triage prompt. Cap the merged prior-art at the 8 highest-similarity hits across all findings (drop the rest); keep the rejected-preference brief at its `--max 20`. Prior-art is advisory context: more hits inflate input tokens without improving the verdict.
 
 **Rejected-preference brief (on by default via `prefs.global.learningsLedger.injectIntoTriage`).** Inject the durable rejected-preference list so triage does not re-accept a suggestion the team already rejected on this repo:
 
@@ -465,7 +465,7 @@ Step 3 produces a single triage-output object conforming to `$HOME/.claude/schem
 
 Return ONLY valid JSON conforming to $HOME/.claude/schemas/triage-output.schema.json:
 {
-  "accepted":  [{ "severity": "blocking|important|suggestion", "file": "...", "line": N, "issue": "...", "fix": "...", "reviewer": "fable|opus|sonnet|gpt" }],
+  "accepted":  [{ "severity": "blocking|important|suggestion", "file": "...", "line": N, "issue": "...", "fix": "...", "foundBy": "Source A" }],
   "deferred":  [{ "finding": {...}, "reason": "..." }],
   "rejected":  [{ "finding": {...}, "reason": "..." }],
   "cannotVerify": [{ "requirement": "...", "resolution": "verified|finding|out-of-scope", "evidence": "file:line or reason" }],  // one per reviewer row, omit when none
@@ -481,7 +481,8 @@ Run on the persisted file immediately after the triage agent returns, before act
 Write it with the Write tool to `$TRIAGE_FILE` = `$WORKTREE/.pipeline/triage-round-<N>.json` (N = `jq '.reviewIterations | length' "$STATE_FILE"`), then:
 
 ```bash
-node $HOME/.claude/scripts/validate-triage.mjs "$TRIAGE_FILE" --reviewers-dir "$WORKTREE/.pipeline" \
+node $HOME/.claude/scripts/validate-triage.mjs "$TRIAGE_FILE" --reviewers-dir "$WORKTREE/.pipeline" --anonymized \
+  && node $HOME/.claude/scripts/anonymize-findings.mjs --restore --map "/tmp/review-$TASK_ID-$ITERATION-map.json" --state "$STATE_FILE" --in-place "$TRIAGE_FILE" \
   && node $HOME/.claude/scripts/finding-fingerprint.mjs annotate --in-place "$TRIAGE_FILE" \
   && cp "$TRIAGE_FILE" "{worktreePath}/triage-output.json"
 ```
@@ -490,7 +491,7 @@ Progress line: `    → checking validator validate-triage`
 
 An unsettled reviewer `cannotVerify[]` row is exit 1.
 
-One file per round; `triage-output.json` is the latest copy every downstream reader expects (Phase 5, finalize, work-summary, diff-explain). Step 3.7 rewrites `$TRIAGE_FILE`; repeat the `cp` after it.
+One file per round; `triage-output.json` is the latest copy every reader expects. Step 3.7 rewrites `$TRIAGE_FILE`; repeat the `cp` after it.
 
 | Exit  | Meaning                      | Action                                            |
 | ----- | ---------------------------- | ------------------------------------------------- |

package/pipeline/multi-agent-refs/phases/phase-4-commit.md

@@ -103,10 +103,7 @@ Branch **deterministically**, no implicit fallback. Read `agent-state.json` and
      - option 2  -  semantically "Yes, WIP checkout"; description: pause so the user can checkout the branch locally and poke around
    - Default: option 1 (by index, not by label  -  the label is localized)
    - If the user picks option 2 (WIP checkout): follow Phase 3 Steps 2-6. On `"fix:"` → Phase 2. On `"ok"` → resume Phase 4.
-2. Commit confirm prompt (skip in autopilot). Same language matrix:
-   - `question` in `outputLanguage` (semantic: "Commit now?")
-   - labels in `outputLanguage`, semantically "Commit" and "Pause and resume later"; branch on the option index, not on the rendered string
-   - No → Pause, user can `resume` later. Yes → continue:
+2. Commit confirm prompt (skip in autopilot), in `outputLanguage`: "Commit now?" with "Commit" / "Pause and resume later", branched on the option index. No → pause (`resume` later). Yes → continue; where prompts are off, record it with `confirm-command.mjs --command '<the exact commit>'` (agent-guard asks on the run's commit).
 3. If WIP commit exists from Phase 3 or Step 1: `git reset HEAD~1` to unstage, then re-commit properly
 4. Stage changes: `git add` with specific files (NOT `git add -A`  -  avoid sensitive files, `.worktrees/`, agent files)
 5. **Multi-submodule check**: If project has submodules (e.g. uicomponents + common):

package/pipeline/multi-agent-refs/rules.md

@@ -84,6 +84,7 @@ This is the single source of truth. When a contributor or model is unsure where
 - **Types**: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`, `style`, `perf`
 - **Max first-line length**: 72 chars
 - **Body** for "why", not "what"
+- **Enforced** on Claude Code inside the run the session drives: agent-guard refuses a subject with no conventional type (after a repo profile's ticket prefix) or over 72 characters, and a PR, issue or Jira body with a literal `\n` or an HTML entity outside code.
 - **Git author**: identity selected in Phase 0, from preferences file (not Keychain, not git global config)
 
 ## Branch Naming
@@ -188,9 +189,9 @@ Same rule applies to any future provider wrapper (e.g. `cloudflare-deploy.sh`, `
 
 These rules govern when and how the pipeline asks the user, and when it must NOT ask.
 
-- **No auto-commit.** Never run `git commit` without explicit user approval, even when build + review pass. The Phase 4 commit step pauses and asks ("commit message X, OK?"); only on `yes` does the commit run. Applies to checkpoint / WIP commits during Dev (Phase 3) and to the orchestrator's own state-save commits.
+- **No auto-commit.** Never run `git commit` without explicit user approval, even when build + review pass. The Phase 4 commit step pauses and asks ("commit message X, OK?"); only on `yes` does the commit run. Applies to checkpoint / WIP commits during Dev (Phase 3) and to the orchestrator's own state-save commits. Enforced on Claude Code: agent-guard asks on a `git commit` from the session driving an attended run, and pre-commit-check refuses it without the run's build, test and (from Phase 4) review evidence.
 - **No micro-confirmations for reversible local work.** Local edits, lint fixes, test additions, scaffold files, in-worktree rewrites  -  just do them. Ask only for irreversible or shared-state actions: `git push`, `git push --force`, tag, third-party POST (Confluence, Jira, Slack), publish, deletes spanning many files, branch deletion. The threshold is "can the user undo this in 30 seconds via Cmd+Z or `git restore`?"  -  if yes, do not ask.
-- **Empty `AskUserQuestion` answer is not consent.** When the user submits without picking any option (empty answers map), do NOT silently apply the "Recommended" default. Re-ask the question, or proceed treating each item as unselected. Future-behavior preference questions are not preemptive  -  only ask when the answer changes what happens NOW.
+- **Empty `AskUserQuestion` answer is not consent.** When the user submits without picking any option (empty answers map), do NOT silently apply the "Recommended" default. Re-ask the question, or proceed treating each item as unselected. On Claude Code the `answer-check.sh` PostToolUse hook names each unanswered question back to the model. Future-behavior preference questions are not preemptive  -  only ask when the answer changes what happens NOW.
 - **Question phrasing in Plan Mode.** Don't reference "the plan" in `AskUserQuestion` text while in plan mode  -  the user cannot see the plan until `ExitPlanMode`. Use `ExitPlanMode` for approval; `AskUserQuestion` only for choosing between concrete options.
 
 ## Figma Access Tier (pipeline-wide, BLOCKING)

package/pipeline/multi-agent-refs/tracker-contract.md

@@ -120,7 +120,7 @@ For each `TaskCreate` line `phase-tracker.sh tiles` prints, IN THAT ORDER:
 
 **The subject is the tracker's line, verbatim.** `phase-tracker.sh tiles` prints each subject from the phase names the command registered (`0:Init 1:Plan 2:Dev 3:Review 4:Commit 5:Report` for a full run). Copy it as printed: no task-id prefix, no renamed, merged or annotated phase (`Analysis + Plan`, `Review + Verify`). What a phase does inside goes in `activeForm` or a sub-step tile, never in the phase name. A tile that disagrees with the tracker is a second, wrong progress record.
 
-The `tasklist_id` meta field is persisted so that `:resume` can rebuild the TaskList from the state file in a fresh session.
+The `tasklist_id` meta field is persisted so that `:resume` can rebuild the TaskList from the state file in a fresh session. On Claude Code the `task-mirror.sh` PostToolUse hook records it from every phase tile's TaskCreate result, replacing an id an earlier session left (so a resume's new ids land too), and tells the model when a tile is created after a higher-numbered phase's tile in the same session. The explicit `meta` call stays in the pattern: it is what the other hosts have, and on Claude Code it writes the same value.
 
 #### The card is not the widget
 

package/pipeline/office/NOTICE.md

@@ -7,7 +7,10 @@ character sheets, the floor and wall tiles and the furniture, kept unchanged
 in `assets/`. The company furniture (kitchen, restroom, server room, archive,
 reception, lab and mail room pieces) is this project's own drawing: its
 sources are the pixel grids in `pipeline/office-art`, which the build renders
-into `assets/` with the pixel-agents palette. pixel-agents'
+into `assets/` with the pixel-agents palette. The employees' sheets
+(`assets/char_12.png` and up) are those six character sheets recoloured
+by the build, one person per sheet, from the colours in
+`pipeline/office-art/employees.json`; no pixel is drawn anew. pixel-agents'
 characters are based on JIK-A-4's MetroCity free top-down character pack
 (https://jik-a-4.itch.io/metrocity-free-topdown-character-pack), released
 under CC0 1.0.