projmux 0.15.2 → 0.16.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.
- package/README-ko.md +3 -4
- package/README.md +3 -3
- package/docs/agent-message-replies.md +82 -2
- package/docs/ai-agent-shortcuts.md +6 -5
- package/docs/architecture.md +149 -63
- package/docs/claude-coordination-endpoints.md +192 -21
- package/docs/cli-guide.md +322 -124
- package/docs/cli.md +605 -500
- package/docs/codex-installed-compatibility.md +6 -11
- package/docs/codex-native-required-migration.md +1 -59
- package/docs/configuration.md +164 -176
- package/docs/globalization.md +11 -1
- package/docs/heterogeneous-dialogue-canary.md +8 -3
- package/docs/hooks.md +83 -32
- package/docs/keybindings.md +108 -3
- package/docs/legacy-cli-retirement.md +3 -3
- package/docs/legacy-diagnostics-inventory.md +4 -4
- package/docs/native-picker.md +3 -5
- package/docs/notify-queue.md +1 -1
- package/docs/operational-diagnostics.md +53 -31
- package/docs/pr-guideline.md +66 -22
- package/docs/release.md +97 -0
- package/docs/replacement-contract.md +66 -58
- package/docs/resource-attribution.md +2 -2
- package/docs/session-restore.md +46 -80
- package/docs/settings-ia.md +43 -20
- package/docs/statusbar.md +25 -22
- package/docs/testing.md +15 -0
- package/docs/theme-palette.md +14 -0
- package/docs/tmux-surface-inventory.md +8 -10
- package/docs/troubleshooting.md +2 -4
- package/docs/upgrading.md +142 -7
- package/docs/usage-tracking.md +56 -53
- package/package.json +5 -5
- package/docs/agent-workflow.md +0 -2123
- package/docs/codex-generation-pool.md +0 -623
- package/docs/codex-stored-qualification.md +0 -45
|
@@ -1,45 +0,0 @@
|
|
|
1
|
-
# Stored Codex version-pair qualification
|
|
2
|
-
|
|
3
|
-
`projmux agent app-server upgrade qualify --receipt <absolute-json>` installs
|
|
4
|
-
one measured receipt for its exact old/new Codex version pair. Inspect the
|
|
5
|
-
saved receipts with:
|
|
6
|
-
|
|
7
|
-
```sh
|
|
8
|
-
projmux doctor --section integrations
|
|
9
|
-
projmux doctor --section integrations --json
|
|
10
|
-
```
|
|
11
|
-
|
|
12
|
-
The default Doctor report includes the same inventory. Its
|
|
13
|
-
`codex_stored_qualification` JSON field also appears in support `doctor.json`,
|
|
14
|
-
with version pairs, statuses, verdicts, reasons, and readiness preserved.
|
|
15
|
-
The read does not depend on a generation-pool journal or a readable Registry.
|
|
16
|
-
|
|
17
|
-
```text
|
|
18
|
-
Codex stored version-pair qualification
|
|
19
|
-
Store: stored
|
|
20
|
-
0.153.2 -> 0.153.4: stored; verdict: yes; reason: qualified; qualification ready: true
|
|
21
|
-
```
|
|
22
|
-
|
|
23
|
-
| Store status | Meaning |
|
|
24
|
-
| --- | --- |
|
|
25
|
-
| `stored` | All enumerated receipts decoded and matched their filenames. |
|
|
26
|
-
| `absent` | No saved receipt exists; the directory may be absent or empty. |
|
|
27
|
-
| `damaged` | At least one receipt could not be read as its filename's pair. Other receipts remain visible. |
|
|
28
|
-
| `unavailable` | The store path could not be resolved or the directory could not be read. |
|
|
29
|
-
|
|
30
|
-
Each `version_pairs` row reports `stored`, `damaged`, or
|
|
31
|
-
`version-pair-mismatch`. A mismatch means a valid receipt names a different pair
|
|
32
|
-
from its filename; its verdict is not reported for the filename's pair. A
|
|
33
|
-
malformed `.json` filename produces a damaged row without exposing that name.
|
|
34
|
-
Non-regular receipt files are damaged; temporary save files are ignored.
|
|
35
|
-
|
|
36
|
-
For a stored row, `verdict` and `reason` come from the existing strict receipt
|
|
37
|
-
decoder. `qualification_ready` comes from the existing qualification gate:
|
|
38
|
-
a saved `no` or a self-consistent `yes` with unbacked evidence counters remains
|
|
39
|
-
not ready. This field describes only the pair's qualification, and does not
|
|
40
|
-
assert that the generation pool or an upgrade operation is ready.
|
|
41
|
-
|
|
42
|
-
Schema v2 has no timestamps or expiry policy. A receipt stays reportable until
|
|
43
|
-
it is replaced or removed. Doctor reads it without running qualification,
|
|
44
|
-
writing receipts or journals, restoring upgrade state, or executing lifecycle
|
|
45
|
-
commands.
|