@lawaty/lacode 0.4.0 → 0.4.2

package/dist/agents.js

@@ -30,6 +30,7 @@ var ORPHAN_TMP_MS = 60 * 1e3;
 var CATALOG_TTL_MS = 10 * 60 * 1e3;
 var STUCK_MIN_AGE_MS = 5 * 60 * 1e3;
 var STUCK_IDLE_MS = 3 * 60 * 1e3;
+var MAX_CLAIM_AGE_MS = 30 * 60 * 1e3;
 var HANG_COOLDOWN_MS = 10 * 60 * 1e3;
 var UNAVAILABLE_COOLDOWN_MS = 60 * 1e3;
 var MAX_SLOTS = 4;
@@ -73,15 +74,9 @@ Every question of the form "what does this file do", "where is X handled", or
   that proves it. Never one whole refactor handed over in a single piece \u2014
   see \`# Task size\` below.
 
-The agents you spawn are the pooled \`explore\` / \`implement\` / \`context\`
-bases. **Always spawn the BARE base name and let the plugin choose the slot;
-never name a \`-N\` variant** (\`explore-1\`..\`explore-4\`, \`implement-1\`..,
-\`context-1\`..). The plugin owns which model every pooled spawn runs on: it
-picks the next slot from the pool's weights, current load and cooldowns, and
-rewrites your spawn to that variant for you. Naming a variant bypasses that
-decision, defeats failover, and can pin work to a cooling or unhealthy model.
-If you catch yourself choosing a slot number, you are doing the plugin's job \u2014
-spawn \`explore\` and let it decide.
+Spawn the BARE pooled base \u2014 \`explore\`, \`implement\` or \`context\`. The pool
+refuses a \`-N\` variant, and a refusal means spawn the bare base, never a
+different number.
 
 # When the pool is unavailable
 
@@ -201,10 +196,8 @@ When you need to understand the codebase:
 2. Invoke @explore with specific, focused instructions (e.g. "read src/auth.ts", "grep for 'migration' in *.py files", "list the src/ directory")
 3. @explore will return its findings \u2014 you process them and plan accordingly
 
-Always spawn the BARE pooled base (\`explore\`, \`implement\`, \`context\`) and let
-the plugin choose the slot. Never name a \`-N\` variant (\`explore-1\`..\`explore-4\`);
-doing so bypasses the pool's weights, load and cooldowns, which is the one thing
-the plugin exists to decide.
+Spawn the BARE pooled base (\`explore\`, \`implement\`, \`context\`); the pool
+refuses \`-N\` variants, and a refusal means spawn the bare base, not another number.
 
 If the pool cannot serve a spawn \u2014 every slot cooling or exhausted, or repeated
 failures \u2014 do NOT fall back to reading or planning from your own inspection.
@@ -462,6 +455,30 @@ You own exactly these five files and nothing else:
   during work that are not already recorded in the project's own decision
   log. Concise; variable length.
 
+A sixth file sits in the same directory and is not yours:
+\`.opencode/context/manager.md\`. It is the client's own statement of intent
+\u2014 what is being worked on, what comes next, what they have settled, and
+what every agent should keep in mind. It deliberately says nothing about
+where code lives: your five files and the source itself are the only
+authority on that, and this file never contradicts them. It has no fixed
+schema \u2014 read the whole file, because every heading in it is direction.
+
+You never create, edit, rename, or delete it \u2014 not at bootstrap, not in an
+update, not in a review, and not when a run of your own concludes the work
+has moved on. The client edits it, or asks a live agent to edit it on
+their explicit instruction. Either way it is their hand, never yours.
+
+Read it before you write anything. Its \`## Current\` and \`## Next\`
+sections tell you what is actually being worked on, and \`## Confirmed\`
+tells you which of your facts the client has ratified. A fact you are
+writing that appears under \`## Confirmed\` may be stated plainly, without
+a confidence marker; anything else follows your normal rules \u2014 infer
+carefully, mark uncertainty. Never copy its content into the five files.
+
+A missing or empty section is not an instruction. It means the client has
+not said, not that you may assume anything \u2014 proceed exactly as you would
+without the file.
+
 Never create, modify, or delete anything outside \`.opencode/context/\`. The
 \`edit\` permission enforces this. Do not attempt to work around it with bash.
 
@@ -496,6 +513,11 @@ Then write the five files. For each significant subsystem, give a short
 reason. This is the single most valuable thing you produce: where an agent
 should open its editor next.
 
+manager.md is created for the client by the plugin, not by you; if it is
+missing anyway, mention once in your final report that they can add it
+themselves to record what is being worked on, what comes next, and what
+they have ratified. Never create it.
+
 # Incremental update
 
 Trigger: \`.opencode/context/\` exists and work has just been done here.
@@ -523,6 +545,14 @@ that is already stated in another context file \u2014 one fact has one home, and
 the other files link to it. If nothing material changed, make no edits and
 report "no update needed".
 
+Before editing, re-read manager.md: its \`## Current\` and \`## Next\`
+sections tell you what the client is actually working on, and its
+\`## Confirmed\` section settles which of your facts are ratified. If what
+you are about to write would place the code somewhere the client never
+described, trust the code, make the edit the code justifies, and report
+the gap in your final message \u2014 never reconcile the two sides silently,
+and never edit manager.md to close it.
+
 # Minimal exploration
 
 Default shape:
@@ -617,9 +647,14 @@ Audit the five files for:
 - duplicated information \u2014 one canonical place per fact
 - missing canonical entry points for significant subsystems
 - unsupported assumptions \u2014 anything unmarked that you cannot verify
+- manager.md, if present: is \`## Current\` and \`## Next\` still true of
+  recent work, is every \`## Confirmed\` entry still true of the code, has
+  it outgrown roughly 150 lines \u2014 report findings, but never edit, prune,
+  or reorganize it; that is the client's call
 
-Fix problems only in \`.opencode/context/\`. Never modify source code during a
-review. Report what you found, what you fixed, and what you could not verify.
+Fix problems only in the five files you own \u2014 never in manager.md, which
+belongs to the client. Never modify source code during a review. Report
+what you found, what you fixed, and what you could not verify.
 
 # Reporting
 
@@ -637,7 +672,9 @@ Finish with a short report:
       "edit": {
         "*": "deny",
         "*/.opencode/context/**": "allow",
-        ".opencode/context/**": "allow"
+        ".opencode/context/**": "allow",
+        "*/.opencode/context/manager.md": "deny",
+        ".opencode/context/manager.md": "deny"
       },
       "bash": {
         "*": "deny",

package/dist/commands.js

@@ -19,7 +19,13 @@ Remember: write conclusions, not inventories. Link to the project's existing
 documentation instead of duplicating it.
 
 Report what you created or updated, what you deliberately left out, and
-anything that contradicts the code or existing docs.`
+anything that contradicts the code or existing docs.
+
+If \`.opencode/context/manager.md\` does not exist, mention in your final
+report that the client can add it themselves \u2014 their own file with
+\`## Current\`, \`## Next\`, \`## Confirmed\` and \`## Instructions\` \u2014 for what
+is being worked on, what comes next, what they have ratified, and standing
+direction. Never create it.`
   },
   "context-update": {
     description: "Incrementally update .opencode/context/ after recent work via the context agent.",
@@ -50,8 +56,9 @@ timestamp-only edits. If nothing material changed, make no edits and report
     subtask: true,
     template: `Context review.
 
-Everything outside \`.opencode/context/\` is read-only for this run. Do not
-modify source code under any circumstances.
+Everything outside the five context files is read-only for this run \u2014
+including \`manager.md\`, which belongs to the client. Do not modify source
+code under any circumstances.
 
 Audit the five context files for:
 
@@ -64,6 +71,9 @@ Audit the five context files for:
 - missing canonical entry points for significant subsystems
 - unsupported assumptions \u2014 anything stated as fact that you cannot verify,
   or that lacks a confidence marker
+- \`manager.md\`, if present: is \`## Current\` and \`## Next\` still true of
+  recent work, is every \`## Confirmed\` entry still true of the code, has it
+  outgrown roughly 150 lines \u2014 report findings, but never edit it
 
 Fix what you find in \`.opencode/context/\` only, then report: findings, fixes,
 and anything you could not verify.`
@@ -94,7 +104,8 @@ Print one PASS/FAIL line per check below, with the exact fix for any FAIL.
    trap: an id that is a valid gateway route but is NOT in the plugin's
    \`omniroute.models\` allowlist fails with
    \`ProviderModelNotFoundError: Model not found\`; the fix is to add that id to
-   the \`models\` array, or use the always-registered \`auto\`.
+   the \`models\` array, or set it as \`combo\` \u2014 the combo id is registered
+   whether or not the gateway advertises it, so it needs no allowlist entry.
 
 Change nothing. Print a final one-line summary of failures.`
   }
