automata-cli 0.1.0-feature-033-orphan-pull-requests.280 → 0.1.0-feature-better-plugin.285

package/README.md

@@ -129,7 +129,7 @@ See [docs/execute-prompt.md](docs/execute-prompt.md) for full details.
 
 ## `automata do-work`
 
-One tick of the autonomous loop: answer the open issues whose newest message from an authorized account the agent has not answered, then do the same for the open pull requests that close no issue of this repository. Reference: [docs/do-work.md](docs/do-work.md). Process, trust model and setup: [the wiki](docs/wiki/Home.md).
+One tick of the autonomous loop: answer the open issues whose newest message from an authorized account the agent has not answered. Reference: [docs/do-work.md](docs/do-work.md). Process, trust model and setup: [the wiki](docs/wiki/Home.md).
 
 ---
 
@@ -158,7 +158,30 @@ Already cloned without `--recurse-submodules`? Fetch the vendored agent plugins
 git submodule update --init --recursive
 ```
 
-`vendor/agent-plugins-base` is registered in `.claude/settings.json` as a project-scope Claude Code marketplace, and the `github-alk` plugin is enabled from it — so its skills load for anyone working in this repository. See [docs/plugins.md](docs/plugins.md).
+`vendor/agent-plugins-base` is registered in `.claude/settings.json` as a project-scope Claude Code marketplace, so its skills load for anyone working in this repository with no further setup.
+
+#### Importing the plugin at user scope
+
+The devcontainer does this for you on creation. Run it by hand to make the skills available in **every** project rather than just this one, or to reach Codex — which keeps marketplaces in `~/.codex/config.toml` and has no project-scoped equivalent, so it needs this step even inside this repository.
+
+```bash
+# from the repository root
+PLUGIN_ROOT="$(pwd)/vendor/agent-plugins-base"
+
+# Claude Code
+claude plugin marketplace add "$PLUGIN_ROOT" --scope user
+claude plugin install github-alk@agent-plugins-base --scope user --yes
+
+# Codex
+codex plugin marketplace add "$PLUGIN_ROOT"
+codex plugin add github-alk@agent-plugins-base
+```
+
+Both clients need an **absolute** path here. Verify with `claude plugin list` (expect `Scope: user`, enabled) and `codex plugin list`.
+
+To remove them again: `claude plugin uninstall github-alk@agent-plugins-base` and `codex plugin remove github-alk@agent-plugins-base`.
+
+Full reference, including how the two scopes interact: [docs/plugins.md](docs/plugins.md).
 
 ### Scripts
 
@@ -172,7 +195,7 @@ git submodule update --init --recursive
 | `npm run audit:prod` | Audit the dependencies that ship — also runs via `prepublishOnly`, so an advisory blocks publishing |
 | `npm run audit:all` | Audit the whole tree, dev toolchain included (advisory only) |
 
-Agent plugins are vendored as a submodule and registered with Claude Code — see [docs/plugins.md](docs/plugins.md).
+Agent plugins are vendored as a submodule and registered with both Claude Code and Codex — see [docs/plugins.md](docs/plugins.md).
 
 ### Maintenance
 

package/dist/{ConfigWizard-D6NYL2E6.js → ConfigWizard-HDHKPY6J.js}

@@ -3,14 +3,13 @@ import {
   DEFAULT_CHECK_ISSUE_PROMPT,
   DEFAULT_DO_WORK,
   DEFAULT_DO_WORK_ISSUE_DISCUSS_PROMPT,
-  DEFAULT_DO_WORK_PR_ORPHAN_PROMPT,
   DEFAULT_DO_WORK_PR_WORK_PROMPT,
   DEFAULT_FIX_COMMENTS_PROMPT,
   DEFAULT_SONAR_PROMPT,
   readConfig,
   readRawConfig,
   writeConfig
-} from "./chunk-MIPBYVK5.js";
+} from "./chunk-LTCVLM4I.js";
 
 // src/config/ConfigWizard.tsx
 import { useState } from "react";
@@ -42,8 +41,7 @@ var PROMPTS_MENU_OPTIONS = [
   "Fix-Comments",
   "Check-Issue",
   "Do Work \u2014 Discuss",
-  "Do Work \u2014 PR",
-  "Do Work \u2014 Orphan PR"
+  "Do Work \u2014 PR"
 ];
 function parseAllowedUsers(value) {
   return value.split(",").map((user) => user.trim()).filter((user) => user.length > 0);
@@ -123,8 +121,7 @@ var PROMPT_SCREEN_BY_OPTION = {
   "Fix-Comments": "fix-comments-prompt",
   "Check-Issue": "check-issue-prompt",
   "Do Work \u2014 Discuss": "do-work-discuss-prompt",
-  "Do Work \u2014 PR": "do-work-pr-prompt",
-  "Do Work \u2014 Orphan PR": "do-work-pr-orphan-prompt"
+  "Do Work \u2014 PR": "do-work-pr-prompt"
 };
 function ConfigWizard() {
   const existing = readConfig();
@@ -170,9 +167,6 @@ function ConfigWizard() {
   const [doWorkPrPrompt, setDoWorkPrPrompt] = useState(
     existing.doWork?.prompts?.prWork ?? DEFAULT_DO_WORK_PR_WORK_PROMPT
   );
-  const [doWorkPrOrphanPrompt, setDoWorkPrOrphanPrompt] = useState(
-    existing.doWork?.prompts?.prOrphan ?? DEFAULT_DO_WORK_PR_ORPHAN_PROMPT
-  );
   const [pendingRemote, setPendingRemote] = useState(existing.remoteType ?? "gh");
   const [pendingTechnique, setPendingTechnique] = useState(
     existing.issueDiscoveryTechnique ?? "label"
@@ -368,17 +362,6 @@ function ConfigWizard() {
         setScreen("prompts-menu");
       },
       onBack: () => setScreen("prompts-menu")
-    },
-    "do-work-pr-orphan-prompt": {
-      setValue: setDoWorkPrOrphanPrompt,
-      onSubmit: () => {
-        savePrompt("do-work-pr-orphan.md", doWorkPrOrphanPrompt, (value, current) => ({
-          ...current,
-          doWork: { ...current.doWork, prompts: { ...current.doWork?.prompts, prOrphan: value } }
-        }));
-        setScreen("prompts-menu");
-      },
-      onBack: () => setScreen("prompts-menu")
     }
   };
   const menus = {
@@ -544,12 +527,6 @@ function ConfigWizard() {
       label: "Pull request turn instructions:",
       value: doWorkPrPrompt,
       hint: `Type prompt \xB7 Enter to save \xB7 ${BACK}`
-    },
-    "do-work-pr-orphan-prompt": {
-      title: "Prompts \u2014 Do Work \u2014 Orphan PR",
-      label: "Instructions for a pull request with no linked issue:",
-      value: doWorkPrOrphanPrompt,
-      hint: `Type prompt \xB7 Enter to save \xB7 ${BACK}`
     }
   };
   const menuViews = {

package/dist/{chunk-MIPBYVK5.js → chunk-LTCVLM4I.js}

@@ -16,7 +16,6 @@ var DEFAULT_DO_WORK = {
 };
 var DEFAULT_DO_WORK_ISSUE_DISCUSS_PROMPT = "You are the agent named in the context below, working on a GitHub issue together with the people allowed to instruct you. Answer the messages marked NEW; the earlier messages are context only.\n\nDo not modify, create or delete any file, and do not create a branch or a pull request, UNLESS a message marked NEW explicitly asks you to implement the work. If it does: create a branch off the base branch named below, implement the change following the project's existing conventions, run the tests and the linter, and open a pull request whose body contains `Closes #<issue number>`.\n\nOtherwise do not touch the code at all: reply on the issue with the specification, the plan, or the open questions you need answered. Keep the reply short and concrete.\n\nEither way, always post a reply on the issue before you finish \u2014 including when you implemented and opened a pull request. Silence is indistinguishable from a crash, and the run will be reported as having produced no answer.";
 var DEFAULT_DO_WORK_PR_WORK_PROMPT = "You are the agent named in the context below, working on the pull request for a GitHub issue together with the people allowed to instruct you. Work on the branch named below, which is already checked out and up to date.\n\nAddress every message marked NEW and every unresolved review thread listed. Follow the project's existing conventions, run the tests and the linter, then commit and push to that branch. Do not merge the pull request and do not push to the base branch.\n\nReply on the pull request with a short summary of what you changed, or reply in the review thread when your answer belongs to a specific comment. Always post a reply \u2014 silence looks like a crash.";
