werkmeister-core 0.94.0 → 0.94.1

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 CHANGED
@@ -1,5 +1,14 @@
1
1
  # sandbox-core
2
2
 
3
+ ## 0.94.1
4
+
5
+ ### Patch Changes
6
+
7
+ - 03c1389: Generated `.werkmeister/pr-rules.md` no longer names Changesets outside the two places that explain changesets-only behaviour: the release-bot example, the merged-PR release note and the quoted `skip_release` example now say "release entry". The repo-agnostic test now checks every markdown file `workspace init` writes (skills, `_shared/`, `CLAUDE.md`), not only the stage contracts.
8
+ - 448cb50: `werkmeister-context.md` § Test commands now prints the test of a container that holds the real `~/.werkmeister` or the docker socket, and mounts the workspace folder at its host path, under the temp HOME: `docker exec -w /app <container> <ws>/.werkmeister/bin/with-temp-home --no-wait sh -c '…'`, as its Validation text requires. Other containers (a docker.sock-only one cannot see `<ws>/.werkmeister/bin`) keep the bare `docker exec` line, and the allow rules are unchanged. Rerun `werkmeister workspace init` to regenerate the file.
9
+ - db0280e: The implement stage contracts name one way to serve a static HTML page for a browser check (the Chrome tool refuses `file://`): `python3 -I -u -m http.server 0 -b 127.0.0.1 -d <dir>` as a background job, stopped by its task ID, recorded in `exercise.md` as the method.
10
+ - 8223702: The implement stage contracts say the Chrome window does not size below 477 px, and check a narrower width (e.g. 375 px) in a same-origin iframe built with the JS tool: a screenshot plus `scrollWidth === clientWidth` inside the frame.
11
+
3
12
  ## 0.94.0
4
13
 
5
14
  ## 0.93.12
@@ -14,6 +14,13 @@
14
14
  * touches the raw fields.
15
15
  */
16
16
  import { type Archetype, type ArchetypeRegistry, type ReposConfig, type ServiceEntry, type ServicesConfig } from "./config.js";
17
+ /**
18
+ * True when one of *entry*'s host binds is a docker socket (any path ending `docker.sock`, e.g. OrbStack's)
19
+ * or the werkmeister home, or a parent of either.
20
+ */
21
+ export declare function hostAccess(entry: ServiceEntry | undefined): boolean;
22
+ /** True when *entry*'s container sees host path *p* at the same path (one of its binds covers it). */
23
+ export declare function seesHostPath(entry: ServiceEntry | undefined, p: string): boolean;
17
24
  /**
18
25
  * Return the normalized archetype dict for one service definition.
19
26
  *
@@ -43,7 +50,7 @@ export declare function serviceNoTests(svcDef: ServiceEntry | null | undefined):
43
50
  * worktree's `node_modules` live. werkmeister-context.md and the workspace's
44
51
  * `permissions.allow` rule both use it, so the rule matches what the agent runs.
45
52
  */
46
- export declare function containerTestCommand(feature: string, svc: string, cmd: string): string;
53
+ export declare function containerTestCommand(feature: string, svc: string, cmd: string, tempHome?: string): string;
47
54
  /** True when *cmd* is simple commands joined only by `&&`: no group, pipe, `||`, `;`, `&`, newline or substitution. */
48
55
  export declare function isPlainChain(cmd: string): boolean;
49
56
  /**
@@ -13,7 +13,36 @@
13
13
  * Everything downstream reads through `resolveServiceArchetype` and never
14
14
  * touches the raw fields.
15
15
  */
16
- import { loadArchetypes, } from "./config.js";
16
+ import * as fs from "node:fs";
17
+ import * as path from "node:path";
18
+ import { expandUser, loadArchetypes, sandboxHome, } from "./config.js";
19
+ const realPath = (p) => {
20
+ try {
21
+ return fs.realpathSync(p);
22
+ }
23
+ catch {
24
+ return path.resolve(p);
25
+ }
26
+ };
27
+ /** Host sources of *entry*'s bind mounts (named volumes skipped), symlinks resolved (`/var` → `/private/var` on macOS). */
28
+ const hostBinds = (entry) => (entry?.extra_volumes ?? [])
29
+ .map((spec) => spec.split(":")[0])
30
+ .filter((src) => src.includes("/"))
31
+ .map((src) => realPath(expandUser(src)));
32
+ const within = (p, dir) => p === dir || p.startsWith(`${dir}${path.sep}`) || dir === "/";
33
+ /**
34
+ * True when one of *entry*'s host binds is a docker socket (any path ending `docker.sock`, e.g. OrbStack's)
35
+ * or the werkmeister home, or a parent of either.
36
+ */
37
+ export function hostAccess(entry) {
38
+ const targets = ["/var/run/docker.sock", sandboxHome()].map(realPath);
39
+ return hostBinds(entry).some((host) => path.basename(host) === "docker.sock" || targets.some((t) => within(t, host)));
40
+ }
41
+ /** True when *entry*'s container sees host path *p* at the same path (one of its binds covers it). */
42
+ export function seesHostPath(entry, p) {
43
+ const target = realPath(p);
44
+ return hostBinds(entry).some((host) => within(target, host));
45
+ }
17
46
  function isDict(value) {
18
47
  return typeof value === "object" && value !== null && !Array.isArray(value);
19
48
  }
