npm - @plot-ai/darwin-arm64 - Versions diffs - 0.0.4 → 0.0.5 - Mend

@plot-ai/darwin-arm64 0.0.4 → 0.0.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (17) hide show

package/bin/CHANGELOG.md +1 -1
package/bin/package.json +1 -1
package/bin/plot-ai +0 -0
package/bin/tui-worker.js +58920 -66616
package/package.json +1 -1
package/pi-resources/skills/{core/plot-land → plot-land}/SKILL.md +1 -0
package/pi-resources/skills/{core/plot-push-pr → plot-push-pr}/SKILL.md +1 -0
package/web-dist/assets/index-BwUv4RrM.css +1 -0
package/web-dist/assets/index-pqfrb_rb.js +35 -0
package/web-dist/index.html +24 -24
package/bin/tracker/beads/skills/plot-beads-tracker/SKILL.md +0 -241
package/bin/tracker/github/skills/plot-github-tracker/SKILL.md +0 -162
package/web-dist/assets/index-BID9mjlA.css +0 -1
package/web-dist/assets/index-DyndTLrM.js +0 -40
/package/pi-resources/skills/{core/plot-commit → plot-commit}/SKILL.md +0 -0
/package/pi-resources/skills/{core/plot-debug → plot-debug}/SKILL.md +0 -0
/package/pi-resources/skills/{core/plot-pull-main → plot-pull-main}/SKILL.md +0 -0

package/web-dist/index.html CHANGED Viewed

@@ -1,27 +1,27 @@
 <!doctype html>
 <html lang="en">
-  <head>
-    <meta charset="utf-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <title>plot</title>
-    <script>
-      if (window.matchMedia("(prefers-color-scheme: dark)").matches) {
-        document.documentElement.classList.add("dark");
-      }
-      window.matchMedia("(prefers-color-scheme: dark)").addEventListener("change", (e) => {
-        document.documentElement.classList.toggle("dark", e.matches);
-      });
-    </script>
-    <link rel="preconnect" href="https://fonts.googleapis.com" />
-    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
-    <link
-      href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500&display=swap"
-      rel="stylesheet"
-    />
-    <script type="module" crossorigin src="/assets/index-DyndTLrM.js"></script>
-    <link rel="stylesheet" crossorigin href="/assets/index-BID9mjlA.css">
-  </head>
-  <body class="min-h-screen bg-background text-foreground antialiased">
-    <div id="root"></div>
-  </body>
+	<head>
+		<meta charset="utf-8" />
+		<meta name="viewport" content="width=device-width, initial-scale=1" />
+		<title>plot</title>
+		<script>
+			if (window.matchMedia("(prefers-color-scheme: dark)").matches) {
+				document.documentElement.classList.add("dark");
+			}
+			window.matchMedia("(prefers-color-scheme: dark)").addEventListener("change", (e) => {
+				document.documentElement.classList.toggle("dark", e.matches);
+			});
+		</script>
+		<link rel="preconnect" href="https://fonts.googleapis.com" />
+		<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
+		<link
+			href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500&display=swap"
+			rel="stylesheet"
+		/>
+		<script type="module" crossorigin src="/assets/index-pqfrb_rb.js"></script>
+		<link rel="stylesheet" crossorigin href="/assets/index-BwUv4RrM.css">
+	</head>
+	<body class="min-h-screen bg-background text-foreground antialiased">
+		<div id="root"></div>
+	</body>
 </html>

package/bin/tracker/beads/skills/plot-beads-tracker/SKILL.md DELETED Viewed

