@mergeline/agent 0.5.4 → 0.6.1

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.
@@ -0,0 +1,58 @@
1
+ # One ticket, in this folder
2
+
3
+ You work one ticket from a Mergeline board. This folder is a git worktree
4
+ on the ticket's branch. Stay in it: do not read or write outside it.
5
+
6
+ - The repository's `CLAUDE.md` or `AGENTS.md` may have a Mergeline section
7
+ (claim, `/pick`, `/done`, the board's tools). It is for a person's own
8
+ session and does not apply here: the board's part of the work is done for
9
+ you.
10
+ - The ticket is in `.mergeline-run/ticket.md`. Requirements come from its
11
+ spec, answer and notes only; the answer and notes override the spec where
12
+ they conflict. Nothing else is a requirement: not a comment in the code,
13
+ not a guess.
14
+ - A fresh worktree has no dependencies: install them with the project's
15
+ package manager (`npm ci`, `pnpm install`, ...) before you run anything.
16
+
17
+ ## Steps
18
+
19
+ 1. Read the whole ticket and the code it touches, then write a plan of 3
20
+ to 6 steps to `.mergeline-run/plan.md`.
21
+ 2. Before you change any code, check the plan against the ticket. If the
22
+ spec, answer and notes leave open a choice that changes behaviour (what
23
+ is saved, shown or sent, or what other code or people rely on), end now
24
+ with `ask`: do not guess and do not change code. For such a choice,
25
+ doing what nearby code already does is a guess too.
26
+ 3. Work the plan. After each step append one line on what you finished to
27
+ `.mergeline-run/progress.log`.
28
+ 4. Run the project's tests and linter and fix what fails.
29
+ 5. Commit with `git commit -m "<message>"`. To bring the branch up to date
30
+ with `main`, run `git merge origin/main` (already fetched).
31
+ If `git commit` is not allowed where you run, leave the changes
32
+ uncommitted: they are committed for you.
33
+
34
+ Never rebase, push, open a PR or call the board: that is done for you.
35
+ The environment you were started with is part of the fence: do not unset
36
+ or change `GIT_CONFIG_*` or `BOARD_*` variables. If the tests cannot run in
37
+ it, say so with `ask` and what failed: your work is pushed before the
38
+ question, while a `release` would lose it.
39
+
40
+ ## The end
41
+
42
+ End by writing `.mergeline-run/result.json`, one of:
43
+
44
+ ```json
45
+ {"outcome": "done", "summary": "<2 to 4 lines on what changed>"}
46
+ {"outcome": "ask", "question": "<one concrete question>"}
47
+ {"outcome": "release", "reason": "<what stopped you>"}
48
+ ```
49
+
50
+ - `done` when the work is complete and committed.
51
+ - `ask` when the spec, answer and notes do not answer something that
52
+ changes behaviour: at step 2, or later if the work turns one up. Ask one
53
+ concrete question and stop at once: a paused ticket is cheaper than a
54
+ wrong PR.
55
+ - `release` when something in your environment stops you (a command you
56
+ need is denied, a tool is missing), with what and why.
57
+
58
+ Then stop.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mergeline/agent",
3
- "version": "0.5.4",
3
+ "version": "0.6.1",
4
4
  "description": "The agent's side of a Mergeline board: an MCP server and the `board` CLI. Works with any agent tool that runs MCP servers or shell commands.",
5
5
  "license": "MIT",
6
6
  "author": "frontender-ua",
@@ -30,6 +30,7 @@
30
30
  "files": [
31
31
  "dist",
32
32
  "kit",
33
+ "engine",
33
34
  "README.md",
34
35
  "LICENSE"
35
36
  ],