@jjanczur/tyran 0.1.34 → 0.1.35

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.34",
14
+ "version": "0.1.35",
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.34",
3
+ "version": "0.1.35",
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,31 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.35 — 2026-08-17
4
+
5
+ ### Three surfaces promised a consolidation step that nobody implements
6
+
7
+ `knowledge.mjs audit` printed, in its own output, *"/tyran:retro
8
+ consolidates, writing a NEW file for review"*. Both doc surfaces said the same.
9
+ Grep `skills/retro/SKILL.md` and `agents/retro.md`: there is no consolidation
10
+ step in either, and no such file has ever been written.
11
+
12
+ A tool that names a downstream step BY NAME is the last place a reader will
13
+ doubt it, which is how this survived on three surfaces at once — worse than
14
+ ADR-21's three spellings of one answer, because it is three spellings of a
15
+ NON-answer.
16
+
17
+ What the retrospective really does to `.tyran/knowledge/` is counter upkeep:
18
+ it folds each report's knowledge-brief verdicts into the entries' counters,
19
+ retires an entry the counters have written off, and splits one `doctor --state`
20
+ flags as `knowledge-entry-oversized`. **Merging two overlapping entries is
21
+ still yours**, and all three surfaces now say so.
22
+
23
+ Two tests, because correcting one surface was never going to be enough: the
24
+ audit's own output makes no such claim, and either doc growing it back fails
25
+ while `scripts/` has no consolidation — stepping aside automatically if
26
+ someone builds it, so the test blocks the false promise without blocking the
27
+ feature. It stays specced in `NOTES-REQUESTS.md` §12.2.
28
+
3
29
  ## 0.1.34 — 2026-08-17
4
30
 
5
31
  ### The dashboard starts itself
package/README.md CHANGED
@@ -309,7 +309,7 @@ enforces the cap (4352 of 5000 characters). What each one assumes, when it
309
309
  fires and who invokes it, is in
310
310
  [skills and agents](https://jjanczur.github.io/tyran/skills/); the prompts
311
311
  themselves are in [`skills/`](skills/) and [`agents/`](agents/). Behind all of
312
- it: 1569 unit tests, run with `node --test "tests/**/*.test.mjs"`.
312
+ it: 1571 unit tests, run with `node --test "tests/**/*.test.mjs"`.
313
313
 
314
314
  ## Documentation
315
315
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jjanczur/tyran",
3
- "version": "0.1.34",
3
+ "version": "0.1.35",
4
4
  "description": "Command-line scripts for the Tyran task conductor (doctor, journal, schema, and repo tooling) for CI and terminals outside Claude Code. Installing this package does NOT install the Claude Code plugin — add that separately with `/plugin marketplace add jjanczur/tyran` inside Claude Code.",
5
5
  "type": "module",
6
6
  "engines": {
@@ -313,7 +313,17 @@ function main() {
313
313
  // A measurement, never an edit: which of two overlapping entries is the
314
314
  // true one is a judgement, and a script that guessed would delete the
315
315
  // hard-won detail this exists to protect.
316
- out.push(' This reports; it never edits. /tyran:retro consolidates, writing a NEW file for review.');
316
+ //
317
+ // This line used to promise that `/tyran:retro` consolidates, writing a
318
+ // new file for review. It does not, and never has: grep the skill and the
319
+ // agent and there is no consolidation step in either. What the retro
320
+ // really does to this store is COUNTER upkeep — folding each report's
321
+ // brief verdicts in, retiring an entry the counters have written off, and
322
+ // splitting one `doctor` calls oversized. Merging two overlapping entries
323
+ // is nobody's job yet. Saying so is the point: a tool that names a
324
+ // downstream step by name is the last place a reader will doubt it.
325
+ out.push(' This reports; it never edits. Nothing merges overlapping entries yet — /tyran:retro');
326
+ out.push(' keeps the counters, retires what stopped earning its keep, and splits what is oversized.');
317
327
  process.stdout.write(out.join('\n') + '\n');
318
328
  process.exitCode = 0;
319
329
  return;