@@ -1,241 +0,0 @@
----
-name: plot-beads-tracker
-description: "beads issue state management for plot orchestration. hybrid model: native beads status for primary lifecycle, labels for orchestrator sub-states (rework, merging). workpad comment lifecycle and bd queries. use when moving issues between states, creating/updating workpad comments, or querying issue status."
----
-# plot-beads-tracker
-manages issue state and progress tracking for the plot orchestrator via beads status, labels, and comments.
-use `bd` for all tracker operations. the git/PR lifecycle uses `gh` separately.
-## state model
-beads uses a hybrid state model with two layers:
-- **status** (native beads lifecycle): `open`, `in_progress`, `blocked`, `deferred`, `closed`
-- **labels** (orchestrator sub-states): `plot:rework`, `plot:merging`
-the orchestrator checks labels first. if a configured label exists on the issue, it becomes the routing state. otherwise the native beads status is the state.
-```
-                  ┌─────────┐
-                  │  open    │  agent picks up, starts work
-                  └────┬────┘
-                       │ bd update <id> --status in_progress
-                       ▼
-                ┌─────────────┐
-                │ in_progress  │  agent implements, pushes PR
-                └──────┬──────┘
-                       │ bd update <id> --status blocked
-                       ▼
-                  ┌─────────┐
-                  │ blocked  │  human reviews PR
-                  └────┬────┘
-                       │
-            ┌──────────┼──────────┐
-            ▼          ▼          ▼
-     ┌────────────┐  ┌─────────────────┐  ┌────────┐
-     │plot:rework │  │  plot:merging    │  │closed  │
-     │(label)     │  │  (label)        │  │(reject)│
-     └─────┬──────┘  └───────┬─────────┘  └────────┘
-           │                 │
-           │ agent fixes,    │ agent merges PR,
-           │ removes label,  │ removes label,
-           │ → blocked       │ closes issue
-           │                 │
-           ▼                 ▼
-      ┌─────────┐      ┌────────┐
-      │ blocked  │      │ closed │
-      └─────────┘      └────────┘
-```
-## state transitions
-```bash
-# open → in_progress (starting work)
-bd update <id> --status in_progress
-# in_progress → blocked (PR ready for review)
-bd update <id> --status blocked
-# human approves → add merging label (human does this)
-bd label add <id> plot:merging
-# human requests changes → add rework label (human does this)
-bd label add <id> plot:rework
-# plot:rework → blocked (rework complete, remove label first)
-bd label remove <id> plot:rework
-bd update <id> --status blocked
-# plot:merging → closed (PR merged, remove label first)
-bd label remove <id> plot:merging
-bd close <id> -r "completed"
-# reopen closed → in_progress
-bd reopen <id> -r "needs rework"
-```
-## available states
-| source | state          | meaning                     | agent action                                          |
-| ------ | -------------- | --------------------------- | ----------------------------------------------------- |
-| status | `open`         | queued for work             | move to `in_progress`, start implementation           |
-| status | `in_progress`  | implementation underway     | continue implementation, push PR, move to `blocked`   |
-| status | `blocked`      | waiting on human review     | do nothing, wait                                      |
-| status | `deferred`     | intentionally postponed     | do nothing, wait                                      |
-| label  | `plot:rework`  | reviewer requested changes  | address feedback, remove label, move to `blocked`     |
-| label  | `plot:merging` | human approved PR           | merge PR, remove label, close issue                   |
-| status | `closed`       | terminal                    | stop                                                  |
-workflow routing:
-- dispatch_states: `open`, `in_progress`, `plot:rework`, `plot:merging`
-- parked_states: `blocked`, `deferred`
-- terminal_states: `closed`
-## workpad comment
-a persistent beads comment used as a living scratchpad across agent sessions.
-### find current workpad
-comments are append-only. there is no edit-in-place. the current workpad is the latest comment whose body starts with `## Plot Workpad`.
-```bash
-bd comments <id> --json
-```
-scan the returned comments and pick the latest one starting with `## Plot Workpad`.
-if none exists, create one.
-### create workpad
-write the full workpad body to a temp file, then add it as a comment:
-````bash
-cat > /tmp/workpad.md <<'WORKPAD'
-## Plot Workpad
-```text
-<workspace-id>@<short-sha>
-```
-### Plan
-- [ ] 1. <task>
-### Acceptance Criteria
-- [ ] <criterion>
-### Validation
-- [ ] targeted tests: `<command>`
-### Latest Attempt Summary
-- changed: <files or none>
-- validated: <commands + outcome>
-- failed: <remaining failure or none>
-- blocked: <blocker or none>
-### Notes
-- <durable context>
-WORKPAD
-bd comments add <id> -f /tmp/workpad.md
-````
-### update workpad
-do not try to edit an old comment. add a new full workpad comment with the complete updated body.
-````bash
-cat > /tmp/workpad.md <<'WORKPAD'
-...full updated workpad body...
-WORKPAD
-bd comments add <id> -f /tmp/workpad.md
-````
-### rules
-- treat the latest `## Plot Workpad` comment as canonical
-- never rely on older workpad comments once a newer one exists
-- update the workpad after every meaningful milestone
-- never leave completed items unchecked
-- include workspace id and short sha at top: `<workspace-id>@<short-sha>`
-- keep the full workpad body in each update so the latest comment is self-contained
-## workpad template
-````markdown
-## Plot Workpad
-```text
-<workspace-id>@<short-sha>
-```
-### Plan
-- [ ] 1. Parent task
-  - [ ] 1.1 Child task
-- [ ] 2. Parent task
-### Acceptance Criteria
-- [ ] Criterion 1
-- [ ] Criterion 2
-### Validation
-- [ ] targeted tests: `<command>`
-### Latest Attempt Summary
-- changed: <files or none>
-- validated: <commands + outcome>
-- failed: <remaining failure or none>
-- blocked: <blocker or none>
-### Notes
-- <short durable context>
-````
-## issue queries
-```bash
-# full issue details
-bd show <id> --json
-# all comments (for workpad lookup)
-bd comments <id> --json
-# list by status
-bd list --status open --json
-bd list --status in_progress --json
-bd list --status blocked --json
-# list by label
-bd list --label plot:rework --json
-bd list --label plot:merging --json
-# ready work: open + no blockers
-bd ready --json
-# complex filters
-bd query "status=open AND priority<=1" --json
-bd query "label=plot:rework" --json
-# text search
-bd search "keyword" --json
-# dependencies
-bd dep list <id>
-```
-## out-of-scope issue creation
-if you discover unrelated work, file a separate beads issue instead of expanding scope:
-```bash
-bd create "discovered: <title>" -t task -p 2 -d "<description>"
-```
-keep the new issue narrow and factual. reference the triggering issue in the description when useful.

