geneseed 4.27.1 → 4.28.0

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.
package/CHANGELOG.md CHANGED
@@ -8,6 +8,18 @@ label. For the capability ↔ spec map, see [SHIPPED.md](SHIPPED.md).
8
8
 
9
9
  ## [Unreleased]
10
10
 
11
+ ## [4.28.0] — 2026-10-28
12
+
13
+ Minor: an ask that waits on the user and is not clear by itself now says what it does and why; the OpenCode 1.x workflow banner no longer paints over the input box. Run `geneseed rebuild-all` once after updating to get the amended rule and the quiet banner.
14
+
15
+ ### Changed
16
+
17
+ - **An unclear ask now comes with its reason.** *Mark the Ask* (`comms` pack) said how to mark a command, a question or a choice that waits on the user, but not what it must say. A marked `👉 run git rebase --onto main HEAD~3` stayed opaque. The rule now adds: before a command the user must run or approve, or a question that is not clear by itself, write one or two plain lines on what it does, why now and what it changes or risks. For a question, say what the answer decides. A clear ask stays bare. Both the full and the lean text are amended. Run `geneseed rebuild-all` to get it.
18
+
19
+ ### Fixed
20
+
21
+ - OpenCode 1.x: the workflow plugin no longer paints `[geneseed-workflow] loaded — …` in red over the TUI input box. Observed on 1.19.4: the banner does not print before the TUI draws, as #373 assumed. The banner now prints only with `GENESEED_DEBUG=1`. A warning that the tool may not register still goes out, to OpenCode's log.
22
+
11
23
  ## [4.27.1] — 2026-10-27
12
24
 
13
25
  Patch: the guard's refusals no longer name the switch that turns it off.
