@skitterbyte/skitterspec-jira 2.16.0 → 2.17.0

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.
@@ -579,10 +579,9 @@ line with it where the engine printed one, and nothing where it did not.
579
579
  `.claude/rules/spec-reports.md` carries the shape, including why a rigid
580
580
  contract took that line.
581
581
 
582
- - **Never write the review unasked**, and **never publish**. Publishing leaves
583
- something behind that this tooling cannot remove, so it is always an ask. A
584
- `file://` link is no use on a phone, and saying so **is** the ask —
585
- `/spec-diff` §6 owns how.
582
+ - **Never write the review unasked**, and **never publish** — there is no
583
+ publishing (`/spec-diff` §6). A `file://` link is no use on a phone, and the
584
+ stack says why nothing was served.
586
585
  **The `reader:` line no longer decides anything here, and that is the point.**
587
586
  It is still printed, and it is still the only place that question is answered —
588
587
  but the offer does not change with it, because the stack lists every tier
@@ -592,22 +591,20 @@ that branching is exactly what produced a `file://` page on a session detected
592
591
  underneath a reader when detection flipped mid-session.
593
592
 
594
593
  So: **relay all three tier lines, every time.** Any `also:` lines sit under
595
- `network` — the other addresses this machine has, offered because the
596
- best-guess one can be wrong — so pass them on rather than editing them out: in
597
- the banner they are indented sub-bullets under **network**, labels
598
- (`(tailnet)`) included, exactly as `.claude/rules/spec-reports.md` shows.
594
+ their tier — the other addresses this machine has of that kind — so pass them
595
+ on rather than editing them out: in the banner they are indented sub-bullets
596
+ under that tier, labels included, exactly as `.claude/rules/spec-reports.md`
597
+ shows.
599
598
 
600
599
  **Never read an environment variable to decide anything about the offer** — not
601
600
  `SSH_CONNECTION`, not `CLAUDE_CODE_*`, not a tty check. There is nothing left
602
601
  here for a detection to decide, and a second implementation of one could not be
603
602
  tested and would drift.
604
603
 
605
- **Serving is the engine's to do; publishing is never.** A `remote` reader
604
+ **Serving is the engine's to do, and there is nothing else.** A `remote` reader
606
605
  authorises a local server — one process, ended by one flag, leaving nothing
607
- behind — and authorises nothing else. Publishing leaves a page this tooling
608
- cannot remove, so it stays an ask in every case, always. If the engine could not
609
- serve (a busy port, a machine with no network address) it falls back to the
610
- `file://` URL with its marker, and that is when publishing is worth naming.
606
+ behind. If the engine could not serve (a busy port, a machine with no network
607
+ address) it falls back to the `file://` URL with its marker.
611
608
 
612
609
  - **Never fatal.** A failed render — no worktree, a git error — is one line, and
613
610
  the fix is still done. The page is a convenience; the repo is the record.
@@ -14,11 +14,11 @@ A phase is built in its own worktree, and the terminal is somewhere else — so
14
14
  `git diff` answers about the wrong branch and a 350-line diff read as terminal
15
15
  text is scrolling, not review. This renders the diff as a page instead: the
16
16
  engine collects it with `git -C`, writes a self-contained HTML file, and you open
17
- it locally or publish it and read it on a phone.
17
+ it locally, or on a phone over your LAN or tailnet.
18
18
 
19
19
  **The diff never passes through the model.** git writes the patches and the
20
20
  engine splices them into the page. A 266KB patch costs **zero** context tokens,
21
- and a 289KB page costs the same to publish as a 5KB one. Do not "simplify" this
21
+ and a 289KB page costs the same to serve as a 5KB one. Do not "simplify" this
22
22
  by reading the diff and emitting HTML — that is the one change that would undo
23
23
  the whole design.
24
24
 
@@ -354,8 +354,8 @@ spend it.
354
354
 
355
355
  ## 2b. An action changes something, then hands the page back
356
356
 
357
- Only on a pass carrying an **action**. Three of them, and
358
- **all three end the same way**:
357
+ Only on a pass carrying an **action**. Two of them, and
358
+ **both end the same way**:
359
359
  do the thing, re-render (§4), and wait again (§4b) — because the reader