-var DEFAULT_DO_WORK_PR_ORPHAN_PROMPT = "You are the agent named in the context below, working on a pull request that is not linked to any issue \u2014 a dependency bump, or another change opened without one \u2014 together with the people allowed to instruct you. Work on the branch named below, which is already checked out and up to date.\n\nAddress every message marked NEW and every unresolved review thread listed. Typical work here is finding out why the checks are failing, bringing the branch up to date with the base branch, and fixing whatever the change needs in order to be mergeable. Follow the project's existing conventions, run the tests and the linter, then commit and push to that branch.\n\nDo not merge the pull request, do not close it, and do not push to the base branch. If you conclude that it should be merged or closed, say so in your reply and leave the decision to the humans.\n\nReply on the pull request with a short summary of what you did and what you recommend, or reply in the review thread when your answer belongs to a specific comment. Always post a reply \u2014 silence looks like a crash.";
 var CONFIG_DIR = ".automata";
 var CONFIG_FILE = "config.json";
 function configPath() {
@@ -82,9 +81,6 @@ function readConfig() {
   if (config.doWork?.prompts?.prWork) {
     config.doWork.prompts.prWork = resolvePromptRef(config.doWork.prompts.prWork, dir);
   }
-  if (config.doWork?.prompts?.prOrphan) {
-    config.doWork.prompts.prOrphan = resolvePromptRef(config.doWork.prompts.prOrphan, dir);
-  }
   return config;
 }
 function writeConfig(config) {
@@ -101,7 +97,6 @@ export {
   DEFAULT_DO_WORK,
   DEFAULT_DO_WORK_ISSUE_DISCUSS_PROMPT,
   DEFAULT_DO_WORK_PR_WORK_PROMPT,
-  DEFAULT_DO_WORK_PR_ORPHAN_PROMPT,
   readRawConfig,
   readConfig,
   writeConfig