@jjanczur/tyran 0.1.18 → 0.1.20

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.
@@ -11,7 +11,7 @@
11
11
  {
12
12
  "name": "tyran",
13
13
  "description": "A task conductor for Claude Code: multi-agent orchestration with an enforced evidence contract, repo-specific learning, and update-safe local evolution.",
14
- "version": "0.1.18",
14
+ "version": "0.1.20",
15
15
  "source": "./",
16
16
  "author": {
17
17
  "name": "Jacek Janczura",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tyran",
3
- "version": "0.1.18",
3
+ "version": "0.1.20",
4
4
  "description": "A task conductor for Claude Code: multi-agent orchestration with an enforced evidence contract, repo-specific learning, and update-safe local evolution.",
5
5
  "author": {
6
6
  "name": "Jacek Janczura",
package/CHANGELOG.md CHANGED
@@ -1,5 +1,119 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.20 — 2026-08-14
4
+
5
+ ### `.tyran/` was tracked, and an entire initiative inside it was not
6
+
7
+ `untrackedTyranDir` was all-or-nothing: one tracked file anywhere under
8
+ `.tyran/` and the whole directory reported healthy. Measured on a real install
9
+ whose `.tyran/` had been tracked for weeks — one initiative directory of six
10
+ files, its plan and the gate event recording two production database migrations
11
+ among them, had NEVER been committed, and a second was 33 events behind its
12
+ committed copy. Both passed. `journal.mjs append` writes the working tree and
13
+ nothing else, so an initiative nobody committed is one `git clean -fd` from
14
+ having never happened.
15
+
16
+ `doctor --state` now reads each initiative's ledger separately, in three states
17
+ rather than two:
18
+
19
+ - `initiative-untracked` (**warning**) — git has never seen it.
20
+ - `initiative-ignored` (**warning**) — a `.gitignore` rule covers it. Split out
21
+ because `git add` on an ignored path exits 0 and stages nothing, so the
22
+ untracked fix would have read as success while changing nothing.
23
+ - `initiative-uncommitted` (**info**, never fails the check) — tracked with
24
+ local changes, which is what an initiative in flight looks like ten seconds
25
+ after any append. It earns its keep at a merge boundary.
26
+
27
+ Two git invocations for the whole tree, not two per initiative: both listings
28
+ are read once and classified by path prefix in JS, so a repo with forty
29
+ initiatives costs the same three subprocesses as one with a single initiative
30
+ — and a test counts them, because that regression passes every behavioural
31
+ test there is. Under a wholly untracked `.tyran/` the directory-level finding
32
+ still reports alone rather than repeating itself once per initiative with
33
+ narrower advice each time.
34
+
35
+ ### Four things the conductor skill was letting agents rediscover
36
+
37
+ - **Interactive shell aliases hang an agent until the tool timeout.** An
38
+ agent's shell starts from the user's profile, so `alias cp='cp -i'` asks a
39
+ question nobody answers. The symptom is a timeout, which points at the
40
+ machine rather than at the alias, so it gets rediscovered every time: three
41
+ agents in one session, then again in a later one that had already read the
42
+ file it is now written in. STEP 0 probes for it.
43
+ - **A `Test timed out` measured under concurrency is not evidence.** The
44
+ hardware ceiling bounds agent count, not concurrent heavy phases. Re-run
45
+ serially and report the serial result. One overnight test failed exactly
46
+ that way inside the full suite while this release was being verified, and
47
+ passed alone.
48
+ - **An agent that dies on a terminal API error is resumed, not respawned** —
49
+ its context, its corrected premises and its uncommitted diff all survive.
50
+ - **Gitignored env files are absent from a fresh worktree too, and fail
51
+ quieter than dependencies**: 127 is loud, a skipped gated spec is not, so the
52
+ worktree reports a *cleaner* baseline than the repo has.
53
+
54
+ ### The README says what Tyran is, and the docs it links are the published ones
55
+
56
+ - **"What Tyran is" rewritten** to open on the failure a reader recognises — a
57
+ full context window, a plan somewhere in the scrollback, "the tests pass" as
58
+ a sentence rather than a result — before naming the mechanism that answers
59
+ it.
60
+ - **The named comparison is back on the front page.** Five rows of the eleven
61
+ in the FAQ, copied verbatim, plus a test that fails if a verdict moves in one
62
+ and not the other. The `Skills · agents it ships` row and the guard pinning
63
+ it were deleted rather than updated: the table under it and the sentence
64
+ under that already carry the same count, and three spellings of one answer is
65
+ the defect this repo calls ADR-21 — a test can hold one in place as easily as
66
+ prose can.
67
+ - **Every documentation link now points at the published site** rather than at
68
+ a markdown file: twenty in the README, three inside skills, and four in
69
+ `doctor`'s own fix lines — which reach repos that have no `docs/` directory
70
+ at all, where `see docs/journal.md` was a dead reference.
71
+ - **The Node version is stated once, where it applies.** It sat in the lede and
72
+ in the install section, neither of which runs Node: the scripts ship with the
73
+ plugin and Claude Code runs them. It now sits beside the one command that
74
+ needs it, `npx @jjanczur/tyran board`.
75
+ - **The dashboard GIF runs at 4 fps instead of 8.3** — the same recording, at a
76
+ speed a tab can actually be read at.
77
+
78
+ ## 0.1.19 — 2026-08-14
79
+
80
+ ### The board answered four questions on one scroll
81
+
82
+ `board.html` is now four tabs. **Overview** — what is waiting on you, agents
83
+ running, progress, tickets that need a human, then the agent strip. **Board** —
84
+ the kanban lanes, where every card is a button that opens a detail panel
85
+ carrying its lane, initiative, agents, note and, once spend has loaded, that
86
+ ticket's tokens and cost. **Waiting on you** — the queue, with the three
87
+ commands that answer it printed above the questions, and its open count in the
88
+ tab label so a pending decision survives being on another tab. **Spend** —
89
+ unchanged in substance, still FETCHED rather than embedded, so `board.json` and
90
+ `board.html` keep their byte-exact `--check` contract.
91
+
92
+ The palette is pulled back. The first version filled whole bars and whole cards
93
+ at full saturation, which reads as an alarm rather than as information. The
94
+ roles are unchanged — one warm accent for the operator's call to action, a cool
95
+ one for the agent strip, red for refusal, green for the ledger's `+` — but
96
+ saturation is now spent on text, edges and 3px rails, and every large fill is a
97
+ muted tone of the same hue. The tokens are `--brass`, `--steel`, `--clay`,
98
+ `--sage`.
99
+
100
+ ### The README explained the problem before it explained the product
101
+
102
+ Rebuilt, 491 lines to 204: what Tyran is, a recorded demo of the board, what it
103
+ gives you, a comparison, install, use, the dashboard. Everything cut was first
104
+ given a home on BOTH doc surfaces — nine sections that lived nowhere else were
105
+ moved rather than deleted, and four inbound links that pointed at README
106
+ anchors now resolve inside `docs/`.
107
+
108
+ The version badge read GitHub Releases, where the newest was 0.1.3 while
109
+ sixteen versions had shipped by tag and by npm. It now reads npm, which the
110
+ release itself maintains and which cannot go stale.
111
+
112
+ **Upgrading: regenerate your board.** `board.html` changed again, so
113
+ `board.mjs --check` reports drift until you run
114
+ `node scripts/board.mjs --dir .tyran` and commit. `board.json` and `BOARD.md`
115
+ are unchanged.
116
+
3
117
  ## 0.1.18 — 2026-08-14
4
118
 
5
119
  ### The spend ledger: nobody could say what a run cost