360
360
  still has a decision in front of them and has not made it.
361
361
 
@@ -363,7 +363,11 @@ still has a decision in front of them and has not made it.
363
363
  |--------|----|------|
364
364
  | `live-on` | commit first (below), then `skitterspec spec-env live take <spec>` | re-render `--branch`, wait again |
365
365
  | `allow-network` | `skitterspec spec-env review allow network` | re-render, wait again |
366
- | `allow-remote` | `skitterspec spec-env review allow remote <spec> --set on` | publish (§6), re-render, wait again |
366
+
367
+ **There is no `allow-remote` either.** It permitted publishing the page as a
368
+ claude.ai artifact, and that tier was retired (feat-tailnet-remote-tier):
369
+ `remote` is the tailnet address now, on `network`'s switch, so `allow-network`
370
+ turns both on.
367
371
 
368
372
  **THERE IS NO `live-off`, and its absence is deliberate.** Putting *this* change
369
373
  live is about the diff on screen; handing the whole instance back to `main` is a
@@ -371,7 +375,7 @@ workspace decision with nothing to do with this review. The `live:` line names
371
375
  `/spec-live main` for it — a command the operator types, which is also why no
372
376
  skill runs it.
373
377
 
374
- **AN ACTION IS NOT A VERDICT, and the gate is untouched by all three.** A phase
378
+ **AN ACTION IS NOT A VERDICT, and the gate is untouched by both.** A phase
375
379
  that ended armed the gate, and it is discharged by a committing verdict or a
376
380
  recorded skip and by nothing else — so after any of these the phase still owes
377
381
  an answer, and that is exactly why the run waits again rather than finishing.
@@ -425,17 +429,9 @@ edits `specs/.core/env.config.json` in the **primary checkout**, so it changes
425
429
  behaviour for everyone who pulls and leaves that tree dirty — one server binds
426
430
  for every spec, so the bind cannot be narrower. The engine prints the absolute
427
431
  path; relay that rather than letting a shared setting change land silently.
428
- **`allow remote` is per spec** and writes only a gitignored sidecar beside the
429
- page, so the base branch stays clean and no other spec may publish. And it is **enable-only**: there is no
430
- action that turns a tier off, because turning `network` off from a page reached
431
- over the network kills the page doing the turning.
432
-
433
- **`allow remote` permits publishing. It does not publish by itself.**
434
- Publishing stays an explicit ask (§6), because the page it leaves behind is one
435
- this tooling cannot remove. A reader who presses `Allow remote` on the page, or
436
- types `/spec-remote-review` beside a waiting review, **has** asked: the engine
437
- names the page on its `review:`/`publish:` lines, and that page is published
438
- and the stack re-shown. Nothing it does not name is published.
432
+ And it is **enable-only**: there is no action that turns a tier off, because
433
+ turning `network` off from a page reached over the network kills the page doing
434
+ the turning.
439
435
 
440
436
  ## 3. Gate it on nothing
441
437
 
@@ -493,7 +489,7 @@ could not run is that strip's business rather than yours.
493
489
 
494
490
  **There is no switch left to handle.** The engine serves and prints a **stack** —
495
491
  one line per tier, `local`, `network`, `remote`, each either a URL or the one
496
- command that turns it on. All of it is free and none of it publishes anything.
492
+ command that turns it on. All of it is free, and all of it is one server.
497
493
  You are not choosing between them; you are relaying every line it printed.
498
494
  `.claude/rules/spec-reports.md` carries the shape and why.
499
495
 
@@ -564,7 +560,7 @@ says:
564
560
  |------|---------|
565
561
  | `local` | the loopback URL — or the `file://` page when nothing served, which says it cannot send a verdict |
566
562
  | `network` | the LAN URL and any `also:` alternates under it — or `off` with the command that turns it on |
567
- | `remote` | the published URL and *a verdict here needs `/spec-reviewed`* — or `off` with the command that turns it on |
563
+ | `remote` | the tailnet URL, labelled `(tailnet)` — or `off` with `network`'s command, or `no tailnet address on this machine` |
568
564
 
569
565
  **The `reader:` line decides nothing here any more.** It is still printed and
570
566
  still the only place that question is answered, but the offer no longer branches
