@lawaty/lacode 0.8.0 → 0.10.0

package/CHANGELOG.md

@@ -6,9 +6,168 @@ All notable changes to LaCode are recorded here. The format follows
 
 Versions come from git release commits; the npm version is bumped in the same
 commit as the changelog entry it describes.
-
 ## [Unreleased]
 
+## [0.10.0] — a notification waits for you instead of timing out, and a permission can be answered from the popup
+
+### Added
+
+- **A permission prompt can be answered from the notification itself.** The
+  plugin reads the permission request id off opencode's `permission.asked`
+  event and puts it in the helper's environment (`LACODE_REQUEST_ID`), so the
+  notification carries three buttons: **Allow once**, **Always allow** and
+  **Deny**. Their names are opencode's own reply values — `once`, `always` and
+  `reject` ("reject" is the server's word for deny) — so a click is already a
+  valid answer and nothing has to be translated on the way.
+
+  The answer travels back over the same path the notification came. The desktop
+  end is an ssh forced command, so its stdout comes back down the ssh
+  connection and the plugin reads the chosen button's name off the helper's
+  stdout — no new key, no listener, no HTTP server. The hop was one-way until
+  now, and what made it two-way was a channel that was already there: the
+  forced command's stdout is carried to whoever opened the connection, so the
+  answer rides home on the connection that is already open. The plugin then
+  answers the permission through opencode's own API, and a permission that was
+  already answered in the terminal is recognised rather than reported as a
+  failure.
+
+  The wire payload is six newline-delimited fields on both wires —
+  `title\nmessage\nurgency\nicon\nsound\nrequestID`, the request id last — and a
+  payload with fewer than six fields carries no request id, so an older sender
+  still works.
+
+  Two limits, stated plainly. The scope is **permissions only**: a question is
+  not answerable this way, because opencode's v1 SDK client — the one this
+  plugin has — has no question API at all, and the v2 routes need a bound TCP
+  socket that the default opencode TUI does not have. And the buttons are
+  **Linux only**: `osascript` and `terminal-notifier` have no action support,
+  so a macOS desktop still gets a plain notice, and the answer there still has
+  to be given in the terminal.
+
+### Changed
+
+- **A desktop notification now waits for you instead of timing out on its own.**
+  `notify-send` is called with `--expire-time=0` — the freedesktop "never
+  expire" timeout — at all three call sites: `sendLocal` in
+  `src/tunnel/index.ts`, the tunnel's forced command
+  (`bin/oc-notify-receiver`), and `send_notify` in `bin/oc`. Without it the
+  desktop daemon's own timer dismissed the popup by itself: measured on KDE
+  Plasma 6.7.4, a normal-urgency notification is closed with reason 1
+  ("expired") after about five seconds, so a notice the user had not acted on
+  within that window was simply gone — the difference between a notice you can
+  still act on and one you missed. A notification now stays on the desktop
+  until you close it.
+
+  Nothing else about it changed: the `--urgency` values are untouched (a
+  question or a permission prompt is deliberately not `critical`, so it does
+  not escalate to a modal on most desktops), and the whitelists and the
+  cooldown behaviour are exactly as they were.
+
+### Documented
+
+- **The npm publish notice does not say which dist-tag a release lands on.** npm
+  12 prints "Publishing to https://registry.npmjs.org/ with tag latest" for every
+  publish, including one whose `publishConfig.tag` sends it to `beta`: the
+  message reports the CLI's default, not the resolved tag. 0.9.0 was published
+  that way and landed on `beta`, with `latest` still at 0.4.2. The registry is
+  the authority, not the notice — after publishing, read
+  `npm view @lawaty/lacode dist-tags` before assuming anything about where the
+  release went.
+
+## [0.9.0] — the cartographer keeps an active backlog, and the model stops naming slot variants
+
+### Added
+
+- **The cartographer keeps an active backlog, and the plugin enforces its
+  window.** `.opencode/context/active.md` is a sixth file in the map directory:
+  the work in flight, grouped by the ISO week each task was opened in. A task
+  that is not marked `[x]` is open, and an open task is never removed however
+  old it is; a task that is finished and dated is kept for a week after it was
+  finished and is then dropped. The file is therefore a rolling window rather
+  than a history — the question it answers is "what is open, and what just
+  closed", not "what has ever been done". A backlog that only grows is a
+  backlog nobody reads.
+
+  The window is applied by `src/lib/active-backlog.ts` and by the plugin, not
+  by the cartographer's prompt. Deciding when a task has aged out is
+  arithmetic, and arithmetic belongs where a test can pin the boundary: a rule
+  a model applies is a rule the model applies when it feels like it — one run
+  prunes and the next does not, and nothing anywhere reports the difference,
+  so the failure is silent and the backlog just grows. The plugin normalizes
+  the file on every edit of it and once when the session starts, so a hand
+  edit is grouped and pruned whether the cartographer ran or not, and the file
+  is rewritten only when its canonical form differs from what is on disk, so
+  the write cannot loop. The boundary is strict: a task finished exactly seven
+  days ago is still that week's news, and is kept.
+
+### Fixed
+
+- **A slot variant is no longer in the agent list the model is shown, so the model
+  stops naming slots by hand.** opencode builds the system prompt's "Available
+  agent types" block by filtering the agent registry on `mode !== "primary"` and on
+  the caller's task permission. It never reads `hidden`: that flag is honoured only
+  by the TUI, the @-mention pickers, the "agent not found" message and default-agent
+  resolution. Every pooled variant was therefore listed to the model under its own
+  name — "explore-1: Hidden pool variant explore-1" — and a model that can see
+  twelve concrete slot names reaches for them, so the root agent kept spawning
+  `explore-1` and `implement-4` instead of the bare base, and the pool refused
+  every one. The refusal was right and the leak that provoked it was not: naming a
+  variant is how a caller would pick the provider and skip the rotation and the
+  slot's ceiling, so it cannot be allowed to succeed. The variants now carry
+  `mode: "primary"`, the one field that filter respects, which takes them out of
+  the agent list while leaving them spawnable by name — the task tool resolves an
+  agent by name and never reads its mode — and out of the TUI, where `hidden`
+  already kept them. The bare bases are untouched and stay in the list, so the
+  model has nothing but the bases to choose from.
+
+- **A refusal no longer names the variant it refused, and the instructions no
+  longer list the names they forbid.** The refusal was the strongest remaining
+  channel. It is the tool result the model reads at the exact moment it is
+  choosing what to spawn next, and it used to repeat the name that had just been
+  denied — so the denial was the thing that taught the name, and the model copied
+  it back. It now names the base instead, which is what the model should type.
+  The same reasoning applies to the rules themselves: "never name a `-N` variant
+  (`explore-1`..`explore-4`, `implement-1`..)" put eight concrete agent names in
+  front of the model in the sentence that told it what to spawn. A rule that
+  lists the names it forbids teaches the names; the rule now states the rule
+  without an example, in the shipped agent prompts, the project prompts and the
+  global delegation rules.
+
+- **The cartographer no longer leaves empty sessions in the session list.** The
+  session was created before the run started, and only the turn's own success
+  and failure paths retired it. Anything that threw in between — a slot that
+  could not be picked, a claim that could not be written, a prompt that failed
+  before it returned — stranded a session with no messages in it: an entry in
+  the user's list that opens as nothing at all. Retirement now covers the whole
+  gap between the create and the prompt, and the delete is *verified* rather
+  than assumed — it is read back afterwards, retried once, and a failure is
+  logged instead of swallowed. (Archiving is not a way out: opencode's list is
+  served from the session rows themselves, so a session with `time_archived` set
+  is still listed. Only a delete removes an entry.)
+- **A finished cartographer run retires its session and keeps the transcript**
+  was already true, and stays true: the transcript is written first and the
+  session deleted second, because the transcript is the only record of what the
+  run did. The plugin's own last 20 runs are kept in full.
+
+### Changed
+
+- **The bundled default pool no longer ships a model its provider has withdrawn.**
+  `presets/free-tier.json` named `opencode/space-bunny-free` as its first slot at
+  weight 3 — the slot that took the most turns. The opencode provider withdrew that
+  model, and because it was the default, every new session then died at step 0 with
+  `ProviderModelNotFoundError: Model not found: opencode/space-bunny-free`. Nothing
+  in the package could tell: the pool warns about a slot that is missing from the
+  config, not about a slot whose model the provider no longer serves, and the root
+  agent's own model lives in the user's config rather than here.
+
+- **`scripts/retire-cartographer-sessions.mjs` clears the sessions the feature
+  did not reach.** Retirement landed after 250 runs had already piled up across
+  the machine's projects, and those were never cleaned. The tool talks to the
+  opencode server over its HTTP API — the same interface the plugin uses — and
+  writes a compact record of each retired session to
+  `~/.local/share/opencode/lacode/cartographer-archive/` before deleting it, so
+  nothing is lost. `--dry-run` shows what it would do.
+
 ## [0.8.0] — cooldowns are probed instead of trusted, and the instructions agent can read the map
 
 ### Added
@@ -371,12 +530,15 @@ experimental; `latest` remains 0.4.2.
 
 - First published release: pooled subagents over a shared set of models.
 
-[Unreleased]: https://github.com/lawaty/lacode/compare/v0.8.0...HEAD
+[Unreleased]: https://github.com/lawaty/lacode/compare/v0.10.0...HEAD
+[0.10.0]: https://github.com/lawaty/lacode/compare/v0.9.0...v0.10.0
+[0.9.0]: https://github.com/lawaty/lacode/compare/v0.8.0...v0.9.0
 [0.8.0]: https://github.com/lawaty/lacode/compare/v0.7.1...v0.8.0
 [0.7.1]: https://github.com/lawaty/lacode/compare/v0.7.0...v0.7.1
 [0.7.0]: https://github.com/lawaty/lacode/compare/v0.6.0...v0.7.0
 [0.6.0]: https://github.com/lawaty/lacode/compare/v0.5.0...v0.6.0
 [0.5.0]: https://github.com/lawaty/lacode/compare/v0.4.2...v0.5.0
+[0.4.2]: https://github.com/lawaty/lacode/compare/v0.4.1...v0.4.2
 [0.4.1]: https://github.com/lawaty/lacode/compare/v0.4.0...v0.4.1
 [0.4.0]: https://github.com/lawaty/lacode/compare/v0.3.0...v0.4.0
 [0.3.0]: https://github.com/lawaty/lacode/compare/v0.2.2...v0.3.0

package/README.md

@@ -213,8 +213,9 @@ deliberately *not* injected, are in
 Agents are stateless between tasks, and exploring your repository is the most
 expensive part of any task — so every agent pays for it again, re-deriving the
 same layout, entry points and boundaries from scratch. LaCode keeps a short,
-maintained map of the repository in `.opencode/context/` (five files:
-`architecture`, `contexts`, `conventions`, `workflows`, `decisions`) and injects
+maintained map of the repository in `.opencode/context/` (five navigation files:
+`architecture`, `contexts`, `conventions`, `workflows`, `decisions`, plus
+`active.md` — the active backlog) and injects
 a standing rule that every agent reads the relevant file before exploring and
 starts from the canonical entry points it lists. The map holds conclusions, not
 inventories: it answers "what should I look at first?" and nothing else, which
@@ -251,7 +252,7 @@ in [docs/CONTEXT.md](docs/CONTEXT.md).
 The project's root `AGENTS.md` is your own statement of intent: it records
 what you want worked on and how you want it approached. It says nothing about
 where code lives, so it can never contradict the code, and within that domain
-it outranks the five generated context files and any agent's inference about what
+it outranks the generated context files and any agent's inference about what
 matters right now.
 
 The file is per-clone and not committed, so it is yours rather than shared
@@ -345,9 +346,11 @@ lacode doctor                                        # what the environment reso
 ```
 
 `lacode notify` is fire-and-forget and always exits 0 — an unreachable desktop
-must never be able to fail the process that tried to notify you. `lacode forward
-HOST -- COMMAND` runs a command on another host over ssh and exits with its
-status.
+must never be able to fail the process that tried to notify you. The one
+exception is an actionable notification — one carrying a permission request id
+— which waits for the click, because the answer is the whole point of it.
+`lacode forward HOST -- COMMAND` runs a command on another host over ssh and
+exits with its status.
 
 The full CLI is `notify`, `forward`, `doctor`, `version`, `update`, `receive`
 and `tunnel setup`. `version` reports which copy of LaCode is running — and
@@ -369,7 +372,7 @@ want it.
 | [Install and troubleshooting](docs/INSTALL.md) | Where opencode puts the package, what to do when the agents are missing, the version matrix, macOS differences, and the `lacode` CLI. |
 | [Configuration reference](docs/CONFIGURATION.md) | Every plugin option, how the pool resolves its slots, per-agent tool grants, and exactly what gets written into your config. |
 | [OmniRoute gateway](docs/OMNIROUTE.md) | The optional local gateway integration: setup, full option set, a latency-measured free combo, and its troubleshooting table. |
-| [Context map](docs/CONTEXT.md) | The mechanism behind `.opencode/context/` — the one-writer permission rule, the five files, and what the log lines mean. |
+| [Context map](docs/CONTEXT.md) | The mechanism behind `.opencode/context/` — the one-writer permission rule, the files, and what the log lines mean. |
 | [Remote hosts and notifications](docs/TUNNEL.md) | The SSH notification hop, payload format, receiver contract, and holding the forward open. |
 | [Benchmarks](docs/BENCHMARKS.md) | How the cost harness works, and why it deliberately publishes no savings number. |
 | [User stories](docs/USER-STORIES.md) | The behavioural contracts behind all of the above, written so a test can assert them. |

package/dist/agents.js

@@ -90,8 +90,8 @@ failing, or a runtime message saying no slot is available \u2014 that is not a r
 to do the work yourself, and not a reason to stop and ask.
 
 **Retry.** A refused or cooling slot is transient and costs you nothing but a
-turn. Spawn the bare base again. Do not escalate a \`-N\` variant when a refusal
-names one \u2014 the refusal means the pool has a routing problem, not that you
+turn. Spawn the bare base again. Do not escalate to a numbered variant after a
+refusal \u2014 the refusal means the pool has a routing problem, not that you
 picked the wrong number.
 
 Retry is always available and never wrong, which is why it is the default. But
@@ -450,7 +450,7 @@ if the blocker is understanding rather than execution, report that instead.`,
     }
   },
   "context": {
-    "description": "Repository cartographer and memory maintainer. Bootstraps and incrementally maintains .opencode/context/ (architecture, contexts, conventions, workflows, decisions) as a small navigation map for future agents. Runs automatically after sessions that changed files; can also be invoked with /context-init, /context-update, /context-review. Never use it for general coding tasks.",
+    "description": "Repository cartographer and memory maintainer. Bootstraps and incrementally maintains .opencode/context/ (architecture, contexts, conventions, workflows, decisions) as a small navigation map for future agents, and keeps .opencode/context/active.md \u2014 the active backlog of work in flight, grouped by week. Runs automatically after sessions that changed files; can also be invoked with /context-init, /context-update, /context-review. Never use it for general coding tasks.",
     "mode": "subagent",
     "temperature": 0.1,
     prompt: `# Role
@@ -466,7 +466,7 @@ map is a derived index of it.
 
 # Owned files
 
-You own exactly these five files and nothing else:
+You own exactly these files and nothing else:
 
 - \`.opencode/context/architecture.md\` \u2014 high-level architecture, major layers,
   boundaries, important entry points, dependency rules. Target 50\u2013150 lines.
@@ -481,6 +481,9 @@ You own exactly these five files and nothing else:
 - \`.opencode/context/decisions.md\` \u2014 architectural decisions discovered
   during work that are not already recorded in the project's own decision
   log. Concise; variable length.
+- \`.opencode/context/active.md\` \u2014 the active backlog: work in flight, grouped
+  by the week it was opened. Not part of the navigation map; it is described
+  under "Task backlog" below.
 
 # Current-state only
 
@@ -520,7 +523,8 @@ Explore progressively and stop as soon as you have a usable map:
 You are mapping a city, not auditing every house. Do not attempt to
 understand every file.
 
-Then write the five files. For each significant subsystem, give a short
+Then write the five files. Also create \`.opencode/context/active.md\` with its
+heading and no tasks. For each significant subsystem, give a short
 "Start here" list \u2014 at most about five canonical files, each with a one-phrase
 reason. This is the single most valuable thing you produce: where an agent
 should open its editor next.
@@ -544,7 +548,7 @@ Trigger: \`.opencode/context/\` exists and work has just been done here.
    - an architectural decision
    - a new dependency between subsystems
    - a renamed or relocated subsystem
-   - a previously undocumented invariant
+    - a previously undocumented invariant
 
 Do not update documentation merely because source files changed. Do not
 rewrite files wholesale. Do not make timestamp-only edits. Do not add a fact
@@ -552,6 +556,38 @@ 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".
 
+Also keep \`.opencode/context/active.md\` current: record work that is in
+flight, and mark a task finished \u2014 with the date it finished \u2014 when it is.
+
+# Task backlog
+
+\`.opencode/context/active.md\` holds the work in flight. It is a rolling
+window, not a history: it answers "what is open, and what just finished".
+
+Format \u2014 one line per task, under the ISO week the task was opened in:
+
+    ## 2026-W43
+
+    - [ ] Ship the release notes \u2014 opened 2026-W43
+    - [x] Fix the flaky test \u2014 opened 2026-W43, finished 2026-10-19
+
+The rules:
+
+- A task that is not marked \`[x]\` is OPEN. An open task is never removed,
+  however old it is.
+- A task is FINISHED when it is marked \`[x]\` AND carries a \`finished\`
+  date. Record the date it actually finished, as \`YYYY-MM-DD\`.
+- The week is \`YYYY-Www\`, Monday to Sunday. \`date +%G-W%V\` prints it.
+- A finished task is dropped once it is more than a week old. The plugin
+  enforces that: record the finished task with its date and let the window
+  close on its own. Do not delete old finished tasks by hand, and do not
+  keep a finished task back to preserve it \u2014 the file is meant to stay
+  small.
+- Never invent a task. Record work that actually happened, and mark a task
+  finished only once it is finished.
+- Keep the file inside the window. If the backlog has grown past a handful
+  of weeks, that is a signal to close finished tasks, not to add sections.
+
 # Minimal exploration
 
 Default shape:
@@ -638,7 +674,7 @@ the lowest-value ones, and link out to authoritative project docs.
 
 Trigger: an explicit review (see the \`context-review\` command).
 
-Audit the five files for:
+Audit the map files and the backlog for:
 
 - stale information \u2014 verify claims against the code
 - contradictions between files, or between the map and the code
@@ -646,10 +682,12 @@ 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
+- backlog tasks that are finished but carry no date \u2014 the retention window
+  cannot age those out, so they stay forever
 
-Fix problems only in the five files you own. 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 files you own. Never modify source code during a
+review. Report what you found, what you fixed, and what you could not
+verify.
 
 # Reporting
 
@@ -817,7 +855,28 @@ function buildAgentSet() {
       const variant = {
         ...def,
         description: `Hidden pool variant ${base}-${slot}: slot ${slot}. Its model is NOT set here -- LaCode injects it from the resolved pool preset at config time, so the preset is the only place a pool model is written down. Spawn '${base}' and let the pool route.`,
-        hidden: true
+        hidden: true,
+        // `mode: "primary"` is what keeps a variant OUT of the model's system
+        // prompt. `hidden` cannot do it.
+        //
+        // opencode builds the "Available agent types" block by filtering the
+        // agent registry on `mode !== "primary"` and on the caller's task
+        // permission. It never looks at `hidden`: that flag is honoured only by
+        // the TUI and the @-mention pickers, by the "agent not found" message,
+        // and by default-agent resolution. A variant left as `mode: "subagent"`
+        // is therefore listed to the model under its own name -- "explore-1:
+        // Hidden pool variant explore-1" -- and the model copies that name
+        // straight into its next spawn. The pool then refuses it, because
+        // naming a variant is how a caller would pick the provider and skip the
+        // rotation. The refusal is right; the leak that provokes it is not.
+        //
+        // `mode` is the only field that filter respects, and setting it here is
+        // safe: the task tool never reads an agent's mode -- it resolves the
+        // agent by name and runs it -- and every other place that filters on
+        // `mode !== "primary"` also filters on `!hidden`, which these already
+        // are. opencode uses this same pair for its own compaction, title and
+        // summary agents.
+        mode: "primary"
       };
       delete variant.model;
       set[`${base}-${slot}`] = variant;

package/dist/commands.js

@@ -67,7 +67,8 @@ 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.
+context files inside their size targets. 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.
@@ -104,10 +105,10 @@ timestamp-only edits. If nothing material changed, make no edits and report
     subtask: true,
     template: `Context review.
 
-Everything outside the five context files is read-only for this run. Do not
+Everything outside \`.opencode/context/\` is read-only for this run. Do not
 modify source code under any circumstances.
 
-Audit the five context files for:
+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
@@ -118,6 +119,8 @@ 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
+- backlog tasks that are finished but carry no date \u2014 the retention window
+  cannot age those out, so they stay forever
 
 Fix what you find in \`.opencode/context/\` only, then report: findings, fixes,
 and anything you could not verify.`