@jjanczur/tyran 0.1.36 → 0.1.37

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.36",
14
+ "version": "0.1.37",
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.36",
3
+ "version": "0.1.37",
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,28 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.37 — 2026-08-17
4
+
5
+ ### `--help` reaches the subcommand-style commands too
6
+
7
+ 0.1.36 gave the nine flag-taking commands a `--help` that answers on stdout
8
+ with exit 0. The four that dispatch on a VERB rather than a flag still reached
9
+ their usage text through the unknown-subcommand path, so `--help` was reported
10
+ as a mistake instead of answered — `mistakes --help` opened with *"unknown
11
+ subcommand"* before printing anything useful.
12
+
13
+ `schema`, `knowledge` and `mistakes` now answer it properly. **`journal` does
14
+ not yet**, and the reason is worth recording: its usage text is built inside
15
+ the error handler as a multi-line expression that also documents every event
16
+ and its required `--data` keys. Extracting it mechanically produced a syntax
17
+ error, so it is `NOTES-REQUESTS.md` §12.5 rather than a rushed edit here.
18
+
19
+ One thing this did NOT change, having measured it first. `doctor --state`
20
+ exiting 1 and `answer render` exiting 1 on a healthy fresh repo look like
21
+ success reported as failure, and they are neither. `answer.mjs`'s header
22
+ documents *"Exit: 0 ok · 1 nothing is waiting on you"*, and doctor's codes are
23
+ pinned by a test named for them. Both are deliberate `grep`-style "no results"
24
+ codes, and no caller in the repo reads them as failure.
25
+
3
26
  ## 0.1.36 — 2026-08-17
4
27
 
5
28
  Four fixes, three of them found by installing Tyran into a clean repo and
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jjanczur/tyran",
3
- "version": "0.1.36",
3
+ "version": "0.1.37",
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": {
@@ -37,6 +37,7 @@ import { join, resolve } from 'node:path';
37
37
  import { fileURLToPath } from 'node:url';
38
38
  import { validateFile, globMatches, normalizePath, KNOWLEDGE_KINDS } from './schema.mjs';
39
39
  import { escapeInvisible, jsonEscapeInvisible } from './invisible.mjs';
40
+ import { wantsHelp } from './cli-args.mjs';
40
41
 
41
42
  export const DEFAULT_DIR = join('.tyran', 'knowledge');
42
43
  export const DEFAULT_BUDGET = 4000;
@@ -247,6 +248,10 @@ function main() {
247
248
  const usage =
248
249
  'usage: knowledge.mjs brief [<path>...] [--dir <knowledge-dir>] [--kinds k,k] [--limit N] [--budget CHARS] [--json]\n' +
249
250
  ' knowledge.mjs audit [--dir <knowledge-dir>] [--budget CHARS] [--json]';
251
+ if (wantsHelp(process.argv.slice(2))) {
252
+ console.log(usage);
253
+ return;
254
+ }
250
255
  if (command !== 'brief' && command !== 'audit') {
251
256
  console.error(usage);
252
257
  process.exit(2);
@@ -55,6 +55,7 @@ import { fileURLToPath } from 'node:url';
55
55
  import { escapeInvisible } from './invisible.mjs';
56
56
  import { writeAtomic } from './project.mjs';
57
57
  import { append as appendEvent, nextId } from './journal.mjs';
58
+ import { wantsHelp } from './cli-args.mjs';
58
59
 
59
60
  /** The ledger's home. Repo ROOT, not `.tyran/`: a human, a reviewer on
60
61
  * GitHub and a session that has never heard of Tyran all have to find it. */
@@ -961,6 +962,10 @@ function journalDecision(flags, { signature, count, line, claudePath }) {
961
962
 
962
963
  function main() {
963
964
  const [command, ...rest] = process.argv.slice(2);
965
+ if (wantsHelp(process.argv.slice(2))) {
966
+ console.log(USAGE);
967
+ return 0;
968
+ }
964
969
  let code;
965
970
  try {
966
971
  const flags = parseArgs(rest);
@@ -18,6 +18,7 @@ import { resolve } from 'node:path';
18
18
  import { fileURLToPath } from 'node:url';
19
19
  import { parse, YamlLiteError } from './yaml-lite.mjs';
20
20
  import { escapeInvisible } from './invisible.mjs';
21
+ import { wantsHelp } from './cli-args.mjs';
21
22
 
22
23
  export const PROFILES = Object.freeze(['eco', 'balanced', 'full']);
23
24
  export const AUTONOMY_CLASSES = Object.freeze(['P1', 'P2', 'P3']);
@@ -711,10 +712,16 @@ export function validateFile(kind, file) {
711
712
 
712
713
  // ---------------------------------------------------------------- CLI
713
714
 
715
+ export const SCHEMA_USAGE = 'usage: schema.mjs validate <config|knowledge|policy> <file...>';
716
+
714
717
  function main() {
715
718
  const [cmd, kind, ...files] = process.argv.slice(2);
719
+ if (wantsHelp(process.argv.slice(2))) {
720
+ console.log(SCHEMA_USAGE);
721
+ return;
722
+ }
716
723
  if (cmd !== 'validate' || !kind || files.length === 0) {
717
- console.error('usage: schema.mjs validate <config|knowledge|policy> <file...>');
724
+ console.error(SCHEMA_USAGE);
718
725
  process.exit(2);
719
726
  }
720
727
  let failed = false;