@@ -581,23 +577,20 @@ tested and would drift. The ranking and the traps
581
577
  a tty under Claude Code) live in `review.js` beside the code, which is where they
582
578
  belong.
583
579
 
584
- **It authorises serving, never publishing.** A `remote` reader authorises a
585
- local server — one process, ended by one flag, leaving nothing behind — and
586
- nothing more. Publishing leaves a page this tooling cannot remove, so it is an
587
- ask, in every case, always. The two were once one rule, and lumping them together
588
- is what left a remote reader holding a dead link: see
589
- `specs/complete/bug-remote-reader-gets-a-dead-link/`.
580
+ **It authorises serving, and serving is all there is.** A `remote` reader
581
+ authorises a local server — one process, ended by one flag, leaving nothing
582
+ behind. Publishing the page was once a second answer and was retired with the
583
+ published tier (feat-tailnet-remote-tier): the tailnet reaches a reader off the
584
+ wifi without a page this tooling could never remove.
590
585
 
591
586
  When serving fails — a busy port, or a machine with no network address — the
592
- engine falls back to the `file://` URL with its marker and nothing breaks. That
593
- is the one case where naming publishing is worth doing, because it is the only
594
- answer left.
587
+ engine falls back to the `file://` URL with its marker and nothing breaks.
595
588
 
596
589
  `review.reader` in `env.config.json` (`local` · `remote` · `detect`) lets the
597
590
  operator settle where they are reading, and an explicit value is believed without
598
591
  sniffing. What the engine may *do* is settled by the tier settings instead —
599
- `review.serve` (`always` · `never`), `review.allowNetwork` and
600
- `review.allowRemote` — not by the reader.
592
+ `review.serve` (`always` · `never`) and `review.allowNetwork` — not by the
593
+ reader.
601
594
 
602
595
  ## 4b. Wait for the verdict — because asking for one means waiting for it
603
596
 
@@ -623,9 +616,6 @@ transport only decides what carries the answer back:
623
616
  - **A `file://` page** has nothing to post to, so the reader pastes the pass and
624
617
  their next message carries it. Say you are holding and **end the turn** — that
625
618
  is the same wait, carried by the conversation. It is not a lesser one.
626
- - **A published page** writes to the artifact's own store, which nothing reaches
627
- from here. That is the one case where the honest sentence is *press a verdict,
628
- then type `/spec-reviewed`* — see the published-page paragraph below.
629
619
 
630
620
  **Do not ask, and therefore do not wait, on a render nobody is waiting behind** —
631
621
  a bare `--page-only`, a page produced alongside other work, a pass that has
@@ -673,18 +663,15 @@ the stranger's pass the old rule was written about, and two arrivals refuse
673
663
  rather than pick. What is left of the old rule is unchanged and still absolute —
674
664
  outside this window, a pass is claimed because a person named it.
675
665
 
676
- **The wait covers the SERVED page and nothing else.** It watches the engine's
677
- local store, which is where a served page POSTs. A **published** page writes to
678
- the artifact's own store instead, and no watch of any kind reaches that — so a
679
- verdict pressed there is invisible until someone asks for it. Never start a
680
- wait and then hand over a published link under it: that reads as a promise to
681
- notice, and it was made three times in a row while three verdicts sat unread.
682
- Where the page is published, say plainly that `/spec-reviewed` is what picks it
683
- up.
666
+ **The wait covers every served door.** It watches the engine's local store,
667
+ which is where a served page POSTs — from `local`, `network` or `remote` alike,
668
+ since all three are the same server. A published page once wrote to a store no
669
+ watch reached, and three verdicts sat unread under a line claiming the run was
670
+ waiting; that is why the published tier was retired rather than caveated.
684
671
 
685
672
  **`/spec-reviewed` is not replaced by this.** It stays the way in for a pass
686
- that arrived when nobody was waiting, for the two-passes case, and for every
687
- published page. It is user-only, and that is still the
673
+ that arrived when nobody was waiting, and for the two-passes case. It is
674
+ user-only, and that is still the
688
675
  enforcement that makes a named claim a person's decision.
689
676
 
690
677
  **A harness with no file-watch is no longer on that list**, and that is the
@@ -743,78 +730,23 @@ Then re-render with it spliced in — the engine renders it, you never emit HTML
743
730
  skitterspec spec-env review <spec> --review <file>