@@ -80,8 +109,12 @@ export function serviceNoTests(svcDef) {
80
109
  * worktree's `node_modules` live. werkmeister-context.md and the workspace's
81
110
  * `permissions.allow` rule both use it, so the rule matches what the agent runs.
82
111
  */
83
- export function containerTestCommand(feature, svc, cmd) {
84
- return `docker exec ${feature}-${svc} sh -c '${cmd.split("'").join(`'\\''`)}'`;
112
+ export function containerTestCommand(feature, svc, cmd, tempHome) {
113
+ const quoted = `sh -c '${cmd.split("'").join(`'\\''`)}'`;
114
+ // SW-769: a container holding the real ~/.werkmeister runs its tests under a temp HOME, as Validation says.
115
+ return tempHome
116
+ ? `docker exec -w /app ${feature}-${svc} ${tempHome} --no-wait ${quoted}`
117
+ : `docker exec ${feature}-${svc} ${quoted}`;
85
118
  }
86
119
  /** True when *cmd* is simple commands joined only by `&&`: no group, pipe, `||`, `;`, `&`, newline or substitution. */
87
120
  export function isPlainChain(cmd) {
@@ -11,7 +11,7 @@
11
11
  */
12
12
  import * as fs from "node:fs";
13
13
  import * as path from "node:path";
14
- import { containerTestCommand, serviceNoTests, serviceTestCommand, validationRows, wrappedTestCommand, } from "../../archetypes.js";
14
+ import { containerTestCommand, hostAccess, seesHostPath, serviceNoTests, serviceTestCommand, validationRows, wrappedTestCommand, } from "../../archetypes.js";
15
15
  import { cacheSource } from "../../build_caches.js";
16
16
  import { baselineUpstream, loadArchetypes, loadCaches, } from "../../config.js";
17
17
  import { ingressHostnames, loadFeatureRouters } from "../../feature_routing.js";
@@ -255,13 +255,15 @@ Hit a bug, or need to log a feature or task, in the \`werkmeister\` tool or a re
255
255
  // ---------------------------------------------------------------------------
256
256
  // werkmeister-context.md generation
257
257
  // ---------------------------------------------------------------------------
258
- function testCommandLine(feature, svc, servicesConfig, archetypes, lint) {
258
+ // SW-769: wrap where the real ~/.werkmeister is at risk, but only if the container sees <ws> (a docker.sock-only one would exit 127).
259
+ const withTempHome = (entry, tempHome) => tempHome && hostAccess(entry) && seesHostPath(entry, tempHome) ? tempHome : "";
260
+ function testCommandLine(feature, svc, servicesConfig, archetypes, lint, tempHome = "") {
259
261
  const cmd = serviceTestCommand(svc, servicesConfig[svc], archetypes);
260
262
  const noTests = serviceNoTests(servicesConfig[svc]);
261
263
  if (noTests)
262
264
  return `- \`${svc}\`: no tests (registry: ${noTests})`;
263
265
  return cmd
264
- ? `- \`${svc}\`: \`${containerTestCommand(feature, svc, lint ? `${lint} && ${cmd}` : cmd)}\``
266
+ ? `- \`${svc}\`: \`${containerTestCommand(feature, svc, lint ? `${lint} && ${cmd}` : cmd, withTempHome(servicesConfig[svc], tempHome))}\``
265
267
  : `- \`${svc}\`: no test command registered (add \`test:\` to its registry entry)`;
266
268
  }
267
269
  /** SW-720: in sw-700 host `node`, a compound line and `docker exec … node <script>` were each denied before this form ran. */
@@ -463,7 +465,7 @@ The registry's \`test:\` for each service (or its archetype's), run in its conta
463
465
  ? " A line starting with `<lint> &&` first runs the repo's lint, the PR gate's lint row, so a `docs:check` or format failure shows here, before the tests, and not first at the gate."
