@minhduydev/mdpi 0.4.1 → 0.5.0

package/dist/template/.pi/templates/loop-state.json

@@ -1,24 +0,0 @@
-{
-  "loop_name": "<loop-name>",
-  "owner": "[Owner]",
-  "cadence": "[cron expression or manual]",
-  "last_run": null,
-  "in_progress": [],
-  "completed": [],
-  "escalated": [],
-  "failures": [],
-  "lessons": [],
-  "processed": [],
-  "stop_conditions_met": [],
-  "metrics": {
-    "runs": 0,
-    "killed": false,
-    "kill_reason": null,
-    "tokens_used": 0,
-    "token_cap": null,
-    "pr_opened": 0,
-    "items_fixed": 0,
-    "items_skipped": 0,
-    "items_escalated": 0
-  }
-}

package/dist/template/.pi/templates/loop-state.md

@@ -1,98 +0,0 @@
----
-purpose: Human-readable working memory + dedup ledger mirror for one loop
-updated: <auto — last modified>
----
-
-# Loop State
-
-<!--
-  Human-readable mirror of STATE.json. The machine ledger (STATE.json) is
-  authoritative for dedup; this file is for humans reading the loop's history.
-  Keep them in sync — the orchestrator writes STATE.json; update this file when
-  you review.
--->
-
-**Loop name:** `<loop-name>`
-**Owner:** `[Owner]`
-**Cadence:** `[cron expression or "manual"]`
-
----
-
-## Last run
-
-<!-- When did the loop last execute, and what happened. -->
-
-| Field     | Value                          |
-| --------- | ------------------------------ |
-| Timestamp | `[ISO-8601 or null]`           |
-| Status    | `[pass / fail / killed / no-op]` |
-| Duration  | `[seconds]`                    |
-| Items     | `[count processed this run]`  |
-| Tokens    | `[tokens used this run]`      |
-
-## In progress
-
-<!-- Items the loop is currently working on. Empty if idle. -->
-
-| Item ID | Type | Started | Note |
-| ------- | ---- | ------- | ---- |
-| `<id>` | `[ci-run / pr / package@version / commit-sha]` | `[ISO-8601]` | `[note]` |
-
-## Completed
-
-<!-- Items the loop finished this cycle (subset of Processed items below). -->
-
-| Item ID | Type | Completed | Outcome |
-| ------- | ---- | --------- | ------- |
-| `<id>` | `[type]` | `[ISO-8601]` | `[fixed / skipped / escalated / rejected]` |
-
-## Escalated
-
-<!-- Items the loop could not handle autonomously and escalated to a human. -->
-
-| Item ID | Type | Escalated | Reason |
-| ------- | ---- | --------- | ------ |
-| `<id>` | `[type]` | `[ISO-8601]` | `[why the loop could not act]` |
-
-## Lessons learned
-
-<!-- Durable lessons from prior runs. One line each; link to STATE.json.lessons[]. -->
-
-- `[Date]` — `[Lesson text]`
-- `[Date]` — `[Lesson text]`
-
-## Processed items
-
-<!--
-  Dedup ledger. Keyed by STABLE item IDs so re-running the orchestrator on an
-  already-processed item skips it (idempotent). Stable ID forms:
-    - CI run ID           e.g. `ci:12345678901`
-    - PR number           e.g. `pr:42`
-    - package@version     e.g. `pkg:lodash@4.17.21`
-    - commit SHA          e.g. `sha:abc1234`
-  Deleting STATE.json reprocesses everything.
--->
-
-| Item ID | Type | First seen | Last status | Retries |
-| ------- | ---- | ---------- | ----------- | ------- |
-| `<stable-id>` | `[ci-run / pr / package / commit]` | `[ISO-8601]` | `[fixed / skipped / failed / escalated]` | `[n]` |
-
-## Stop conditions met
-
-<!-- Boolean flags from the VISION.md "Hard stops" list. All false = safe to run. -->
-
-| Stop condition | Met? |
-| -------------- | ---- |
-| Token budget exceeded | `[yes / no]` |
-| Protected path modified | `[yes / no]` |
-| Item already processed | `[yes / no]` |
-| `gh` not authenticated | `[yes / no]` |
-| Gate command missing/unparseable | `[yes / no]` |
-
----
-
-<!--
-  This file is a mirror. The machine ledger (STATE.json) is the source of
-  truth for dedup and idempotence. Update this file when reviewing run history;
-  the orchestrator does not need to write here.
--->

package/dist/template/.pi/templates/loop-vision.md

