@lawaty/lacode 1.0.3 → 1.2.0

package/dist/commands.js

@@ -38,7 +38,6 @@ var MAX_CLAIM_AGE_MS = 30 * 60 * 1e3;
 var HANG_COOLDOWN_MS = 10 * 60 * 1e3;
 var UNAVAILABLE_COOLDOWN_MS = 60 * 1e3;
 var MAX_WEIGHT = 100;
-var MAX_SLOTS = 4;
 var COOLDOWN_BASE_MS = 60 * 1e3;
 var COOLDOWN_MAX_MS = 15 * 60 * 1e3;
 var QUOTA_COOLDOWN_BASE_MS = 15 * 60 * 1e3;
@@ -67,11 +66,14 @@ your system prompt.
 Otherwise follow the bootstrap procedure in your system prompt: progressive
 exploration (README \u2192 existing docs \u2192 manifests \u2192 top-level structure \u2192 build
 and framework config \u2192 entry points \u2192 selective source), then write the five
-context files inside their size targets. Also create
-\`.opencode/context/active.md\` with its heading and no tasks.
+context files inside their line budgets, using the entry schema (provenance
+marker, rule of at most three lines, \`\u2014 See <path>[ \xA7Section] (verified
+YYYY-MM-DD)\`). Also create \`.opencode/context/active.md\` with its heading and no
+tasks.
 
-Remember: write conclusions, not inventories. Link to the project's existing
-documentation instead of duplicating it.
+Remember: write conclusions, not inventories. Point at the project's existing
+documentation instead of restating it. Run the drift pass and report a
+contradiction rather than silently choosing a side.
 
 Report what you created or updated, what you deliberately left out, and
 anything that contradicts the code or existing docs.`
@@ -97,7 +99,11 @@ or an invariant not yet recorded.
 
 Do not edit documentation just because source files changed. No
 timestamp-only edits. If nothing material changed, make no edits and report
-"no update needed".`
+"no update needed".
+
+Every new or changed entry uses the schema in your system prompt and stays
+under the file's line budget. If a file is already over budget, consolidate
+before adding.`
   },
   "context-review": {
     description: "Audit .opencode/context/ for staleness, contradictions, excess size, duplication, and missing entry points.",
@@ -105,20 +111,29 @@ 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.
+Follow the review procedure and entry schema in your system prompt. Everything
+outside \`.opencode/context/\` is read-only for this run. Do not modify source
+code under any circumstances.
 
 Audit the context files and the backlog for:
 
-- stale information \u2014 verify claims against the actual code
-- contradictions between context files, or between the map and the code
-- excessive size \u2014 consolidate toward the per-file targets in your system
-  prompt
+- schema \u2014 every entry has one provenance marker, at most three lines, a
+  pointer, and a \`(verified YYYY-MM-DD)\` date
+- budget \u2014 every file is within its non-blank-line cap; consolidate rather
+  than exceed it
+- stale information \u2014 verify claims against the actual code and the cited page
+- contradictions between context files, or between the map and a page \u2014 mark
+  \`[disputed]\` and report both sides; never silently prefer one
+- dangling pointers \u2014 every cited path and \xA7section must exist
+- unarchived content \u2014 an entry with no source in the tree; report it and keep
+  it, because it may be the only copy
+- restatement \u2014 a table, a fenced block, or a long verbatim span copied from a
+  page
 - duplicated information \u2014 one canonical place per fact; link to the
   project's own docs rather than restating them
 - missing canonical entry points for significant subsystems
-- unsupported assumptions \u2014 anything stated as fact that you cannot verify,
-  or that lacks a confidence marker
+- unsupported assumptions \u2014 anything that is not \`[binding]\` or \`[disputed]\`
+  should be \`[provisional]\`
 - backlog tasks that are finished but carry no date \u2014 the retention window
   cannot age those out, so they stay forever
 
@@ -142,7 +157,7 @@ Follow the rules for the file in your system prompt, then report what you change
 Print one PASS/FAIL line per check below, with the exact fix for any FAIL.
 
 1. Pool status \u2014 call the \`pool_status\` tool. Report the slot list, each
-   slot's load against its ceiling (twice the slot's weight), and which models
+   slot's load against its budget (its weight), and which models
    are cooling.
 
 2. OmniRoute configured \u2014 inspect the \`@lawaty/lacode\` plugin options in the
@@ -179,10 +194,10 @@ The pool is ONE global slot table shared by every pooled base (explore, implemen
 
 2. Resolve the instruction above into a target slot table. These are the rules the loader enforces \u2014 never write a file that breaks one:
    - one slot per line: \`<provider>/<model-id>  [weight]\`
-   - at most ${MAX_SLOTS} slots, and a model may appear only once
-   - weight is optional (default 1) and must be a number in (0, ${MAX_WEIGHT}]. It is the slot's active-session budget for one pass \u2014 how many turns it takes per cycle \u2014 and its concurrency ceiling is twice that. NOT a priority; pick order follows line order.
+   - any number of slots; a model may appear on more than one line, and each line is its own slot with its own budget
+   - weight is optional (default 1) and must be a number in (0, ${MAX_WEIGHT}]. It is the slot's active-session budget \u2014 how many concurrent sessions it may hold. The pool's total capacity is the sum of the weights. NOT a priority; pick order follows line order.
    - \`#\` starts a comment (whole-line or trailing); blank lines are ignored.
-   If the instruction names a model ambiguously, or would need more than ${MAX_SLOTS} slots, stop and ask rather than guessing.
+   If the instruction names a model ambiguously, stop and ask rather than guessing.
 
 3. Write the WHOLE file, not a patch. This file is an override, not an edit target: any slot you drop disappears, and slot numbers are line positions, so a partial write silently renumbers slots. Keep the existing comment header. If the write fails on a missing directory, create \`~/.config/lacode\` first and retry.
 
@@ -208,6 +223,11 @@ $ARGUMENTS
 
 Report the tool's output as it came back, then add one short line naming what changed: re-admitted, still limited, or benched because the provider does not serve the model. If a model was benched as \`model-missing\`, say so and name the replacement in \`~/.config/lacode/pool.txt\` \u2014 but change nothing yourself.`
   },
+  "reprocess-timeline": {
+    description: "Rebuild this session's timeline from its full transcript",
+    agent: "implement",
+    template: "Call the `timeline_reprocess` tool exactly once with no arguments. Then reply with only its output."
+  },
   "image-in-cb": {
     description: "Attach the clipboard image to this message \u2014 macOS needs pngpaste, Linux needs wl-paste or xclip.",
     template: "$ARGUMENTS"