464
466
  : ""}
465
467
 
466
- ${svcs.map((s, i) => testCommandLine(feature, s, servicesConfig, archetypes ?? loadArchetypes(), svcLint[i])).join("\n")}
468
+ ${svcs.map((s, i) => testCommandLine(feature, s, servicesConfig, archetypes ?? loadArchetypes(), svcLint[i], tempHome)).join("\n")}
467
469
  ${sharedCachesLine(caches)}
468
470
  `;
469
471
  }
@@ -44,8 +44,8 @@
44
44
  import * as fs from "node:fs";
45
45
  import * as path from "node:path";
46
46
  import { parse as parseYaml } from "yaml";
47
- import { candidateServiceNames, containerTestCommand, isPlainChain, serviceTestCommand, wrappedTestCommand, } from "../../archetypes.js";
48
- import { dotDir, expandUser, getReposRoot, loadArchetypes, loadReposConfig, loadServices, sandboxHome, sandboxRoot, } from "../../config.js";
47
+ import { candidateServiceNames, containerTestCommand, hostAccess, isPlainChain, serviceTestCommand, wrappedTestCommand, } from "../../archetypes.js";
48
+ import { dotDir, getReposRoot, loadArchetypes, loadReposConfig, loadServices, sandboxRoot, } from "../../config.js";
49
49
  import { frozenInstalls } from "../../fragment_detect/workspace.js";
50
50
  import { load as loadGlobalConfig } from "../../global_config.js";
51
51
  import { workspaceServices } from "../../registry_sync.js";
@@ -464,30 +464,6 @@ hostServices = [], reposConfig = {}) {
464
464
  .map((r) => `${wrapped}--no-wait ${r.slice(wrapped.length)}`));
465
465
  return [...new Set([...rules, ...READ_ONLY_GIT_RULES])];
466
466
  }
467
- /**
468
- * True when one of *entry*'s host binds is a docker socket (any path ending `docker.sock`, e.g. OrbStack's)
469
- * or the werkmeister home, or a parent of either; symlinks resolved (`/var` → `/private/var` on macOS).
470
- */
471
- function hostAccess(entry) {
472
- const real = (p) => {
473
- try {
474
- return fs.realpathSync(p);
475
- }
476
- catch {
477
- return path.resolve(p);
478
- }
479
- };
480
- const targets = ["/var/run/docker.sock", sandboxHome()].map(real);
481
- return (entry?.extra_volumes ?? []).some((spec) => {
482
- const src = spec.split(":")[0];
483
- if (!src.includes("/"))
484
- return false; // a named volume
485
- const host = real(expandUser(src));
486
- if (path.basename(host) === "docker.sock")
487
- return true;
488
- return targets.some((t) => t === host || t.startsWith(`${host}${path.sep}`) || host === "/");
489
- });
490
- }
491
467
  /**
492
468
  * SW-845: *registry* with each entry's `extra_volumes` widened to every bind compose mounts: the
493
469
  * branch's own fragment and the workspace's `dev_links` too (both agent-editable), variables
package/dist/pr_rules.js CHANGED
@@ -31,7 +31,7 @@ These hold for every PR this workspace produces, whatever skill or command was a
31
31
  3. **Gate.** Before a PR opens, all of these hold: every earlier stage/phase is done; every follow-up a decided question in \`decisions.md\` promises names its issue key; the PR file's acceptance table is all PASS (MANUAL rows pass and the gate lists them); the code worktree is clean; a branch not yet pushed is not behind \`origin/<base>\` (the gate fetches it first; a pushed one passes with a note, rule 5; when behind, rebase with \`git -C <repo> rebase origin/<base>\` and rerun the tests, before the first push so no force-push is needed); each touched service's registry test command passes (\`.werkmeister/werkmeister-context.md\`); the exercise evidence is all PASS (or \`skip_exercise\` gives the reason); the code review in \`review.md\` is all PASS (or \`skip_review\` gives the reason; only in a workspace whose build stage has the review step); the repo's release check passes; the PR file reads \`status: approved\`. The PR-file checks (stages, acceptance table, approved, exercise evidence, review) and the base check run first; if one fails, the gate stops before any test command. With the tests the gate can run past a 10-minute tool call. Run \`pr open\`, and \`pr gate\` or \`pr gate --tests\` too, alone as a background job your harness tracks (Claude Code: \`run_in_background\`), with only its log redirect and no \`cd\`, pipe or other command around it, so an allow rule for it matches (an autonomous run has one; an interactive one asks): \`werkmeister pr open > <absolute workspace path>/.werkmeister/pr-open.log 2>&1\`, or \`werkmeister pr gate --tests > <absolute workspace path>/.werkmeister/gate-run.log 2>&1\`. The log path is absolute because the shell's cwd can drift into a code worktree, which would write the log there as an untracked file. Wait for its completion notice, which carries the exit code, then read the log's end. A bare \`&\` dies when the tool call returns, and \`nohup … &\` sends no notice when it ends.
32
32
  4. **Only \`werkmeister pr open\` opens PRs.** \`gh pr create\`, \`/create-pr\` and \`finishing-a-development-branch\` are blocked inside a workspace.
33
33
  5. **Auto-fix is always on.** \`werkmeister pr watch\` wakes the session that opened the PR when a check fails, a review comes in or the PR conflicts with its base, with the cause in the message. On a conflict, rebase onto \`origin/<base>\`; never merge the base into the branch, or GitHub can't rebase-merge it. A conflict in a generated file (a snapshot, a lockfile): take the base's copy and regenerate it with the repo's generator (\`.werkmeister/werkmeister-context.md\` names it); never hand-merge it. The agent can't force-push, so give the person \`git -C <absolute worktree path> push --force-with-lease=<branch>:<old sha>\`, where \`<old sha>\` is the PR head before the rebase; the wake message prints it filled in. With no wake message (a manual second rebase), run \`git fetch\` and take \`<old sha>\` from the output of \`git rev-parse origin/<branch>\`, pasted verbatim: never shortened or retyped, or the push fails \`stale info\`. ${DESKTOP_AUTOFIX_RULE} Never turn on auto-merge.
34
- 6. **Merge is the person's act.** Tooling never merges. On a repo with a merge queue, the queue's method decides how every PR merges (\`gh api repos/<repo>/rules/branches/<base>\`, the \`merge_queue\` rule's \`merge_method\`); without one, squash is the default. A PR that needs another method says so at the top of its body, and the person merges it that way, bypassing the queue: a grouped PR (\`group\` in \`workspace.yml\`) says "Rebase and merge, not squash" and keeps its per-ticket commits (\`werkmeister pr gate\` warns when the base won't allow it); a PR whose commit SHAs must survive (e.g. a commit listed in \`.git-blame-ignore-revs\`) says "Merge with a merge commit", since squash and rebase both rewrite SHAs. A PR that must wait for a step outside the code (e.g. a ruleset applied after its CI goes green) sets \`hold: <reason>\` in its PR file: \`werkmeister pr open\` then opens it as a draft, which GitHub won't merge, with \`Don't merge until: <reason>\` at the top of the body. The session that does the step runs \`gh pr ready <url>\` and empties \`hold:\`. A PR the repo's own automation queues (a release bot's version PR, e.g. Changesets' "version packages") is the exception: leave it to that automation, and don't tell the person it's theirs to merge.
34
+ 6. **Merge is the person's act.** Tooling never merges. On a repo with a merge queue, the queue's method decides how every PR merges (\`gh api repos/<repo>/rules/branches/<base>\`, the \`merge_queue\` rule's \`merge_method\`); without one, squash is the default. A PR that needs another method says so at the top of its body, and the person merges it that way, bypassing the queue: a grouped PR (\`group\` in \`workspace.yml\`) says "Rebase and merge, not squash" and keeps its per-ticket commits (\`werkmeister pr gate\` warns when the base won't allow it); a PR whose commit SHAs must survive (e.g. a commit listed in \`.git-blame-ignore-revs\`) says "Merge with a merge commit", since squash and rebase both rewrite SHAs. A PR that must wait for a step outside the code (e.g. a ruleset applied after its CI goes green) sets \`hold: <reason>\` in its PR file: \`werkmeister pr open\` then opens it as a draft, which GitHub won't merge, with \`Don't merge until: <reason>\` at the top of the body. The session that does the step runs \`gh pr ready <url>\` and empties \`hold:\`. A PR the repo's own automation queues (a release bot's version PR) is the exception: leave it to that automation, and don't tell the person it's theirs to merge.
35
35
  7. **Close out only when every PR file is \`shipped\`, \`closed\` or \`abandoned\`, and after the post-mortem:** the werkmeister \`postmortem\` skill writes \`postmortem.md\` at the workspace root. \`werkmeister workspace close\` refuses without it unless \`--skip-postmortem "<reason>"\`.
36
36
 
37
37
  ## PR file — \`${prFileDir}pr-<worktree>[-<slug>].md\`
@@ -50,7 +50,7 @@ merge_sha: # written by werkmeister pr status
50
50
  release: # release tag that shipped it, written by werkmeister pr status; \`none\` for a merged skip_release PR with no changeset (changesets repos), else set it yourself for a change that ships nothing
51
51
  reason: "" # required for closed / abandoned
52
52
  skip_tests: {} # <service>: <reason> — for a service with no test command or no running container (a service that has no tests says \`test: none: <reason>\` in its registry entry instead); tests: <reason> when no service maps to the changed files
53
- skip_release: "" # <reason> — skips the gate's release check; a ship: tag repo still waits for its release tag unless release: none, or the merged PR has no changeset
53
+ skip_release: "" # <reason> — skips the gate's release check; a ship: tag repo still waits for its release tag unless release: none, or the merged PR has no release entry
54
54
  skip_exercise: "" # <reason> — skips the gate's exercise check, e.g. a doc deliverable with nothing to run
55
55
  skip_review: "" # <reason> — skips the gate's review check, e.g. a doc deliverable with no code to review
56
56
  hold: "" # <reason> — pr open opens the PR as a draft, body starting "Don't merge until: <reason>"; when the step is done, gh pr ready <url> and empty this (rule 6)
@@ -59,7 +59,7 @@ hold: "" # <reason> — pr open opens the PR as a draft, body sta
59
59
  <PR body: summary, test and exercise results, acceptance table, Fixes <issue>>
60
60
  \`\`\`
61
61
 
62
- **Quote free-text values.** \`reason\`, \`skip_*\` (each \`skip_tests\` entry too) and \`hold\` take a double-quoted string, e.g. \`skip_release: "no changeset: docs only"\`. An unquoted value that contains \`: \` is invalid YAML and \`werkmeister pr open\` fails on it.
62
+ **Quote free-text values.** \`reason\`, \`skip_*\` (each \`skip_tests\` entry too) and \`hold\` take a double-quoted string, e.g. \`skip_release: "no release entry: docs only"\`. An unquoted value that contains \`: \` is invalid YAML and \`werkmeister pr open\` fails on it.
63
63
 
64
64
  **Acceptance table.** One row per criterion. The result cell holds exactly \`PASS\` or \`FAIL\` and nothing else; evidence goes in its own column. A criterion only the reviewer can check (it needs a real PR, the desktop app or the real machine) reads \`MANUAL\`, with why in the evidence: the gate passes it and lists it, and never \`PASS\` for a check nobody ran. Only this table takes \`MANUAL\`; exercise and review rows are PASS or FAIL. \`| criterion | PASS: repro.md §1 |\` fails the gate.
65
65
 
@@ -16,6 +16,10 @@ const RELOAD_RULE = "If the container is not running, run `werkmeister feature u
16
16
  "they are slower, and init rewrites the stage contracts.";