package/README.md CHANGED
@@ -17,7 +17,7 @@
17
17
  [![Plugins](https://img.shields.io/badge/plugins-7-teal)](adapters/opencode/plugins/)
18
18
  [![OpenCode · Claude Code · Bob · OpenClaude · AGENT.md](https://img.shields.io/badge/works%20with-OpenCode%20·%20Claude%20Code%20·%20Bob%20·%20OpenClaude%20·%20AGENT.md-1f6feb)](#-supported-harnesses)
19
19
 
20
- [**Why**](#-1--why-geneseed) · [**Setup**](#-2--setup) · [**Web & terminal**](#-3--web--terminal) · [**What you get**](#-4--what-you-get) · [**Harnesses**](#-supported-harnesses) · [**Docs**](#-documentation)
20
+ [**Why**](#-1--why-geneseed) · [**Setup**](#-2--setup) · [**Web & terminal**](#-3--web--terminal) · [**What you get**](#-4--what-you-get) · [**Ownership**](#-ownership-of-production-code) · [**Harnesses**](#-supported-harnesses) · [**Docs**](#-documentation)
21
21
 
22
22
  </div>
23
23
 
@@ -35,9 +35,10 @@ Want to read what it leaves behind before installing anything? [**geneseed-demo*
35
35
 
36
36
  ### Why not just a CLAUDE.md?
37
37
 
38
- A hand-written instructions file is prose the model may or may not honour, copied into every repo and drifting in each one. Geneseed is a build, and that changes four things:
38
+ A hand-written instructions file is prose the model may or may not honour, copied into every repo and drifting in each one. Geneseed is a build, and that changes five things:
39
39
 
40
40
  - **Laws are enforced, not suggested.** A force-push to `main`, a `reset --hard` that abandons unpushed commits, or a credential written into a tracked file is caught by a hook *before* the tool runs, in the host's own dialect — a prompt on Claude Code and OpenClaude, a hard block on OpenCode, exit 2 on Bob. The gates fail closed, and every catch is one line in a ledger that `geneseed status` counts.
41
+ - **The developer stays the owner of the code.** In a production application the agent proposes and the developer decides — per feature, per file or per function, as the team sets in a committed `AGENTS.md`. Interfaces and sensitive zones are always a checkpoint, complex parts are explained before they land, and a hook stops the first write in an application that has not chosen yet. [Ownership →](#-ownership-of-production-code)
41
42
  - **One source, five targets.** Skills are byte-identical on every host; only the wiring differs. Every commit renders all 263 emit configurations, and a second emit into the same tree must change nothing.
42
43
  - **Costs are measured, not guessed.** Zero runtime dependencies. The hook path loads in about 14 ms per tool call. The default *lean* footprint keeps the always-on context small and puts the full rationale one read away — the numbers are in [docs/token-footprint.md](docs/token-footprint.md).
43
44
  - **It follows you.** Install once, globally; every repo inherits it. One `git pull` or `npm install -g geneseed@latest` rebuilds every active install.
package/SHIPPED.md CHANGED
@@ -20,7 +20,7 @@ historical references, not files distributed with the repo.
20
20
  > **On version numbers.** [`harness.config.json`](harness.config.json)'s `version` is a
21
21
  > human-readable label only. The canonical identity of an installed harness is the
22
22
  > **source fingerprint** stamped in `.geneseed-version` (see `geneseed version`), not the
23
- > string. Current label: **4.27.1**.
23
+ > string. Current label: **4.28.0**.
24
24
 
25
25
  ## Capabilities
26
26
 
@@ -14,9 +14,8 @@
14
14
  // written to `.geneseed/workflow-runs/<runId>.log`. Every failure is contained and
15
15
  // reported, never thrown into the session.
16
16
  //
17
- // One stderr line at load (the banner below — it is how a restart shows the tool
18
- // registered, or warns that it could not); everything else is quiet unless
19
- // GENESEED_DEBUG=1. GENESEED_WORKFLOWS_DIR overrides
17
+ // Quiet unless GENESEED_DEBUG=1 (which adds a load banner on stderr), except a
18
+ // warning that the tool may not register. GENESEED_WORKFLOWS_DIR overrides
20
19
  // where saved workflows are loaded from.
21
20
 
22
21
  import { execFile } from "node:child_process"
@@ -197,11 +196,14 @@ const TOOL_DESCRIPTION =
197
196
  const NAME_DESCRIPTION = "saved workflow name; omit to list available"
198
197
  const ARGS_DESCRIPTION = "inputs passed to the workflow script as `args` (object, or a JSON object string)"
199
198
 
200
- // One-line load banner (always on) so a restart visibly confirms the plugin loaded and the
201
- // `workflow` tool is registered. tests/host_canary.mjs reads it as V1's proof of load, so it
202
- // stays on stderr, not `say`: `opencode debug config` never prints a `client.app.log` line. It
203
- // runs once, before the TUI draws, so it does not land in the input box as `say`'s lines did.
199
+ // One-line load banner, GENESEED_DEBUG=1 only: OpenCode 1.19 paints it in red over the input
200
+ // box like any other stderr line (it does not run before the TUI draws). tests/host_canary.mjs
201
+ // sets the flag and reads it as V1's proof of load, so it stays on stderr, not `say`:
202
+ // `opencode debug config` never prints a `client.app.log` line. A warning always goes out,
203
+ // through `say`, so a tool that may not register is never silent.
204
204
  async function loadBanner(warn = "") {
205
+ if (warn) say(`tool 'workflow'${warn}`)
206
+ if (!DEBUG) return
205
207
  try {
206
208
  const names = await listWorkflows()
207
209
  console.error(`[geneseed-workflow] loaded — tool 'workflow' registered, ${names.length} workflow(s) [${names.join(", ") || "none"}] from ${WORKFLOWS_DIR}${warn}`)
@@ -2,5 +2,5 @@
2
2
  "_comment": "version is a human-readable release label only; the canonical identity of an installed harness is the source fingerprint stamped in .geneseed-version (see `harness version`), not this string.",
3
3
  "theme": "neutral",
4
4
  "product": "Geneseed",
5
- "version": "4.27.1"
5
+ "version": "4.28.0"
6
6
  }
@@ -35,7 +35,7 @@ import { isFile, readText } from '../lib/fs.mjs';
35
35
  * console draws it on the cost chart, so it lives here, once, where both read it. Raise it by
36
36
  * exactly the measured overrun and say why in that test's docblock, which keeps its history.
37
37
  */
38
- export const CARRIER_CEILING = { full: 65_715, lean: 41_085 };
38
+ export const CARRIER_CEILING = { full: 66_096, lean: 41_276 };
39
39
 
40
40
  /**
41
41
  * A frontmatter value as the host shows it. The emit writes descriptions JSON-escaped
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "//": "Every field here is argued and gated in tests/unit/package_manifest.test.mjs. `files`, `bin` and `engines` each have a test that fails when reality drifts from this file; `version` mirrors harness.config.json and is gated too. Read that docblock before editing this one.",
3
3
  "name": "geneseed",
4
- "version": "4.27.1",
4
+ "version": "4.28.0",
5
5
  "description": "A portable, theme-able harness you implant once and use everywhere to grow a disciplined AI coding agent.",
6
6
  "keywords": [
7
7
  "ai",
@@ -97,7 +97,7 @@ condition first. Active voice, no -ing forms, no dropped articles, one word per
97
97
  <!-- LEAN:end -->
98
98
 
99
99
  ### {{DOCTRINE:mark-the-ask}} Mark the Ask
100
- <!-- note: summary: Mark an ask that waits on the user with an emoji and arrows; routine output stays plain. -->
100
+ <!-- note: summary: Mark an ask that waits on the user, and explain it when it is not clear alone; routine output stays plain. -->
101
101
  <!-- LEAN:begin -->
102
102
  When a reply stops and waits on the user — a question, a choice, an approval, a blocker —
103
103
  make the ask stand apart from the work around it, so a reader who skims finds it first. Open
@@ -111,11 +111,18 @@ the surface renders it, such as markdown or a rich host; never write ANSI escape
111
111
  markup into plain text that prints them raw. Routine output stays plain: a reply that waits
112
112
  on nothing carries no marker, and a marker on every line marks nothing. The markers are
113
113
  signs, not words, so the prose around them keeps {{DOCTRINE:simplified-technical-english}}.
114
+ Make the ask understood, not only seen. Before a command the user must run or approve, or a
115
+ question or a choice that is not clear by itself, write one or two plain lines: what it does,
116
+ why now, and what it changes or risks when that is not obvious. For a question, say what the
117
+ answer decides. An ask that is clear by itself stays bare: `ls`, or a yes/no question with no
118
+ stakes.
114
119
  <!-- LEAN:else -->
115
120
  When a reply waits on the user — a question, a choice, an approval, a blocker — mark the
116
121
  ask. Open it with one marker: `❓` question, `👉` act to do, `⚠️` risk or blocker, `✅` done,
117
122
  waits on sign-off; it comes before the code: `❓ **Q3** — keep the v1 route?`. Arrows (`→`)
118
123
  lay out options and flows, the recommended option first. One ask per block. Colour only
119
124
  where the host renders it, never raw ANSI in plain text. Routine output stays plain; markers
120
- are signs, not words.
125
+ are signs, not words. An ask that is not clear by itself carries one or two plain lines before
126
+ it: what it does, why now, what it changes or risks; for a question, what the answer decides.
127
+ A clear ask stays bare.
121
128
  <!-- LEAN:end -->