744
731
  ```
745
732
 
746
- ## 6. Publish only when asked
747
-
748
- **Never publish unprompted.** Publishing leaves something behind that this
749
- tooling cannot remove, and the page already works as a local file. Offer it;
750
- do not assume it.
751
-
752
- When the user asks:
753
-
754
- - **One spec is one page.** `--json` reports `url` when this spec has been
755
- published before. If it has, **update that URL** rather than creating a
756
- second entry, and label the new version for the phase (`phase-3`).
757
- - **On the first publish**, write the returned URL to the path `--json` reports
758
- as `urlFile` — one line, no formatting. That file is how every later phase
759
- finds the same page. Never construct the path yourself.
760
- - **Say, once, that it is theirs now.** When you report a URL, say in the same
761
- breath that skitterspec cannot remove the page and that `/artifacts` (or the
762
- gallery at `claude.ai/code/artifacts`) is where it goes. This is the moment the
763
- decision is being made, so it is the moment worth saying it — `spec-env down`
764
- repeats it at teardown, by which point the page has outlived the spec.
765
- - **Degrade in one line.** If the harness cannot publish — no capability, an
766
- error — say so, report the local file path, and carry on. That is a working
767
- outcome, not a failure.
768
- - **Reach for `--publish-copy`, never a hand transform.** The engine writes the
769
- page as a complete HTML document and an artifact host wraps page *content*, so
770
- publishing the page as-written nests two documents. `spec-env review <spec>
771
- --publish-copy` emits the body-only copy and names its path on a `publish:`
772
- line. Do not split the document yourself: a rendered page contains the diff,
773
- and a diff of this project contains `<!doctype html>` as ordinary patch text.
774
-
775
- The engine knows nothing about publishing and cannot do it. It writes a file and
776
- reads a URL back as an opaque string; everything about what that string means
777
- lives here.
778
-
779
- ### Publish it so the buttons still work
780
-
781
- A published page is the answer for a reader **no local server can reach** — a
782
- phone on mobile data, anyone away from the LAN the engine serves on. It is also
783
- the one surface where the verdict buttons have nowhere to POST: the page's own
784
- URL is on claude.ai, so a POST fails and the reader gets "could not reach the
785
- server" after pressing a verdict they meant.
786
-
787
- So **publish it with a store**, and the page uses it:
788
-
789
- - Declare `capabilities: {db: {}}`. The page checks for `window.claude.use` and
790
- writes the pass into the artifact's own `passes` collection instead of
791
- POSTing. Nothing else about it changes — same marks, same verdicts, same
792
- refusal to commit over an open comment.
793
- - **Do not declare `user`.** The pass is not per-viewer private state, a shared
794
- collection is what it wants, and a declaration nothing uses is a grant asked
795
- for nothing.
796
- - **Same file path every time**, so a redeploy reuses the URL. That is what
797
- answers the clear-down worry: one page per spec, replaced at each render,
798
- rather than an artifact per phase accumulating in the gallery.
799
- - **Send a push notification with the URL** when you publish. The reader is by
800
- definition somewhere else — that is why it was published.
801
-
802
- ### Taking a stored pass back
803
-
804
- A pass in the store is claimed the same way in spirit and a different way in
805
- mechanism, because the engine cannot see it:
806
-
807
- 1. Read the `passes` collection with the Artifact tool's `read_db`.
808
- 2. **Apply step 0 unchanged.** One waiting pass, offered by what it says and
809
- when it was sent; two is a refusal to guess. Nothing here is automatic —
810
- there is no wait window on this transport, because nothing pushes from the
811
- store to this conversation.
812
- 3. Write the pass's `blob` to a scratch file **verbatim** and merge it with
813
- `spec-env review <spec> --notes <file>`. It rejoins the ordinary path at §2
814
- step 1, so the verdict is judged and routed exactly as any other.
815
- 4. **Delete the document** with `write_db` once it is merged. A claim consumes:
816
- a pass left in the store is claimable twice, which is the one property the
817
- six-digit code has always had and this transport must not lose.
733
+ ## 6. There is no publishing
734
+
735
+ **This skill does not publish the page, and nothing in this workflow does.**
736
+ Publishing it as a claude.ai artifact was retired with the published tier
737
+ (feat-tailnet-remote-tier). It wrote to a store no wait could watch, and left a
738
+ page this tooling could never remove. A reader off the wifi opens the `remote`
739
+ line — the review server's tailnet address — and sends the verdict into the
740
+ same store as every other door.
741
+
742
+ **Where no door reaches the reader** — no network, no tailnet, a server that
743
+ could not start — say so plainly with the stack the engine printed, and stop.
744
+ Do not reach for the Artifact tool as a fallback: that is the second store this
745
+ design removed.
746
+
747
+ A page published before this change still exists, and teardown still names it
748
+ (`spec-env down` reads the `.url` sidecar it left). Nothing writes that sidecar
749
+ any more.
818
750
 
819
751
  ## 7. Report
820
752
 
@@ -593,10 +593,9 @@ line with it where the engine printed one, and nothing where it did not.
593
593
  `.claude/rules/spec-reports.md` carries the shape, including why a rigid
594
594
  contract took that line.
595
595
 
596
- - **Never write the review unasked**, and **never publish**. Publishing leaves
597
- something behind that this tooling cannot remove, so it is always an ask. A
598
- `file://` link is no use on a phone, and saying so **is** the ask —
599
- `/spec-diff` §6 owns how.
596
+ - **Never write the review unasked**, and **never publish** — there is no
597
+ publishing (`/spec-diff` §6). A `file://` link is no use on a phone, and the
598
+ stack says why nothing was served.
600
599
  **The `reader:` line no longer decides anything here, and that is the point.**
