ticket-runner 0.6.4 → 0.6.5
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/README.ko.md +4 -4
- package/README.md +3 -3
- package/docs/templates/operator-skill.md +7 -7
- package/package.json +1 -1
- package/src/acceptance-criteria.ts +2 -2
- package/src/adapters/claude-agent-runner.ts +3 -3
- package/src/adapters/exec.ts +19 -4
- package/src/adapters/gh-tracker.ts +17 -17
- package/src/adapters/git-workspace.ts +12 -8
- package/src/adapters/liveness.ts +77 -0
- package/src/adapters/process-tree.ts +4 -7
- package/src/adapters/version.ts +5 -5
- package/src/branch.ts +1 -1
- package/src/cli.ts +2 -2
- package/src/config.ts +4 -4
- package/src/conventions.ts +21 -18
- package/src/credential.ts +14 -13
- package/src/criteria.ts +107 -15
- package/src/failing-base.ts +7 -7
- package/src/failure-message.ts +72 -0
- package/src/guards.ts +2 -2
- package/src/handoff.ts +2 -2
- package/src/init.ts +8 -8
- package/src/landing.ts +1 -1
- package/src/lifecycle.ts +2 -2
- package/src/lock.ts +10 -2
- package/src/note-schema.ts +3 -3
- package/src/notes.ts +8 -6
- package/src/operator-skill.ts +2 -2
- package/src/orchestrator.ts +168 -128
- package/src/ports/agent-runner.ts +1 -1
- package/src/ports/tracker.ts +14 -13
- package/src/ports/workspace.ts +23 -22
- package/src/progress.ts +2 -2
- package/src/prompts.ts +67 -24
- package/src/readiness.ts +11 -11
- package/src/remove.ts +7 -7
- package/src/resume.ts +12 -12
- package/src/run-log.ts +5 -5
- package/src/run.ts +7 -7
- package/src/staleness.ts +14 -14
- package/src/start.ts +17 -12
- package/src/stranded.ts +19 -19
- package/src/templates.ts +147 -66
- package/src/title.ts +44 -8
- package/src/verdict.ts +7 -7
- package/src/version-number.ts +13 -13
- package/src/version-pr.ts +12 -12
package/src/notes.ts
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
*
|
|
4
4
|
* A Stage that meets a defect in code it was not sent to touch has three bad
|
|
5
5
|
* options and one good one. Fixing it widens the Ticket past the Acceptance
|
|
6
|
-
* Criteria the
|
|
6
|
+
* Criteria the verdict grades. Ignoring it loses it. Writing it into the
|
|
7
7
|
* Ticket's own comments buries it under a Ticket that is about to close. So it
|
|
8
8
|
* records a **Note** instead, and the pipeline puts the Note where somebody
|
|
9
9
|
* will meet it: the comments of the Ticket it belongs to, or the standing
|
|
@@ -11,7 +11,7 @@
|
|
|
11
11
|
*
|
|
12
12
|
* Notes ride along with the structured output of the implement, verify and fix
|
|
13
13
|
* Stages: the two that write code, which meet what they were not sent to touch,
|
|
14
|
-
* and the one that grades, whose
|
|
14
|
+
* and the one that grades, whose verdict has a slot per Acceptance Criterion and
|
|
15
15
|
* none for anything else it found. A Stage with nothing to report emits an empty
|
|
16
16
|
* list and is not treated differently for it.
|
|
17
17
|
*/
|
|
@@ -61,7 +61,7 @@ export interface RoutedNote {
|
|
|
61
61
|
origin: number;
|
|
62
62
|
/**
|
|
63
63
|
* The Stage that made it, or the pipeline itself: the one Note no Stage
|
|
64
|
-
* writes is the pipeline's, about a
|
|
64
|
+
* writes is the pipeline's, about a base branch failing a Check.
|
|
65
65
|
*/
|
|
66
66
|
stage: NotingStage | "pipeline";
|
|
67
67
|
/** The issue the Note reached: the Ticket it named, or the standing Notes issue. */
|
|
@@ -378,9 +378,11 @@ async function route(routing: NoteRouting, note: Note): Promise<RoutedNote> {
|
|
|
378
378
|
return { origin, stage, issue: ticket, opened: false, summary: text.summary };
|
|
379
379
|
}
|
|
380
380
|
} catch (error) {
|
|
381
|
+
// The message last, as every other event logs one, so what a failed
|
|
382
|
+
// command printed follows the line it is printed under.
|
|
381
383
|
routing.log?.(
|
|
382
|
-
`#${origin} could not comment its Note on #${ticket} ` +
|
|
383
|
-
|
|
384
|
+
`#${origin} could not comment its Note on #${ticket}, sending it to triage instead: ` +
|
|
385
|
+
(error as Error).message,
|
|
384
386
|
);
|
|
385
387
|
return await sendToTriage(routing, { ...from, intended: ticket });
|
|
386
388
|
}
|
|
@@ -400,7 +402,7 @@ async function route(routing: NoteRouting, note: Note): Promise<RoutedNote> {
|
|
|
400
402
|
* finishes with, after `which`.
|
|
401
403
|
*
|
|
402
404
|
* Claimed is the label alone, not the assignee with it: the pipeline's own
|
|
403
|
-
*
|
|
405
|
+
* claim writes both, but a human who took a Ticket may have written only the
|
|
404
406
|
* label, and either way there is somebody on it.
|
|
405
407
|
*/
|
|
406
408
|
async function buriedOn(routing: NoteRouting, ticket: number): Promise<string | undefined> {
|
package/src/operator-skill.ts
CHANGED
|
@@ -11,8 +11,8 @@ import { readFileSync } from "node:fs";
|
|
|
11
11
|
* Its text is a shape like every other the pipeline writes, so it lives with
|
|
12
12
|
* them in `docs/templates/`, and it is read from there rather than copied into
|
|
13
13
|
* this module: the package carries that one file for this. The text names no
|
|
14
|
-
*
|
|
15
|
-
* mark, so a Target is never rewritten for a
|
|
14
|
+
* version. The Operator reads the one to install off the conventions document's
|
|
15
|
+
* mark, so a Target is never rewritten for a version that changed nothing here.
|
|
16
16
|
*/
|
|
17
17
|
|
|
18
18
|
/** Where the skill goes in a Target, relative to the Target's root. */
|