@jjanczur/tyran 0.1.45 → 0.1.47

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.
@@ -404,11 +404,17 @@ open one.
404
404
  re-litigated after every compaction; a question written as a bare `kind` of
405
405
  your own invention collides with the next one that shares it, and the older
406
406
  question is lost with nothing objecting anywhere.
407
- - **Always record a `default`** — what ships if nobody ever answers. It is
408
- what the operator accepts by leaving an answer blank, and it is the only
409
- reason a queue of fifteen questions takes ten minutes instead of an hour.
410
- An ask with no default is a question the operator must stop and think
411
- about; spend that budget deliberately.
407
+ - **Always record a `recommendation`** — what you would do. It becomes the
408
+ `default` when you name no other, so an ask that carries one is a
409
+ question with a safe outcome rather than a stop. An ask carrying NEITHER
410
+ is a question the operator must wake up and think about; spend that
411
+ budget deliberately, and expect it to hold its ticket until they do.
412
+ Record a separate `default` only when the safe answer differs from your
413
+ advice — "per-seat" recommended, "keep flat fee" if nobody rules.
414
+ - **`--blocking` is for the ones that must wake them.** Irreversible,
415
+ visible outside the repo, or spending money. It is the only thing that
416
+ survives `unattended.mode: on`, so use it exactly there and nowhere else:
417
+ a run whose every question is blocking is a run that stops.
412
418
  - **Do not park an asked ticket.** An ask that names a ticket already puts
413
419
  it in the board's `waiting-operator` lane. A `ticket.status` override on
414
420
  top of it **overrules** that lane and hides the question's own ticket —
@@ -421,6 +427,14 @@ open one.
421
427
  operator answers you in chat instead, append that pair yourself — same
422
428
  `kind`, `result: answered`, plus a `decision` whose text begins
423
429
  `Q-<n>: ` — and say in your next report that you did.
430
+ - **Under `unattended: mode: on`, sweep after you raise.** Run
431
+ `node ${CLAUDE_PLUGIN_ROOT}/scripts/answer.mjs auto --dir .tyran`, which
432
+ closes every ask that carries a recommendation and is not `--blocking`,
433
+ recording `answer_mode: unattended`. The operator went to sleep expecting
434
+ shipped work; a queue nobody read is a night spent parked. It is a SWEEP
435
+ rather than a rule you apply yourself — the same command runs on the
436
+ board's own timer, so an ask you raise and then die on still gets ruled.
437
+ Say in your report which questions were answered without them.
424
438
  **Check the brake before every spawn and every merge:**
425
439
  `node ${CLAUDE_PLUGIN_ROOT}/scripts/stop-check.mjs` — exit 1 means the
426
440
  operator created `.tyran/STOP`. Halt, report where you got to, and do not
@@ -72,10 +72,13 @@ boundaries:
72
72
  prompts: ask
73
73
 
74
74
  # Overnight mode — pause autonomous work near the subscription usage limits
75
- # and resume after the window resets (https://jjanczur.github.io/tyran/overnight/). Requires the
76
- # operator-installed statusline helper (scripts/statusline.mjs), which is the
77
- # only place the platform exposes usage telemetry; without it the gate is
78
- # silent and doctor says so.
75
+ # and resume after the window resets (https://jjanczur.github.io/tyran/overnight/).
76
+ # Telemetry is read from three places in order: the statusline helper if you
77
+ # installed one, the platform's usage cache in ~/.claude.json, and — when
78
+ # neither reports a percentage — the wall itself, read back out of the session
79
+ # transcript. The third only fires AFTER the limit is hit, so it cannot stop
80
+ # you early; what it restores is the clean wind-down and the scheduled resume.
81
+ # Doctor says so when none of the three can see anything.
79
82
  #
80
83
  # mode: off | warn | pause warn surfaces, never denies; pause winds down
81
84
  # wait_max_hours: 5 reset further away than this = a LONG pause:
@@ -96,6 +99,29 @@ limits:
96
99
  resume_margin_minutes: 5
97
100
  keep_awake: false # a real boolean, so the bare-off trap above cannot apply
98
101
 
102
+ # Unattended delivery — what an open question does when nobody is awake.
103
+ #
104
+ # With mode: on, an ask is answered by the agent's own recommendation the
105
+ # moment it is raised, and the run keeps going. That is the point of an
106
+ # overnight run: you went to sleep expecting shipped work, and a queue of
107
+ # questions nobody read is a night spent parked.
108
+ #
109
+ # Two refusals are mechanical, and they are what make this safe to switch on:
110
+ # an ask with no recommendation is a real question and stays open, and an ask
111
+ # raised with `--blocking` (the irreversible, the outward-facing, the ones that
112
+ # spend money) always waits for you. Everything taken automatically is
113
+ # journalled as `answer_mode: unattended` with its decision text prefixed
114
+ # `(auto-accepted overnight)`, so the morning is one scan of the ledger.
115
+ #
116
+ # `.tyran/STOP` still outranks all of it.
117
+ #
118
+ # mode: off | on bare on/off are fine here — both spellings work
119
+ # answer: recommendation what an ask resolves to: the agent's advice,
120
+ # | default or the conservative fallback it recorded
121
+ unattended:
122
+ mode: 'off'
123
+ answer: recommendation
124
+
99
125
  # The dashboard. Unlike everything above, this defaults ON: the board is where
100
126
  # a journal, a projection and a spend report become something a person can
101
127
  # read, and an install where nobody starts it is an install where none of that