@@ -1,110 +0,0 @@
----
-purpose: Anti goal-drift contract for a loop — reread at the start of every run; the loop must not act outside this file
-updated: <auto — last modified>
----
-
-# Loop Vision
-
-<!--
-  This file is the immutable contract for one loop. The orchestrator (and any
-  interactive run) MUST reread this file at the start of every cycle and treat
-  its boundaries as authoritative. If context summarization drops a constraint
-  mid-run, this file restores it (boundaries are re-derived from disk, not
-  from context).
-
-  Fill the bracketed placeholders via `/loop-init <name>`, then edit by hand.
-  Never let a run edit this file during a cycle (protected path — see
-  loop-guard.ts).
--->
-
-**Loop name:** `<loop-name>`
-**Owner:** `[Owner]`
-**Cadence:** `[cron expression or "manual"]`
-**Created:** `[Date]`
-**Last revised:** `[Date]`
-
----
-
-## Goal
-
-<!-- One sentence: the outcome this loop produces, outcome-shaped not task-shaped. -->
-
-[What does this loop achieve? e.g. "Triage failing CI runs nightly and open fix PRs for deterministic failures."]
-
-## Scope
-
-<!-- What the loop is allowed to touch. Be concrete: file paths, package names, commands. -->
-
-- [Allowed action 1: e.g. edit source under `src/`]
-- [Allowed action 2: e.g. run `npm test` / `npm run lint`]
-- [Allowed action 3: e.g. open a PR on branch `loop/<name>/<ts>` — never `main`]
-
-## Out-of-scope
-
-<!-- What the loop must NEVER do, even if asked. Hard refuses. -->
-
-- [Refuse 1: e.g. auth / payments / architecture changes]
-- [Refuse 2: e.g. editing `package.json`, lockfiles, or this VISION.md / the gate script]
-- [Refuse 3: e.g. merging or deploying — human approval required]
-
-## Definition-of-done
-
-<!-- Observable, verifiable end state. Must be checkable by the Gate command (exit 0). -->
-
-- [ ] [Criterion 1: e.g. `npm test` exits 0]
-- [ ] [Criterion 2: e.g. diff is limited to in-scope paths]
-- [ ] [Criterion 3: e.g. a PR is open on `loop/<name>/<ts>` with a body citing this file]
-
-## Gate
-
-<!--
-  PARSE CONTRACT (machine-readable — do NOT edit this comment):
-    The orchestrator extracts the gate command from the SINGLE fenced
-    ```bash block located directly under the "## Gate" heading in this file.
-    Extraction rule: require EXACTLY ONE ```bash block in this section
-    (bounded by the next "## " heading). Zero or more-than-one -> refuse
-    (gate not parseable; orchestrator records failure and does NOT ship).
-    Take that single block's content, strip trailing whitespace, run it via
-    `bash -c "<command>"`, read the exit code.
-      exit 0   -> PASS  -> ship (push branch `loop/<name>/<ts>` + open PR)
-      non-zero -> FAIL  -> no ship; record failure in STATE.json; cleanup worktree
-    The gate decision is computational (exit code), never an LLM's opinion.
-    Keep EXACTLY ONE ```bash block directly under ## Gate.
--->
-
-Command (exit 0 = pass):
-
-```bash
-<GATE_COMMAND>
-```
-
-**Pass:** exit 0 → ship (push `loop/<name>/<ts>` branch + open PR via `gh`).
-**Fail:** non-zero → no ship; record failure in `STATE.json.failures[]`; cleanup worktree.
-
-## Hard stops
-
-<!-- Conditions that abort the run immediately, no matter the gate result. -->
-
-- [Hard stop 1: e.g. token budget exceeded (`STATE.json.metrics.tokens_used > cap`)]
-- [Hard stop 2: e.g. gate file / VISION.md / `package.json` modified during the run]
-- [Hard stop 3: e.g. item already in `STATE.json.processed` → idempotent skip]
-- [Hard stop 4: e.g. `gh` not authenticated → fall back to commit-only/log, do not ship]
-
-## Human-approval-required
-
-<!-- Actions the loop may stage but never execute on its own. -->
-
-- [ ] Merging a PR
-- [ ] Deploying to production
-- [ ] Changing dependencies (`package.json`, lockfiles, version bumps)
-- [ ] Modifying this VISION.md or the Gate command mid-run
-- [ ] Touching auth, payments, or architectural decisions
-
----
-
-<!--
-  Reread this file at the start of every run. The loop must not act outside
-  this file. If a proposed action is not clearly inside Scope, treat it as
-  Out-of-scope and escalate (record in STATE.json.escalated[]) instead of
-  acting.
--->