17
17
  // SW-612: sw-588 fell back to a published port after `feature up` warned a routed hostname did not resolve.
18
18
  const HOSTNAME_RULE = "If `werkmeister feature up` warns that a routed hostname does not resolve to 127.0.0.1 (its last warning line points to `werkmeister machine setup`), stop before any browser check and ask the person to run `werkmeister machine setup` (it needs sudo for the hosts entries and certificate trust). Never click through or bypass a certificate warning. Use the container's published port instead only when the person says to skip setup, and record it in `exercise.md` as a deviation.";
19
+ // SW-791: sw-772 hand-ran http.server to check a docs page; the Chrome tool refuses file://.
20
+ const STATIC_PAGE_RULE = "A static HTML page with no service to load it from is served for the browser check, since the Chrome tool refuses `file://`: run `python3 -I -u -m http.server 0 -b 127.0.0.1 -d <dir>` as a background Bash job (never without `-b 127.0.0.1`: it binds every interface by default), open the port its first line prints, and stop the job by its task ID when the check ends. Record it in `exercise.md` as the method.";
21
+ // SW-792: Chrome won't size its window below 477 px, so sw-772's 375 px check ran at 477.
22
+ const NARROW_VIEWPORT_RULE = 'The Chrome window does not size below 477 px, so check a narrower width in an iframe on the same origin: open the server\'s root, then with the JS tool replace the body with `<iframe src="<page>" width="375" height="812">`, screenshot it, and check `frame.contentDocument.documentElement.scrollWidth === frame.contentDocument.documentElement.clientWidth`. A page on another origin can\'t be read in the frame: ask the person for that row.';
19
23
  // SW-143: a library or CLI has nothing to restart. How to exercise one is the service's (or its archetype's)