package/bin/tracker/github/skills/plot-github-tracker/SKILL.md DELETED Viewed

@@ -1,162 +0,0 @@
----
-name: plot-github-tracker
-description: "github issue state management for plot orchestration. state transitions via labels, workpad comment lifecycle, and issue/PR linkage. use when moving issues between states, creating/updating workpad comments, or linking PRs to issues."
----
-# plot-github-tracker
-manages issue state and progress tracking for the plot orchestrator via GitHub labels and comments.
-use `gh` CLI for all GitHub operations. `$GITHUB_REPO` must be set to `owner/repo`.
-## state transitions
-issue state is determined by labels. plot only routes issues that have an explicit `plot:*` state label. unlabeled issues are ignored.
-transition by removing the previous `plot:*` label and adding the new one:
-```bash
-# todo -> in-progress
-gh issue edit <number>   --repo "$GITHUB_REPO"   --remove-label "plot:todo"   --add-label "plot:in-progress"
-# in-progress -> human-review
-gh issue edit <number>   --repo "$GITHUB_REPO"   --remove-label "plot:in-progress"   --add-label "plot:human-review"
-# rework -> human-review
-gh issue edit <number>   --repo "$GITHUB_REPO"   --remove-label "plot:rework"   --add-label "plot:human-review"
-# merging -> done, then close
-gh issue edit <number>   --repo "$GITHUB_REPO"   --remove-label "plot:merging"   --add-label "plot:done"
-gh issue close <number> --repo "$GITHUB_REPO"
-```
-if you need to move a terminal issue back into active work, reopen first, then swap labels:
-```bash
-gh issue reopen <number> --repo "$GITHUB_REPO"
-gh issue edit <number>   --repo "$GITHUB_REPO"   --remove-label "plot:done"   --add-label "plot:rework"
-```
-## available states
-| label             | meaning                    | agent action                                           |
-| ----------------- | -------------------------- | ------------------------------------------------------ |
-| plot:todo         | queued for work            | move to plot:in-progress, start execution              |
-| plot:in-progress  | implementation underway    | implement, verify, open PR, move to plot:human-review |
-| plot:human-review | PR open, waiting on human  | do nothing, wait                                       |
-| plot:rework       | reviewer requested changes | read feedback, fix, move to plot:human-review         |
-| plot:merging      | human approved             | merge PR, move to plot:done                           |
-| plot:done         | terminal                   | stop                                                   |
-## workpad comment
-a single persistent GitHub issue comment used as a living scratchpad across agent sessions.
-### find or create
-```bash
-# search for existing workpad
-gh api repos/$GITHUB_REPO/issues/<number>/comments --jq '.[] | select(.body | startswith("## Plot Workpad")) | .id' | head -1
-```
-if not found, create it:
-```bash
-gh api repos/$GITHUB_REPO/issues/<number>/comments   -X POST   -f body='## Plot Workpad
-### Plan
-- [ ] 1. <task>
-### Acceptance Criteria
-- [ ] <criterion>
-### Validation
-- [ ] <test command>
-### Latest Attempt Summary
-- changed: <files or none>
-- validated: <commands + outcome>
-- failed: <remaining failure or none>
-- blocked: <blocker or none>
-### Notes
-- <durable context>'
-```
-### update existing
-replace the full workpad body in place:
-```bash
-gh api repos/$GITHUB_REPO/issues/comments/<id>   -X PATCH   -f body='...full updated workpad body...'
-```
-### rules
-- exactly one workpad comment per issue, identified by `## Plot Workpad` header
-- reuse existing comment on continuation runs — do not create duplicates
-- update the workpad after every meaningful milestone
-- never leave completed items unchecked
-- include workspace id and short sha at top: `<workspace-id>@<short-sha>`
-## workpad template
-````markdown
-## Plot Workpad
-```text
-<workspace-id>@<short-sha>
-```
-### Plan
-- [ ] 1. Parent task
-  - [ ] 1.1 Child task
-- [ ] 2. Parent task
-### Acceptance Criteria
-- [ ] Criterion 1
-- [ ] Criterion 2
-### Validation
-- [ ] targeted tests: `<command>`
-### Latest Attempt Summary
-- changed: <files or none>
-- validated: <commands + outcome>
-- failed: <remaining failure or none>
-- blocked: <blocker or none>
-### Notes
-- <short durable context>
-````
-## issue queries
-```bash
-# view issue details
-gh issue view <number> --repo "$GITHUB_REPO" --json title,body,state,labels,comments
-# list open issues by label
-gh issue list --repo "$GITHUB_REPO" --label "plot:in-progress" --state open
-```
-## PR linkage
-after creating or updating a PR, ensure the PR body includes `Resolves #<number>`. that is the durable issue/PR link.
-if you need to post the PR URL back to the issue, add a normal issue comment:
-```bash
-gh api repos/$GITHUB_REPO/issues/<number>/comments   -X POST   -f body='linked PR: <pr-url>'
-```