@jjanczur/tyran 0.1.5 → 0.1.6

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.5",
14
+ "version": "0.1.6",
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.5",
3
+ "version": "0.1.6",
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,40 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.6 — 2026-08-06
4
+
5
+ ### A browser pass must follow the value to what got STORED
6
+
7
+ A column-mapping override shipped with a perfect `browser-check` measurement —
8
+ 15/15 columns visible, 0 console errors, the mapping visibly changed by hand —
9
+ and was completely inert. The server re-derived the source type from the
10
+ uploaded bytes, discarded the client's mapping, and answered `201` either way.
11
+ Nothing in the browser pass could have caught it, because it never inspected
12
+ what the server persisted; a reviewer reading the route did.
13
+
14
+ `browser-check` now says so: when the UI claims to change something the SERVER
15
+ acts on, a clean console and a `2xx` are not proof it arrived. Capture the
16
+ request body you actually sent, or read the value back with a second request or
17
+ a reload, and assert on THAT. The evidence contract already pinned the
18
+ execution MODE (dev server vs production build); it said nothing about
19
+ following a value past the response into storage.
20
+
21
+ ### A reviewer must never restore an uncommitted tree with git
22
+
23
+ Breaking the fix to watch its test fail is the right way to prove a guard is
24
+ real. The restore is the foot-gun: the work under review is UNCOMMITTED, so
25
+ `git checkout -- <file>`, `git restore` and `git stash` all revert to HEAD and
26
+ destroy the very thing the reviewer was sent to review. Measured in the field —
27
+ a reviewer did exactly this, caught it by re-diffing, and recovered only
28
+ because it had taken a backup first. Without the backup the author's work is
29
+ gone with no record of what was in it.
30
+
31
+ `agents/reviewer.md` now carries the procedure: copy to a scratch path, restore
32
+ from the copy, prove the restore with `diff`, then disclose the mutation in the
33
+ report. The agent already knew it had no edit tools "on purpose" and that
34
+ `Bash` can still write — what it lacked was the one sequence where its own
35
+ correct technique destroys the subject.
36
+
37
+
3
38
  ## 0.1.5 — 2026-08-03
4
39
 
5
40
  ### The plugin loads again (0.1.4 did not)
@@ -31,6 +31,16 @@ that keeps you.
31
31
  - Warm up routes before a batch run; a cold compile reads as a failure.
32
32
  - Take heavy slots only through the lease protocol, and clean up your
33
33
  processes afterwards (SIGTERM, not `kill -9`).
34
+ - **To prove a guard is real, break the fix — but never restore with git.**
35
+ Neutering the change to watch its test fail is the right technique. The
36
+ restore is where it goes wrong: the work under review is UNCOMMITTED, so
37
+ `git checkout -- <file>`, `git restore` and `git stash` all revert to
38
+ HEAD and destroy the very thing you were sent to review. Copy the file to
39
+ a scratch path first, restore from that copy, and prove the restore with
40
+ `diff` before you carry on. Then DISCLOSE the mutation in your report.
41
+ Measured: a reviewer did exactly this, caught it by re-diffing, and
42
+ recovered only because it had taken the backup — the same sequence
43
+ without one loses the author's work with no record of what was in it.
34
44
  3. **Check the optimization section** — whether what the author claims is
35
45
  genuinely in the code, not just in the write-up.
36
46
  4. **The verdict is binary.** APPROVE, with minor notes routed to `NOTES.md`;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jjanczur/tyran",
3
- "version": "0.1.5",
3
+ "version": "0.1.6",
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": {
@@ -57,6 +57,18 @@ Return them as **counts plus the first few offenders**, then a single verdict
57
57
  line. A pass with `0` console errors is a fact; "the console was clean" is a
58
58
  recollection.
59
59
 
60
+ **When the UI claims to change something the SERVER acts on** — a mapping, a
61
+ setting, a value the next request depends on — a clean console and a `2xx` are
62
+ not proof it arrived. The evidence has to follow the value to what got STORED,
63
+ not stop at what got RENDERED: capture the request body you actually sent, or
64
+ read the value back with a second request or a reload, and assert on THAT. This
65
+ is not hypothetical. A column-mapping override shipped with a perfect browser
66
+ pass — 15/15 columns visible, 0 console errors, the mapping visibly changed by
67
+ hand — while the server re-derived the source type from the uploaded bytes and
68
+ discarded the mapping, answering `201` either way. Only a reviewer reading the
69
+ server route caught it; nothing in the browser measurement could have, because
70
+ it never inspected what the server persisted.
71
+
60
72
  ## Selectors that do not go blind
61
73
 
62
74
  Anchor on what the user sees — a role, a label, the text — not on a container