werkmeister-core 0.91.4 → 0.91.5
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/CHANGELOG.md +6 -0
- package/dist/strategies/icm_templates.js +6 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# sandbox-core
|
|
2
2
|
|
|
3
|
+
## 0.91.5
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 4ea7192: SW-789: the feature pipeline's research contract (step 3) now tells a gate-, test- or build-speed ticket to sample the container cgroup `cpu.stat` `usage_usec` every 5 s across a cold run and report cores in use per phase before naming a critical path or lever. If the run holds all its CPUs, only a CPU cut shortens it, and the decision says so.
|
|
8
|
+
|
|
3
9
|
## 0.91.4
|
|
4
10
|
|
|
5
11
|
### Patch Changes
|
|
@@ -98,6 +98,9 @@ const reviewStep = (rerun, group) => "Review the diff: for each code worktree yo
|
|
|
98
98
|
const implementReview = (v) => reviewStep("rerun the host test step above", v.group);
|
|
99
99
|
// SW-687: sw-634 decided a blocklist for a pre-approved wrapper's input; one key it let through sent auth to any host.
|
|
100
100
|
const PREAPPROVED_INPUT = "When the change adds or widens an input to a pre-approved command (an allow rule, or a wrapper an allow rule covers), the decision defaults to an allowlist of accepted values and lists what each accepted value can reach: files, env vars, network addresses, processes. A blocklist needs a stated reason.";
|
|
101
|
+
// SW-789: sw-751 named the build chain as the critical path from task start/end times; the row held all 3 CPUs for ~170 s, so only a CPU cut shortens it.
|
|
102
|
+
const CPU_PROFILE = "When the ticket is about gate, test or build speed, sample the container cgroup `cpu.stat` `usage_usec` every 5 s across a cold run and report the cores in use per phase before naming a critical path or any lever. " +
|
|
103
|
+
"Task start and end times alone do not show whether a path matters. If the run holds all its CPUs, only a CPU cut shortens it, and the decision says so.";
|
|
101
104
|
// SW-106 decision 7 renamed a legacy alias that `git log -S` would have shown was meant to be removed.
|
|
102
105
|
const NAME_HISTORY_STEP = "For each decision that renames, keeps or removes a name, a fallback or an alias, record its definition site (file and line) and the commit that introduced it (`git log -S <name>`, in the repo that defines it). " +
|
|
103
106
|
'When that commit marks it as a transition or legacy alias, list "remove" as an option beside rename and keep.';
|
|
@@ -192,7 +195,9 @@ const feature = [
|
|
|
192
195
|
"When a decision rests on how an external tool behaves (a CLI command or flag, a plugin API, an event name), check it against the installed tool, not only its docs: record `<bin> --version`, and confirm each fact with `<bin> <cmd> --help` or a real run or plugin load. `decisions.md` names the version and, beside each fact, the command that confirmed it; a fact only the docs support is marked `unverified: docs only`, and no decision rests on it. If the tool cannot be installed, say so and mark every such fact `unverified`. " +
|
|
193
196
|
// SW-605: sw-583 recommended a GitHub API call as `unverified` only in the file; the person approved it and a read-only call later returned 403.
|
|
194
197
|
"A recommended answer that rests on an external API, permission or platform behaviour (a token scope, a hosted API's response, a cloud permission) is checked live, read-only (a list, get, `--help` or dry run, never a write), before it goes into `decisions.md`, with the command and its result beside it. When it cannot be checked read-only, write `unverified` in the option text itself, so the question the person is asked carries the word, not only the file. " +
|
|
195
|
-
PREAPPROVED_INPUT
|
|
198
|
+
PREAPPROVED_INPUT +
|
|
199
|
+
" " +
|
|
200
|
+
CPU_PROFILE,
|
|
196
201
|
"Write `output/inventory.md`: steps 1–3.",
|
|
197
202
|
NAME_HISTORY_STEP,
|
|
198
203
|
`Write \`output/decisions.md\`: every open question in \`BRIEF.md\`, each as a heading with \`status: proposed\`, your recommended answer, and the evidence from steps 1–3 and 5. Leave the answer blank when only a person can give it (a ticket key, a preference). ${CRITERION_REACH}`,
|
package/package.json
CHANGED