@lmzhen/dsh-evolution-core 0.22.0 → 0.23.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.md +20 -0
- package/lib/index.js +271 -521
- package/lib/types/errors.d.ts +2 -1
- package/lib/types/guards.d.ts +23 -0
- package/lib/types/index.d.ts +1 -0
- package/lib/types/io.d.ts +44 -103
- package/lib/types/params.d.ts +10 -0
- package/lib/types/platform-services.d.ts +2 -2
- package/lib/types/preset-composition.d.ts +84 -1
- package/lib/types/skill-row-cells.d.ts +2 -0
- package/lib/types/skill-store.d.ts +9 -49
- package/package.json +1 -1
- package/persisted-write-inventory.json +3 -3
package/README.md
CHANGED
|
@@ -75,3 +75,23 @@ are emitted for operators and observability (5 and 3 dispatch sites, 0 `ctx.on`
|
|
|
75
75
|
**kept deliberately** — the observation surface is the point, and a deployment's own listener is the intended
|
|
76
76
|
consumer — so the `@mode` target stays at six (decision 10, provisional: keep).
|
|
77
77
|
|
|
78
|
+
## 错误码（THE error-code table）
|
|
79
|
+
|
|
80
|
+
> 本节的表与 `src/errors.ts` 的码表必须**同集**，并写明**区间**：CI 门禁 `verify-error-codes.mjs <root>`
|
|
81
|
+
> 到 `<root>/evolution-core/README.md` 逐码核对（新增码要同时进表与区间行）。
|
|
82
|
+
| `E-301` / `E-302` / `E-303` | approval / curator / replay service not mounted | mount the row (they ship with host/all), then run doctor |
|
|
83
|
+
| `E-306` | this deployment stages foreground writes, but the named command is not replayable through the skill runner | approve-and-execute it directly, or set `stageForeground: false` deliberately |
|
|
84
|
+
| `E-304` | the mounted approval service predates the release capability (a skewed/partial upgrade) | `reject` the pending record instead of `release` |
|
|
85
|
+
| `E-305` | the invocation carries no agent (a script/headless caller reached a session-backed branch) | run the command from a session in the GUI or the CLI |
|
|
86
|
+
| `E-307` / `E-311` | the settings service is missing or cannot report its sections (`/evolution params`, `/evolution policy set`) | mount the settings row (ships with host/all), then run doctor |
|
|
87
|
+
| `E-312` | a parameter id or value was rejected, with the reason included | run `/evolution params` to see the canonical ids |
|
|
88
|
+
| `E-308` / `E-313` | unknown parameter group or id | list them: `/evolution params` shows every registered id with its tier and owner |
|
|
89
|
+
| `E-314` / `E-315` / `E-316` | the id is a deployment parameter, has no user layer, or its owner is not mounted | write it in `cordis.yml`, or mount the owner row — the message names tier, owner and namespace |
|
|
90
|
+
| `E-309` / `E-310` | your write lost a revision race, or the settings service refused it (the reason is included) | re-read with `/evolution params` and retry |
|
|
91
|
+
| `E-317` | you declined the confirmation the tool asked before creating or deleting a skill (a foreground create or bare delete asks when `skillWriteConfirm` is `ask` or `timeout`; the default `auto` does not ask at all) | nothing was written; repeat the call if you do want it |
|
|
92
|
+
| `E-318` | a write without a read: the session never loaded that skill, so the write is refused (skills only; the foreground operator session is exempt) | load it with the `skill` tool, then repeat the write |
|
|
93
|
+
| `E-320` | the profile home is not reported by this host, so the legacy settings document cannot be located | run the command in a session whose profile home is set |
|
|
94
|
+
| `E-321` | no evolution-io provider is mounted, so the legacy settings document cannot be read | mount the `evolution-io-node` row |
|
|
95
|
+
| `E-322` | a cross-field parameter constraint would be broken (the field, its floor and the attempted value are included) | raise the value to the named floor, or lower the sibling first |
|
|
96
|
+
| `E-319` | the confirmation before a create or bare delete went unanswered for `skillWriteConfirmTimeoutSeconds` (`skillWriteConfirm: 'timeout'`), so the write was cancelled | set `skillWriteConfirm` to `auto` (write without asking), keep `ask` (wait until answered), or raise the timeout |
|
|
97
|
+
Symptom → next step; the exact text of every code (`E-301`–`E-322`) is stored once in
|