601
600
  It is still printed, and it is still the only place that question is answered —
602
601
  but the offer does not change with it, because the stack lists every tier
@@ -606,22 +605,20 @@ that branching is exactly what produced a `file://` page on a session detected
606
605
  underneath a reader when detection flipped mid-session.
607
606
 
608
607
  So: **relay all three tier lines, every time.** Any `also:` lines sit under
609
- `network` — the other addresses this machine has, offered because the
610
- best-guess one can be wrong — so pass them on rather than editing them out: in
611
- the banner they are indented sub-bullets under **network**, labels
612
- (`(tailnet)`) included, exactly as `.claude/rules/spec-reports.md` shows.
608
+ their tier — the other addresses this machine has of that kind — so pass them
609
+ on rather than editing them out: in the banner they are indented sub-bullets
610
+ under that tier, labels included, exactly as `.claude/rules/spec-reports.md`
611
+ shows.
613
612
 
614
613
  **Never read an environment variable to decide anything about the offer** — not
615
614
  `SSH_CONNECTION`, not `CLAUDE_CODE_*`, not a tty check. There is nothing left
616
615
  here for a detection to decide, and a second implementation of one could not be
617
616
  tested and would drift.
618
617
 
619
- **Serving is the engine's to do; publishing is never.** A `remote` reader
618
+ **Serving is the engine's to do, and there is nothing else.** A `remote` reader
620
619
  authorises a local server — one process, ended by one flag, leaving nothing
621
- behind — and authorises nothing else. Publishing leaves a page this tooling
622
- cannot remove, so it stays an ask in every case, always. If the engine could not
623
- serve (a busy port, a machine with no network address) it falls back to the
624
- `file://` URL with its marker, and that is when publishing is worth naming.
620
+ behind. If the engine could not serve (a busy port, a machine with no network
621
+ address) it falls back to the `file://` URL with its marker.
625
622
 
626
623
  - **Never fatal.** A failed render — no worktree, a git error — is one line, and
627
624
  the fix is still done. The page is a convenience; the repo is the record.
@@ -50,8 +50,10 @@ evidence.
50
50
  Otherwise resolve **in this order**, and stop at the first that answers:
51
51
 
52
52
  1. **The live spec of this checkout** — run
