@pqpo/pragma 0.1.0-next.12 → 0.1.0-next.14
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.
- package/README.md +43 -1
- package/dist/cli.js +36304 -33320
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -40,8 +40,50 @@ active owner reports a stable busy error; it does not silently enqueue a
|
|
|
40
40
|
different operation. Human checkpoints can be answered interactively or
|
|
41
41
|
returned as `input_required` for a later response.
|
|
42
42
|
|
|
43
|
+
Useful read-only commands:
|
|
44
|
+
|
|
45
|
+
```bash
|
|
46
|
+
pragma expert discover "memory"
|
|
47
|
+
pragma mission list --executor expert:<16-char-id>
|
|
48
|
+
pragma mission get <MISSION_ID> --view summary
|
|
49
|
+
pragma mission get <MISSION_ID> --view result
|
|
50
|
+
pragma mission get <MISSION_ID> --view events --limit 20
|
|
51
|
+
pragma mission queue list <MISSION_ID>
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
`discover` accepts one selector. A canonical `kind:ID` is an exact match;
|
|
55
|
+
other selectors search executor names and descriptions. `--query` is the
|
|
56
|
+
keyword-search form and cannot be combined with a selector. Event pages return
|
|
57
|
+
a durable `nextCursor`; copy it into the printed continuation command.
|
|
58
|
+
|
|
59
|
+
`mission get --view summary|result|events` is backed by the Local Host query
|
|
60
|
+
projection. `chat` and `work` deliberately fail with `INVALID_ARGUMENT` until
|
|
61
|
+
their contracts are ready; use `--view events` or `mission watch` meanwhile.
|
|
62
|
+
The text renderers use stable Mission/queue columns, while JSON and JSONL stay
|
|
63
|
+
pure `pragma.cli-result/v2` and `pragma.cli-event/v2` protocol output.
|
|
64
|
+
|
|
65
|
+
Runs wait for a terminal result by default. `--detach` returns after handle
|
|
66
|
+
acceptance, and `--request-id` is optional because the CLI generates one when
|
|
67
|
+
omitted. Text mode prints the request, Mission, and execution identities;
|
|
68
|
+
machine formats keep those identities inside the protocol envelope.
|
|
69
|
+
|
|
70
|
+
Command-specific help includes usage, defaults, output format, idempotency,
|
|
71
|
+
and a copyable example, for example `pragma mission get --help` or
|
|
72
|
+
`pragma expert discover --help`.
|
|
73
|
+
|
|
43
74
|
For scripts and other AI tools, use `--format=json` or `--format=jsonl` and
|
|
44
|
-
inspect the process exit code.
|
|
75
|
+
inspect the process exit code. The P1 `--log-level` /
|
|
76
|
+
`PRAGMA_LOG_LEVEL` contract will use `silent|fatal|error|warn|info|debug` with
|
|
77
|
+
priority CLI > environment > default `info`; the current release may not yet
|
|
78
|
+
include this option.
|
|
79
|
+
|
|
80
|
+
The three documents have separate jobs: this README is the npm installation
|
|
81
|
+
and entry-point guide, the human guide explains interactive CLI/Mission
|
|
82
|
+
semantics, and the Agent/automation guide defines machine output, recovery,
|
|
83
|
+
and cursor handling.
|
|
84
|
+
|
|
85
|
+
- Human CLI guide → [docs/usage/cli.md](https://github.com/pqpo/pragma/blob/main/docs/usage/cli.md)
|
|
86
|
+
- Agent/automation guide → [docs/usage/cli-agent.md](https://github.com/pqpo/pragma/blob/main/docs/usage/cli-agent.md)
|
|
45
87
|
|
|
46
88
|
## Upgrade, rollback, and uninstall
|
|
47
89
|
|