20
24
  // `validate:` text, so app-specific steps stay out of the generic templates.
21
25
  const NO_SERVICE_RULE = "A library or CLI has no service to restart: build it, then exercise the built artifact exactly as its Validation text in `werkmeister-context.md` § How to validate says.";
@@ -297,7 +301,7 @@ const feature = [
297
301
  implementReview(v),
298
302
  GATE_STEP,
299
303
  REVIEW_DELTA,
300
- `Reload the running code: ${v.restart}. ${RELOAD_RULE} ${HOSTNAME_RULE} Then exercise the change as the How-to-validate section of \`werkmeister-context.md\` describes for each service touched, and capture the output. ${NO_SERVICE_RULE} ${PROBE_RULE} ${EXERCISE_WORKAROUND} ${TIMING_CLAIM}`,
304
+ `Reload the running code: ${v.restart}. ${RELOAD_RULE} ${HOSTNAME_RULE} ${STATIC_PAGE_RULE} ${NARROW_VIEWPORT_RULE} Then exercise the change as the How-to-validate section of \`werkmeister-context.md\` describes for each service touched, and capture the output. ${NO_SERVICE_RULE} ${PROBE_RULE} ${EXERCISE_WORKAROUND} ${TIMING_CLAIM}`,
301
305
  `Write \`output/exercise.md\`: \`git diff --stat\` for each repo you touched, the host and \`pr gate --tests\` exit codes and summary lines, ${PER_SERVICE}, ${SKIPPED}, any deviation from \`spec.md\` with its reason, and the exercise checks as ${exerciseFormat("evidence")}.`,
302
306
  MANUAL_STEP,
303
307
  ],