53
- `skitterspec spec-env live status` and read its `live:` line. `live: yes`
54
- names the spec whose branch is checked out here; that is the one to build.
53
+ `skitterspec spec-env live status` and read its `in-flight:` line. A spec
54
+ name there is the spec whose branch is checked out here; that is the one to
55
+ build. `none` and `unknown` answer nothing — carry on down the list. (The
56
+ bare report's first line is a bare `spec-env live:` header, not an answer.)
55
57
  2. **The worktree you are standing in** — if this session's cwd is inside a
56
58
  spec's worktree, that spec is in flight *for this session*. This is the
57
59
  manual-parallel path: several specs may be provisioned, and a terminal tab
@@ -62,10 +64,17 @@ Otherwise resolve **in this order**, and stop at the first that answers:
62
64
  named, from wherever you happen to be standing:
63
65
 
64
66
  ```
65
- skitterspec spec-env resolve
67
+ skitterspec spec-env resolve --json
66
68
  ```
67
69
 
68
- Take its `spec:` line **only when it names exactly one spec**.
70
+ Take its `spec` **only when it names exactly one spec** (`ok: true`); `via`
71
+ says which rung answered.
72
+
73
+ From the primary checkout that includes the spec `/spec-live main` last
74
+ released here (`via: "last-live"`): releasing leaves the session standing
75
+ in the primary checkout, which says nothing on its own, so the engine
76
+ remembers the spec it handed back — for as long as that spec's worktree
77
+ exists — ahead of counting worktrees.
69
78
 
70
79
  This is the **durable** rung, and that is the whole reason it exists. Rungs 1
71
80
  to 3 all read *session* state, and session state does not survive a `/clear`,
@@ -81,13 +90,14 @@ Otherwise resolve **in this order**, and stop at the first that answers:
81
90
  `.claude/rules/spec-planning.md` states has none left.
82
91
 
83
92
  **Say which spec you resolved and how**, before writing a line of it:
84
- *"not standing in a worktree — `<spec>` is the only spec provisioned"*. Rungs
93
+ *"not standing in a worktree — `<spec>` is the only spec provisioned"*, or
94
+ *"`<spec>` was last live on this checkout"*. Rungs
85
95
  1 to 3 are self-evident to whoever typed the command; this one is not, and
86
96
  the operator cannot see from where they sit what you picked.
87
97
 
88
- **Several worktrees stay a refusal.** The engine names them and resolves
89
- nothing — exactly the ambiguity the refusal below exists for. Relay its list
90
- unchanged and stop; never pick from it.
98
+ **Several worktrees stay a refusal.** The engine answers `ok: false` with
99
+ `reason: "ambiguous"` and lists the `candidates`, each with its `worktree`,
100
+ and resolves nothing. Relay that list unchanged and stop; never pick from it.
91
101
 
92
102
  WHAT WOULD FOOL THIS: a worktree left behind by a declined teardown is still
93
103
  a worktree, so a finished spec can go on counting as provisioned. That widens
@@ -96,10 +106,18 @@ Otherwise resolve **in this order**, and stop at the first that answers:
96
106
  manufacture an *absence*, which is why the absence below is still worth
97
107
  refusing on.
98
108
 
99
- **If none answers, refuse and stop:**
100
- `no spec in flight — run /spec-start <name> to start one`.
109
+ **If none answers, refuse and stop — and say which absence it is.** Rung 4's
110
+ `reason` tells them apart, and they send the reader to different places:
111
+
112
+ - **`reason: "none"`** — no spec has a worktree anywhere:
113
+ `no spec in flight — run /spec-start <name> to start one`.
114
+ - **`reason: "ambiguous"`** — several specs are in flight and this session is
115
+ standing in none of them: `several specs are in flight and this session is
116
+ not in one of them`, then the candidates as the engine listed them (spec and
117
+ worktree), and `/spec-next --worktree <path>` as the way to name one.
118
+ `/spec-start` is wrong here: every one of them is already started.
101
119
 
102
- That now answers a real absence — no worktree anywhere, the engine included —
120
+ The first answers a real absence — no worktree anywhere, the engine included —
103
121
  rather than a session that merely lost track of where it was standing.
104
122
 
105
123
  **Never fall back to the spec "in context".** A spec discussed in conversation
@@ -482,11 +500,11 @@ so one subject lives in one place:
482
500
 
483
501
  - **local** — <the `local:` URL>
484
502
  - **network** — <the `network:` URL, or off with the command that turns it on>
485
- - **remote** — <the `remote:` URL, or off with the command that turns it on>
503
+ - **remote** — <the `remote:` tailnet URL, or what that line says when there is none>
486
504
 
487
505
  <the `live:` line, exactly as the engine printed it — omitted when it printed none>
488
506
 
489
- I'm holding here until you send a verdict — the wait covers local and network.
507
+ I'm holding here until you send a verdict — the wait covers <the tiers the engine's `covers` names>.
490
508
 
491
509
  `/spec-reviewed` picks it up · `spec-env review skip "<reason>"` moves on
492
510
 
@@ -507,22 +525,14 @@ reviewer sees the heading they have always seen.
507
525
  printed one line per tier, in that order, and `--json` carries the same thing as
508
526
  `tiers`. Relay all three whatever they say, including the ones that are off with
509
527
  the command that turns them on: a reader who has left the house cannot ask for a
510
- remote page they were never shown.
528
+ remote door they were never shown.
511
529
 
512
530
  **Do not pick one for them.** The engine used to, and the guess failed three
513
531
  separate ways in one day. `.claude/rules/spec-reports.md` carries the shape and
514
532
  why the *one link, never two* rule now reads
515
- **one link per reachable store, each labelled** —
516
- local and network are two doors into one room, so the wait
517
- covers both. `remote` is a second store, so its own line carries its own caveat:
518
- *a verdict here needs `/spec-reviewed`*, because nothing pushes from
519
- the artifact store into this conversation. Never let the holding line promise a
520
- wait over that tier.
521
-
522
- **Publishing is still never yours to do.** `remote` reading `off` is the normal
523
- state, and the fix for it is the command on that line — typed by the operator,
524
- or pressed on the page, because a published page is one this tooling cannot
525
- remove and permitting it is not publishing it.
533
+ **one link per door, each labelled, all into one store** —
534
+ local, network and remote are three doors into one room, so the wait
535
+ covers every one the stack shows.
526
536
 
527
537
  **The `live:` line goes with the stack**, and it is the engine's line too —
528
538
  copied as printed, and **absent when the engine printed none**. The page can act
@@ -537,7 +547,7 @@ verdict.
537
547
  **Where you are not waiting, it stays the `Review` row** — the counts and the
538
548
  page link, and **no question**:
539
549
 
540
- | **Review** | <N> files, +<a> −<d> · **local** <URL> · **network** <URL> · **remote** off |
550
+ | **Review** | <N> files, +<a> −<d> · **local** <URL> · **network** <URL> · **remote** <URL> (tailnet) |
541
551
 
542
552
  At the end of a phase you are always waiting, so this shape belongs to the
543
553
  renders that are not this step: a mid-phase `/spec-diff`, a page produced
@@ -651,10 +661,9 @@ Relay the engine's **stack** — the `local:`, `network:` and `remote:` lines
651
661
  never the bare `page:` path: a path is not clickable in any terminal, and a page
652
662
  nobody can open is a page nobody reads.
653
663
 
654
- - **Never write the review unasked**, and **never publish**. Publishing leaves
655
- something behind that this tooling cannot remove, so it is always something
656
- someone asks for. A `file://` link is no use on a phone, and saying so **is**
657
- the ask — publishing is the answer to it, and `/spec-diff` §6 owns how.
664
+ - **Never write the review unasked**, and **never publish** — there is no
665
+ publishing (`/spec-diff` §6). A `file://` link is no use on a phone, and the
666
+ stack says why nothing was served.
658
667
  **The `reader:` line no longer decides anything here, and that is the point.**
659
668
  It is still printed, and it is still the only place that question is answered —
660
669
  but the offer does not change with it, because the stack lists every tier
@@ -664,23 +673,20 @@ that branching is exactly what produced a `file://` page on a session detected
664
673
  underneath a reader when detection flipped mid-session.
665
674
 
666
675
  So: **relay all three tier lines, every time.** Any `also:` lines sit under
667
- `network` — the other addresses this machine has, offered because the
668
- best-guess one can be wrong — so pass them on rather than editing them out: in
669
- the banner they are indented sub-bullets under **network**, labels
670
- (`(tailnet)`) included, exactly as `.claude/rules/spec-reports.md` shows.
676
+ their tier — the other addresses this machine has of that kind — so pass them
677
+ on rather than editing them out: in the banner they are indented sub-bullets
678
+ under that tier, labels included, exactly as `.claude/rules/spec-reports.md`
679
+ shows.
671
680
 
672
681
  **Never read an environment variable to decide anything about the offer** — not
673
682
  `SSH_CONNECTION`, not `CLAUDE_CODE_*`, not a tty check. There is nothing left
674
683
  here for a detection to decide, and a second implementation of one could not be
675
684
  tested and would drift.
676
685
 
677
- **Serving is the engine's to do; publishing is never.** The server is one
686
+ **Serving is the engine's to do, and there is nothing else.** The server is one
678
687
  process, ended by one flag, leaving nothing behind, and `review.allowNetwork`
679
- decides whether it binds wide — no detection involved. A reader the server CAN
680
- reach is not a reason to publish as well: the tiers they can already open are on
681
- the stack. Publishing leaves a page this tooling cannot remove, so it stays an
682
- ask in every case, always — which is why `remote` shows the command rather than
683
- a URL until someone types it.
688
+ decides whether it binds wide — on the LAN and the tailnet alike — with no
689
+ detection involved.
684
690
 
685
691
  - **Never fatal.** A failed render — no worktree, a git error — is one line and
686
692
  the phase is still done. The page is a convenience; the repo is the record.
@@ -702,7 +708,8 @@ the shape; this section carries only what is specific here.
702
708
  **Some failed** or **Not yet**: the phase stays `🔄`, `Notes` says which steps
703
709
  are open, and `Next` is `/commit, then /spec-next` to pick them up.
704
710
  - `❌` — the phase's tests are red, or it stopped part-way. Quote the failure.
705
- - `⏸` — no spec in flight, or the name given does not match the one that is.
711
+ - `⏸` — no spec in flight, several in flight with this session in none of
712
+ them, or the name given does not match the one that is.
706
713
 
707
714
  **Fields:** `Tracker` · `Branch` · `Built` · `Tests` · `Notes` · `Review` ·
708
715
  `Follow-ups` · `Next`
@@ -286,9 +286,9 @@ reader:
286
286
 
287
287
  - **local** — &lt;the `local:` URL&gt;
288
288
  - **network** — &lt;the `network:` URL, or off with the command that turns it on&gt;
289
- - **remote** — &lt;the `remote:` URL, or off with the command that turns it on&gt;
289
+ - **remote** — &lt;the `remote:` tailnet URL, or what that line says when there is none&gt;
290
290
 
291
- I'm holding here until you send a verdict — the wait covers local and network.
291
+ I'm holding here until you send a verdict — the wait covers &lt;the tiers the engine's `covers` names&gt;.
292
292
 
293
293
  `Commit` commits the refresh · `Request changes` works them now
294
294
 
@@ -176,14 +176,7 @@ everything a decision needs, so there is nothing to go looking for, and going
176
176
  looking is the bypass step 0 forbids. The file is right there and readable; that
177
177
  is precisely why the rule is written down rather than assumed.
178
178
 
179
- **Check the store before concluding nothing is waiting.** Only when this spec
180
- has a published page (`--json` reports a `url`): a reader off the LAN sent their
181
- pass to the artifact's own `passes` collection rather than to the engine, so an
182
- empty holding area is not an empty answer yet. Read it with the Artifact tool's
183
- `read_db`, merge the `blob` through `--notes`, and **delete the document** —
184
- `/spec-diff` §6 owns the whole sequence, including that a claim consumes.
185
-
186
- **Nothing waiting in either is an ordinary answer.** Say so and stop. Do not hunt
179
+ **Nothing waiting is an ordinary answer.** Say so and stop. Do not hunt
187
180
  through other specs, and do not treat an empty holding area as a problem — a
188
181
  `file://` page copies to the clipboard instead of sending, so mention that the
189
182
  pass may be on their clipboard waiting to be pasted, and finish.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skitterbyte/skitterspec-jira",
3
- "version": "2.16.0",
3
+ "version": "2.17.0",
4
4
  "description": "Spec-driven development for Claude Code, with one-way Jira Cloud sync — a superset of @skitterbyte/skitterspec: the base filesystem workflow plus /spec-status · /spec-push and the spec-sync CLI. The repo is canonical; Jira is a generated mirror. Install this OR the base OR the Linear superset — exactly one.",
5
5
  "keywords": [
6
6
  "claude",