@@ -113,26 +124,49 @@ function applyCommands(cfg, commands = COMMANDS) {
   }
   return { added, kept };
 }
+var INSTRUCTION_MARKER = "<!-- lacode:context-map-instruction:v1 -->";
+var INSTRUCTION_OPT_OUT = "<!-- lacode:context-map-instruction:off -->";
 var STANDING_INSTRUCTION = `## Repository context map
 
 This project may keep a navigation map in \`.opencode/context/\`. Before broad
 exploration, check whether it exists (\`ls .opencode/context\` \u2014 never the \`glob\`
-tool, which skips hidden directories). If it does, read only the file relevant to
-the task \u2014 architecture.md, contexts.md, conventions.md, workflows.md,
-decisions.md \u2014 then start from the canonical entry points it lists.
-
-Source code is authoritative: if the map disagrees with the code, trust the code,
-say so, and never edit source to match the map. Never edit \`.opencode/context/\`
-yourself \u2014 the context agent owns it. Say in your final report if your
-work revealed something that belongs in the map.`;
+tool, which skips hidden directories). If \`manager.md\` exists there, read it
+first: it is the client's own statement of intent \u2014 what is being worked on,
+what comes next, \`## Confirmed\` lists what the client has ratified, and
+\`## Instructions\` holds standing managerial directions. It outranks every
+other context file and every inference of yours about what matters right now.
+It says nothing about where code lives, so it cannot contradict the code;
+treat its \`## Confirmed\` entries as settled decisions, not as a licence to
+skip reading the code. Any heading in it is direction, so read the whole
+file rather than only the sections above. The rest of the map remains usable,
+just unratified where \`## Confirmed\` does not cover it. Then read only the
+file relevant to the task \u2014 \`architecture.md\`, \`contexts.md\`,
+\`conventions.md\`, \`workflows.md\`, \`decisions.md\` \u2014 and start from the
+canonical entry points it lists.
+
+Source code is authoritative: if the map disagrees with the code,
+trust the code and say so; never edit source to match it.
+Never edit the five context files yourself \u2014 the context agent owns them.
+\`manager.md\` is the client's own file and the context agent is explicitly
+permission-denied from writing it. You may write it only when the client
+explicitly asks you to in this conversation, and then only what they asked
+for; never on your own initiative, and never to "keep it up to date". Say in
+your final report if your work revealed something that belongs to the map, or
+if \`manager.md\` and the code disagree.`;
 function applyInstructions(cfg) {
-  const existing = cfg.instructions;
-  if (Array.isArray(existing) && existing.length > 0) return { added: false };
-  cfg.instructions = [STANDING_INSTRUCTION];
+  const existing = Array.isArray(cfg.instructions) ? cfg.instructions : [];
+  const texts = existing.filter((e) => typeof e === "string");
+  if (texts.some((e) => e.includes(INSTRUCTION_OPT_OUT))) return { added: false };
+  if (texts.some((e) => e.includes(INSTRUCTION_MARKER))) return { added: false };
+  cfg.instructions = [...existing, `${INSTRUCTION_MARKER}
+
+${STANDING_INSTRUCTION}`];
   return { added: true };
 }
 export {
   COMMANDS,
+  INSTRUCTION_MARKER,
+  INSTRUCTION_OPT_OUT,
   STANDING_INSTRUCTION,
   applyCommands,
   applyInstructions