@jjanczur/tyran 0.1.31 → 0.1.32

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.
@@ -77,6 +77,31 @@ is a `staging` branch with CI. That looks like P2 — I release to staging on
77
77
  my own, production stays yours. Confirm, or say P1 and I only ever touch
78
78
  branches."
79
79
 
80
+ ### If they are not an engineer, ask the ONE question instead
81
+
82
+ Sales and marketing people run this now. `questions` is written for someone
83
+ who knows what an autonomy class is, and four entries shaped `field: source`
84
+ is where a non-expert stops. The same scan carries a `plain` object built for
85
+ them — **one** question, its evidence in ordinary words, two options at most,
86
+ and a `derived` list of what Tyran settled for itself.
87
+
88
+ Use it whenever the operator has given you any sign they are not an engineer,
89
+ and when you are unsure. It costs a fluent reader nothing: everything in
90
+ `questions` is still in the config with its provenance, and `plain.evidence`
91
+ keeps the raw git sentence for anyone who wants the numbers.
92
+
93
+ Read `plain.question`, `plain.because`, then the options with
94
+ `plain.recommended` marked. Then read the `derived` lines out as decisions,
95
+ not as questions — those are the things the repository already answered, and
96
+ re-asking them is what makes setup feel like an interrogation. Close with
97
+ `plain.note`, which says how the one class Tyran will never infer is actually
98
+ reached, and that the dashboard can change all of it later.
99
+
100
+ The three questions you are NOT asking them are deliberate: the package
101
+ manager is a fact, the validation commands are a fact or an honest gap, and
102
+ the `CLAUDE.md` line is a paste they can see. A question someone cannot
103
+ answer is not a safeguard; it is a place to give up.
104
+
80
105
  One flagged question is the `CLAUDE.md` pointer, and it is a question rather
81
106
  than an edit on purpose. Tyran writes `CLAUDE.md` only inside its own
82
107
  `tyran:rules` fence, and only through `mistakes.mjs promote --law`, which
@@ -106,6 +131,56 @@ still lives in the plugin and updates keep reaching it. Mention that it lands
106
131
  in their repo and will show up in their next commit — a file appearing in
107
132
  someone's working tree unannounced is a bad way to meet a tool.
108
133
 
134
+ ## 4b. Make the secrets gate satisfiable, and say what it found
135
+
136
+ The gate refuses every commit and push until `gitleaks` exists. Install it
137
+ before anything needs it, rather than letting the first commit fail with a
138
+ prerequisite the operator may not be able to meet:
139
+
140
+ ```bash
141
+ node "${CLAUDE_PLUGIN_ROOT}/scripts/ensure-gitleaks.mjs"
142
+ ```
143
+
144
+ Pinned and checksummed, into `~/.tyran/bin/`; it is a no-op when the machine
145
+ already has one, and PATH still wins.
146
+
147
+ **Then look, before they hit it.** A repository whose history already contains
148
+ a secret is common and the gate handles it badly by surprise: nothing is
149
+ scanned until someone EDITS the file that holds it, and then every commit
150
+ touching that file is refused, permanently, with no hint that the cause is
151
+ years old. Run a scan and say plainly what is there.
152
+
153
+ If there are pre-existing findings, explain the choice in the operator's
154
+ words, and do not make it for them:
155
+
156
+ - a tracked `.gitleaks-baseline.json` tells the gate "these exact findings are
157
+ known" — new secrets are still caught, and because it is tracked the
158
+ suppression appears in a diff instead of being an invisible local file;
159
+ - **but a baseline makes the tool quiet, it does not make the key safe.** If
160
+ the repository is public, that key is already burned and the real fix is
161
+ rotating it. Say this once, here, rather than letting them discover it after
162
+ they have relied on the baseline.
163
+
164
+ ## 4c. Turn the dashboard on
165
+
166
+ Setup is not finished until they have SEEN something. Everything above is
167
+ files on disk; the board is where any of it becomes legible, and it was the
168
+ one thing installation never actually reached.
169
+
170
+ ```bash
171
+ node "${CLAUDE_PLUGIN_ROOT}/scripts/board.mjs" --dir .tyran --serve --write --open
172
+ ```
173
+
174
+ `--open` launches their browser; `--write` is what makes the **Settings** tab
175
+ able to edit `config.yaml` and the autonomy policy from the page. Tell them
176
+ that tab exists and what it covers — profile, autonomy class, tiers,
177
+ validation commands, shared zones, overnight limits — because for someone who
178
+ would rather not hand-edit YAML in their own repository, that tab is the
179
+ entire configuration story and they will not guess it is there.
180
+
181
+ It holds the terminal while it serves. Say so, and say that Ctrl-C stops it
182
+ and the board is still there next time.
183
+
109
184
  ## 5. Validate and report
110
185
 
111
186
  ```bash
@@ -166,18 +241,29 @@ copies of the config. Stage explicit paths until this commit exists.
166
241
 
167
242
  Overnight mode (https://jjanczur.github.io/tyran/overnight/) pauses autonomous work near the
168
243
  subscription usage limit and resumes after the window resets. It is OFF by
169
- default because its telemetry is a statusline the plugin cannot install:
170
- `.claude/settings.json` in user scope is the operator's file, and the policy
171
- gate refuses agents writing the in-repo one — so print the snippet with the
172
- plugin path RESOLVED and let the human paste it:
244
+ default, and turning it on is now **one edit to `.tyran/config.yaml`** — the
245
+ Settings tab will do it — because the gate reads the platform's own usage
246
+ cache in `~/.claude.json` when no statusline is installed.
247
+
248
+ That fallback is why this step is short. Until it existed, the telemetry came
249
+ only from a statusline the plugin cannot install (`.claude/settings.json` in
250
+ user scope is the operator's file, and the gate refuses agents writing the
251
+ in-repo one), so overnight mode's real prerequisite was a paste — and on an
252
+ install that skipped it the pause failed open and said nothing.
253
+
254
+ Show the `limits:` block to enable (`mode: 'pause'` — quoted, since bare
255
+ `off`/`on` are YAML booleans), and say that `doctor --state` reports
256
+ `limit-telemetry-missing` only when NO telemetry is reachable at all, which
257
+ usually means signed out rather than misconfigured.
258
+
259
+ A statusline is still worth offering to anyone who wants the sharpest
260
+ possible pause: it is session-scoped and refreshed every few seconds, where
261
+ the platform's cache is refreshed on its own schedule and has been measured
262
+ over an hour old. Print the snippet with the plugin path RESOLVED and let the
263
+ human paste it — never attempt the settings write yourself, the refusal is the
264
+ boundary working:
173
265
 
174
266
  ```json
175
267
  { "statusLine": { "type": "command",
176
268
  "command": "node <resolved-plugin-root>/scripts/statusline.mjs" } }
177
269
  ```
178
-
179
- Then show the `limits:` block to enable (`mode: 'pause'` — quoted, bare
180
- `off`/`on` are YAML booleans) and note that `doctor --state` reports
181
- `limit-telemetry-missing` if the pause is configured while the statusline is
182
- not installed. Do not attempt the settings write yourself; the refusal is
183
- the boundary working.