@@ -401,7 +405,7 @@ const bugfix = [
401
405
  ],
402
406
  doNotLoad: "`BRIEF.md` (`repro.md` carries the settled scope), `.werkmeister/*.yml`.",
403
407
  process: [
404
- `Reload the running code: ${v.restart}. ${RELOAD_RULE} ${HOSTNAME_RULE} ${NO_SERVICE_RULE} ${PROBE_RULE}`,
408
+ `Reload the running code: ${v.restart}. ${RELOAD_RULE} ${HOSTNAME_RULE} ${STATIC_PAGE_RULE} ${NARROW_VIEWPORT_RULE} ${NO_SERVICE_RULE} ${PROBE_RULE}`,
405
409
  "Rerun the reproduction steps from `repro.md` exactly. Capture the output.",
406
410
  `Exercise one neighbouring path through each caller \`repro.md\` listed. Capture the output. ${EXERCISE_WORKAROUND} ${TIMING_CLAIM}`,
407
411
  `Write \`output/exercise.md\`: steps 2–3 as ${exerciseFormat("detail")}.`,
@@ -474,7 +478,7 @@ const refactor = [
474
478
  implementReview(v),
475
479
  GATE_STEP,
476
480
  REVIEW_DELTA,
477
- `After the last step, reload and exercise the service: ${v.restart}. ${RELOAD_RULE} ${HOSTNAME_RULE} ${NO_SERVICE_RULE} ${PROBE_RULE} ${EXERCISE_WORKAROUND} ${TIMING_CLAIM}`,
481
+ `After the last step, reload and exercise the service: ${v.restart}. ${RELOAD_RULE} ${HOSTNAME_RULE} ${STATIC_PAGE_RULE} ${NARROW_VIEWPORT_RULE} ${NO_SERVICE_RULE} ${PROBE_RULE} ${EXERCISE_WORKAROUND} ${TIMING_CLAIM}`,
478
482
  `Write \`output/exercise.md\`: \`git diff --stat\` per repo, the test result after each step, the \`pr gate --tests\` exit code, ${PER_SERVICE}, ${SKIPPED}, and the final exercise checks as ${exerciseFormat("evidence")}.`,
479
483
  MANUAL_STEP,
480
484
  ],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "werkmeister-core",
3
- "version": "0.94.0",
3
+ "version": "0.94.1",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "description": "werkmeister's shared library. Its public API is werkmeister-core/sdk; every other entry point is internal.",