@skitterbyte/skitterspec-linear 19.16.0 → 19.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.
@@ -1,37 +0,0 @@
1
- ---
2
- description: Permit or forbid publishing this spec's review for a reader off your network — bare toggles it, `on`/`off` set it explicitly
3
- argument-hint: "[on | off]"
4
- allowed-tools: Bash({{exec}} skitterspec spec-env review allow remote:*)
5
- disable-model-invocation: true
6
- ---
7
- !`{{exec}} skitterspec spec-env review allow remote --set "$ARGUMENTS"`
8
-
9
- Relay the engine output above verbatim. Add nothing to it.
10
-
11
- **Then one thing, and only when the engine asked for it.** Where the output
12
- carries a `review:` and a `publish:` line, typing this command **is** the ask
13
- to publish that page: the banner named this command beside a review the reader
14
- could not reach, so the link is what they are waiting for. Publish it exactly
15
- as `/spec-diff` §6 describes (run the `publish:` command, publish the copy it
16
- names with a store, write the URL file), then re-emit the review banner with
17
- all three tiers, `remote` now carrying the URL. A wait already running keeps
18
- running; do not restart it or the server. If the harness refuses the publish,
19
- say so in one line and keep the banner as it was, because local and network
20
- still work.
21
-
22
- With no `publish:` line, run nothing else. Nothing has a page to publish, or
23
- the tier was turned off.
24
-
25
- **Bare toggles.** That is the common case: you are looking at a render whose
26
- `remote:` line says which way it currently is, and what you want is the other
27
- one. `on` and `off` are there for when you are not looking at it.
28
-
29
- **It is per spec.** The engine resolves the spec from the worktree you are
30
- standing in and records the permission in the gitignored review store, so
31
- the base branch is untouched and no other spec may publish because of it.
32
- `skitterspec spec-env review allow remote --project` is the committed,
33
- every-spec form, for a team that wants it.
34
-
35
- **A published page is one skitterspec cannot delete**, and a verdict pressed
36
- on one needs `/spec-reviewed`, because nothing pushes from an artifact's store
37
- into a conversation.