@1aboveio/engineering-skills 0.1.11 → 0.1.12

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@1aboveio/engineering-skills",
3
- "version": "0.1.11",
3
+ "version": "0.1.12",
4
4
  "description": "Issue-to-PR and release orchestrators, review, coverage, golden paths and test quality.",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -27,7 +27,7 @@
27
27
  "id": "engineering",
28
28
  "core": "@1aboveio/core-skills",
29
29
  "coreSkills": [],
30
- "digest": "74205f550e53a2a8bd1b313edb82cfea5f4813a3559e6523080fd4ec8265e98f"
30
+ "digest": "a9804afc2b06ea51e2ab9ba611a502f5a8e67936493473526b1e591d02a535b0"
31
31
  },
32
32
  "publishConfig": {
33
33
  "registry": "https://registry.npmjs.org/",
@@ -4,7 +4,7 @@ description: "Slash/explicit-only (/better-review). Single-agent adversarial rev
4
4
  disable-model-invocation: true
5
5
  dependencies:
6
6
  - engineering-runtime
7
- release-version: 0.45.0
7
+ release-version: 0.45.1
8
8
  ---
9
9
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
10
10
  # Better Review
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: e2e-test
3
3
  description: "Playwright end-to-end guidance for affected browser journeys, render health and presentation checks, with route manifests and sweeps for broader audits. Use when browser routes or user flows ship or change, or a Playwright test flakes. NOT for non-browser tests, defining what to test (ensure-coverage), the curated ALIVE/DEAD golden-path gate (golden-path), or CI workflow YAML (github-actions)."
4
- release-version: 0.45.0
4
+ release-version: 0.45.1
5
5
  ---
6
6
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
7
7
  # E2E Testing Standard
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: engineering
3
- description: "Project engineering conventions and explicit /engineering init: feature-delivery priorities, focused verification and review, operational boundaries, and tracker routing. Use when setting up AGENTS.md or CONTRIBUTING.md, saving engineering defaults, or before creating an engineering issue, spec, epic, ticket, or sub-issue on GitHub or Linear. Reads existing policy without writing during ordinary work. NOT the issue-to-PR workflow (resolve-issues), release execution (resolve-release), Git delivery (github-flow), or CI setup (github-actions)."
4
- release-version: 0.45.0
3
+ description: "Engineering conventions: feature-delivery priorities, focused verification and review, operational boundaries, and tracker routing. Standalone /engineering offers Global, Project, or Session setup and targeted resets for configured scopes; /engineering init keeps explicit project setup. Use when setting up AGENTS.md or CONTRIBUTING.md, saving or resetting engineering defaults, or before creating an engineering issue, spec, epic, ticket, or sub-issue on GitHub or Linear. Reads existing policy without writing during ordinary work. NOT the issue-to-PR workflow (resolve-issues), release execution (resolve-release), Git delivery (github-flow), or CI setup (github-actions)."
4
+ release-version: 0.45.1
5
5
  ---
6
6
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
7
7
  # Engineering
@@ -15,12 +15,83 @@ work into a setup, audit, framework, or gate project.
15
15
 
16
16
  | Task | Action |
17
17
  | --- | --- |
18
+ | Standalone `/engineering` or `engineering`, with no other task or scope | [Choose the scope](#choose-the-scope); ask before writing |
18
19
  | `/engineering init` or an explicit request to register project defaults | [Initialize](#initialize-project-guidance) |
20
+ | Explicit request to save global defaults or use session-only defaults | Honor the named scope using [Choose the scope](#choose-the-scope); do not ask again |
21
+ | Explicit request to reset one or more scopes | [Reset and clean up](references/scope-management.md#reset-and-clean-up) only the named scopes |
19
22
  | Ordinary implementation or review | Read applicable guidance; apply the defaults below without writing files |
20
23
  | Create an issue, spec, epic, or sub-issue | [Tracker routing](#tracker-routing); do not initialize as a side effect |
21
24
  | Existing guidance conflicts with a proposed default | Preserve it; ask for a decision only if the requested action needs one |
22
25
  | Choose additional setup capabilities | [Initialization scope](references/init-scope.md); route to the owning skill |
23
26
 
27
+ ## Choose the scope
28
+
29
+ For every standalone invocation, inspect the known global instruction file, selected
30
+ project guidance, and session choice without writing. Read
31
+ [scope management](references/scope-management.md) for configuration detection,
32
+ ownership records, and reset cleanup. Do not infer session setup from an automatic
33
+ skill load or from inherited global or project rules.
34
+
35
+ Ask one structured single-choice question when available. With no configured scope,
36
+ ask "Where should the engineering rules apply?" with these options:
37
+
38
+ | Choice | Meaning |
39
+ | --- | --- |
40
+ | Global | Save defaults in the current agent's global instructions for future projects and sessions |
41
+ | Project | Save defaults in this project's `AGENTS.md` and `CONTRIBUTING.md` |
42
+ | Session | Apply defaults for this session only; do not write files |
43
+
44
+ When any scope is configured, ask "Which engineering scope should I set up or reset?"
45
+ Keep all three scopes visible: offer `Reset Global`, `Reset Project`, or `Reset Session`
46
+ for each configured scope, and `Set up Global`, `Set up Project`, or `Use for Session`
47
+ for each unconfigured scope. Describe what is set, inherited, partial, or unresolved
48
+ and name known target paths. Never label an unreadable or unknown scope as unset.
49
+ A reset selection authorizes cleanup only for that scope. If the user explicitly
50
+ requests several resets, process those scopes without asking them to choose one again.
51
+
52
+ Wait for the answer before writing. If the user cancels or makes no selection,
53
+ leave files unchanged.
54
+ Automatic discovery, a handoff, quoted examples, and a task that merely mentions
55
+ engineering do not show this question or authorize setup. A request to edit this
56
+ skill is not an invocation to save its rules.
57
+
58
+ - **Project:** The selection authorizes [project initialization](#initialize-project-guidance)
59
+ in the selected project, with its existing preservation and validation rules.
60
+ `/engineering init` remains a direct project setup request and skips this question.
61
+ - **Session:** Read the delivery defaults, [engineering conventions](references/engineering-conventions.md),
62
+ [testing conventions](../test-quality/references/testing-conventions.md), and
63
+ [tracker routing](#tracker-routing), and apply them without saving guidance or
64
+ changing agent settings. Keep this choice across reload or compaction within
65
+ the current session; it expires in a new session. Existing binding requirements
66
+ and permissions still apply.
67
+ - **Global:** The selection authorizes only the global guidance procedure below,
68
+ not project initialization. Do not pass a home or agent directory to `init.mjs`.
69
+
70
+ ### Save global defaults
71
+
72
+ 1. Resolve the current agent's supported user-level instruction file from the
73
+ active environment or its documented configuration. Show the exact path before
74
+ editing. If the destination is unknown or ambiguous, ask for it; do not guess
75
+ a path or write every agent's global files.
76
+ 2. Read existing global guidance and the feature-delivery, engineering, and testing
77
+ templates linked under project initialization. Use the scope-neutral rules from
78
+ those templates and tracker routing above; never copy the current project's
79
+ repository, Linear project, stack, commands, or delivery policy into global defaults.
80
+ 3. Validate the target before editing. Refuse unreadable or invalid files, dangling
81
+ links, and symlinks escaping the selected global instruction directory; preserve
82
+ valid links and edit their resolved target only once. Create only the selected
83
+ instruction file if missing. Keep the rules directly in that loaded file so future
84
+ sessions do not depend on a pointer to this skill's installation path.
85
+ 4. Add only missing defaults under `## Engineering defaults`, preserving existing
86
+ equivalent rules, hand edits, and unrelated instructions. Do not replace conflicting
87
+ policy without separate agreement. Repeating the same save is a no-op; a skill
88
+ update does not authorize refreshing saved rules. State that these are defaults
89
+ and that binding project requirements and action permissions still apply.
90
+ Record only this save's additions using the [ownership record](references/scope-management.md#record-ownership).
91
+ 5. Report the global scope, exact file created, updated, or already configured, and
92
+ any unresolved conflict or write failure. Do not change project files, install
93
+ dependencies, or perform delivery actions as part of saving defaults.
94
+
24
95
  ## Delivery defaults
25
96
 
26
97
  Prioritize the requested outcome. Supporting code, tests, and infrastructure need
@@ -35,13 +106,16 @@ extra planning roles. Ordinary implementation choices stay with the implementer.
35
106
 
36
107
  ## Initialize project guidance
37
108
 
38
- An explicit `/engineering init` authorizes the additions described here in the
39
- selected project. Automatic skill discovery, an issue-routing trigger, installation,
109
+ An explicit `/engineering init`, a Project selection above, or an explicit request
110
+ to save project defaults authorizes the additions described here in the selected
111
+ project. Automatic skill discovery, an issue-routing trigger, installation,
40
112
  updates, and quoted examples do not authorize writes. When defaults would help an
41
113
  unconfigured project, offer init once and continue; setup is not a feature prerequisite.
42
114
 
43
115
  1. Read existing project guidance and check for policy conflicts. The script preserves
44
116
  existing sections; it does not interpret or replace the project's decisions.
117
+ Retain the before-state so the ownership record can distinguish new additions
118
+ from preserved sections and links.
45
119
  2. Set `SKILL_DIR` to this installed skill's directory. Preview:
46
120
 
47
121
  ```sh
@@ -52,6 +126,9 @@ unconfigured project, offer init once and continue; setup is not a feature prere
52
126
  3. For the explicitly authorized init, run the same command with `--write`. A preview
53
127
  request alone stays read-only. No second approval is needed for the additions
54
128
  already requested; a conflicting policy change needs separate agreement.
129
+ Record only newly added blocks, pointers, and created files using the
130
+ [ownership record](references/scope-management.md#record-ownership). A no-op init
131
+ does not adopt existing guidance or create an ownership record for it.
55
132
  4. Report created, updated, and preserved files and any unresolved project decisions.
56
133
  Do not install dependencies, generate CI, create issues, push, or deploy as part of init.
57
134
 
@@ -1,6 +1,14 @@
1
1
  # What initialization includes
2
2
 
3
- The default is durable project guidance, not an orchestration or infrastructure setup.
3
+ Standalone `/engineering` first asks for Global, Project, or Session scope. Only a
4
+ Project selection, `/engineering init`, or an explicit project save uses the project
5
+ initializer described here. Global saving follows `SKILL.md`'s separate procedure;
6
+ Session keeps the rules in conversation context without writing files.
7
+ On later standalone calls, configured scopes offer a targeted reset with
8
+ [owned-guidance cleanup](scope-management.md#reset-and-clean-up); setup does not
9
+ grant permission to remove pre-existing rules.
10
+
11
+ Project initialization creates durable guidance, not an orchestration or infrastructure setup.
4
12
  This review covers every active first-party skill in the Engineering package and
5
13
  the related delivery, CI, and merge-queue convention owners. Archived skills are
6
14
  not initialization sources; pinned external skills keep their upstream ownership.
@@ -0,0 +1,85 @@
1
+ # Scope management
2
+
3
+ This procedure governs standalone setup and reset. It does not authorize cleanup
4
+ while the skill is loaded for implementation, review, or tracker routing.
5
+
6
+ ## Detect configuration
7
+
8
+ - Global uses only the current agent's supported user-level instruction file.
9
+ Project uses the selected Git root, or current directory without Git, and its
10
+ `AGENTS.md` and `CONTRIBUTING.md`. Apply the save procedure's target validation
11
+ before setup or reset. Do not scan unrelated projects or agent installations.
12
+ - A valid ownership record, equivalent existing engineering rules, or an explicit
13
+ active session choice means the corresponding scope is configured. Distinguish
14
+ fully configured, partially configured, and existing rules not owned by this skill.
15
+ Rules inherited from another scope do not mean this scope is configured.
16
+ - Inspect files afresh on every standalone call. Keep the session choice in context
17
+ across reload or compaction; a new session starts without that temporary choice.
18
+ A reset session choice remains off until the user explicitly enables it again.
19
+ - Report unknown, unreadable, invalid, and conflicting guidance honestly. Offer to
20
+ resolve that scope rather than presenting a save or reset as safe. An unknown
21
+ global path does not prevent a known project or session action.
22
+
23
+ ## Record ownership
24
+
25
+ After an authorized Global or Project save, keep a small JSON ownership record in
26
+ an HTML comment in each changed guidance file:
27
+
28
+ ```markdown
29
+ <!-- engineering:ownership
30
+ {"version":1,"scope":"project","createdFile":false,"additions":[]}
31
+ -->
32
+ ```
33
+
34
+ Populate `additions` from the actual before/after diff, never from the presence of
35
+ a familiar heading. Each entry has `namespace` (`conventions` or `engineering`),
36
+ `id`, and `sha256` fields. These identify the `<!-- <namespace>:<id>:start -->`
37
+ and matching `end` marker, and the SHA-256 of the bytes between them. Store marker
38
+ identifiers, not literal comment strings, so the initializer does not count the
39
+ receipt as duplicate markers. Include any new wrapper heading inside its recorded
40
+ block. Record only newly inserted text. Use the
41
+ existing `conventions:<id>:start/end` markers for new project sections. Wrap any
42
+ new global defaults or new loading pointer in unique `engineering:<id>:start/end`
43
+ comments before recording their hashes. Do not rewrap existing text or claim it as
44
+ owned. Keep existing valid records and add only new entries; deduplicate entries.
45
+
46
+ Set `createdFile` only when this save created that file. Preserve unrelated bytes
47
+ and existing links. Do not create a sidecar, global settings entry, or project file
48
+ for a session choice. A repeated save with no additions leaves files unchanged.
49
+ If a record is malformed or ownership is uncertain, preserve the affected text and
50
+ report the problem instead of inventing a receipt or claiming complete setup.
51
+
52
+ ## Reset and clean up
53
+
54
+ A selected reset or an explicit scoped reset request authorizes removal of that
55
+ scope's saved defaults, not a reinstall, refresh, or reset of every scope.
56
+
57
+ 1. Re-read and validate every target in the selected scope before editing. Explain
58
+ the planned removals and any preserved user rules. A read-only reset preview
59
+ stays read-only. Cancellation performs no cleanup.
60
+ 2. **Session:** Clear only the explicit temporary engineering choice. Do not edit
61
+ files or agent settings. Continue to honor inherited global and project rules
62
+ and binding requirements; session reset does not switch those off.
63
+ 3. **Global or Project:** Remove recorded additions only when their markers are
64
+ unique and balanced and their current content matches the recorded hash. Remove
65
+ their ownership entries as well. Retain edited blocks and their records, explain
66
+ the difference, and ask before removing user changes. Never delete an entire
67
+ section just because its heading matches a template.
68
+ 4. For older or unrecorded guidance, including legacy tracker blocks, ownership
69
+ cannot be inferred from markers alone. Identify the exact candidate text and
70
+ ask for agreement before deleting it. Do not adopt or erase rules written by
71
+ another skill. Safe, independently owned removals may proceed while an uncertain
72
+ removal remains unresolved; report the reset as partial.
73
+ 5. Remove owned loading pointers only if they are unchanged and no longer needed
74
+ by retained guidance. Keep a pointer that still loads user policy. Remove an
75
+ empty ownership record and any empty wrapper heading added by this save.
76
+ Delete a file only if `createdFile` proves this skill created it and nothing
77
+ except the original generated title and whitespace remains. Preserve pre-existing
78
+ files, symlinks, hand edits, and unrelated sections; never delete an instruction
79
+ directory or skill installation. Do not touch `CLAUDE.md` during project reset,
80
+ because project init does not own it.
81
+ 6. Report what was removed, retained, or blocked and which scopes still apply.
82
+ Resetting Project does not remove Global defaults, and resetting Global does
83
+ not erase project policy. Repeating a completed reset makes no file changes.
84
+ Reset does not disable ordinary read-only use of engineering defaults when a
85
+ later implementation or routing task loads this skill.
@@ -3,7 +3,7 @@ name: engineering-runtime
3
3
  description: Internal support package for shared Engineering Workflow executable behavior. Never select or invoke this package as a user capability.
4
4
  disable-model-invocation: true
5
5
  user-invocable: false
6
- release-version: 0.45.0
6
+ release-version: 0.45.1
7
7
  ---
8
8
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
9
9
  # Engineering Runtime
@@ -369,7 +369,7 @@
369
369
  "repository": "1aboveio/ai",
370
370
  "revision": "main"
371
371
  },
372
- "contentDigest": "8ab89f526fd30be9a81c8dc602d797e7aa8d2f09c63da0b56d8d214966e7e1fc",
372
+ "contentDigest": "e1a3eda72480a554a71b876b0803ffadb6d975f57ce73e9ae84e3a30a75630bc",
373
373
  "digestExcludes": []
374
374
  },
375
375
  {
@@ -382,7 +382,7 @@
382
382
  "repository": "1aboveio/ai",
383
383
  "revision": "main"
384
384
  },
385
- "contentDigest": "386ab76e0a90f031da690ca27ee5066684d895290ae0c97faabf6aaad94cd495",
385
+ "contentDigest": "4976da3d810ab0a712121dfc5acbd62f63f8ae42ec0116431ad7d27d0c52a324",
386
386
  "digestExcludes": []
387
387
  },
388
388
  {
@@ -395,7 +395,7 @@
395
395
  "repository": "1aboveio/ai",
396
396
  "revision": "main"
397
397
  },
398
- "contentDigest": "0399fc78af9e7823ace55e04aa867b30b12c738f2a47e28395184512525861bf",
398
+ "contentDigest": "32204a3fe185c2ea79eb27b0dd4055c321ef7b9f152ffc3a374b714ae8d465fa",
399
399
  "digestExcludes": []
400
400
  },
401
401
  {
@@ -408,7 +408,7 @@
408
408
  "repository": "1aboveio/ai",
409
409
  "revision": "main"
410
410
  },
411
- "contentDigest": "2bc51a5c6ed89007075d51f174c7b76d0a743b61f0d299c2067487679c86dd3f",
411
+ "contentDigest": "6dc6606527c8023eb1f79a188ae73bea4fafe8b339ed391a00fae60340107e0c",
412
412
  "digestExcludes": []
413
413
  },
414
414
  {
@@ -421,7 +421,7 @@
421
421
  "repository": "1aboveio/ai",
422
422
  "revision": "main"
423
423
  },
424
- "contentDigest": "c3cd951d823c6ce4f2b9b229892e450ad285e27cda157c5eead0d8ddc3d550f5",
424
+ "contentDigest": "0ec4a9d50c9918d1219a2454ea2aad7eb3ffdabe917319c55d7928c6d5e3580e",
425
425
  "digestExcludes": []
426
426
  },
427
427
  {
@@ -434,7 +434,7 @@
434
434
  "repository": "1aboveio/ai",
435
435
  "revision": "main"
436
436
  },
437
- "contentDigest": "639a25b40d67942c5355abee9d791b02784bedc50fa1f5fb8b4d90125f0b95e7",
437
+ "contentDigest": "388bd68865a9af12e76b1a522f879684546d5d03427649df5639b16d0b0240b9",
438
438
  "digestExcludes": []
439
439
  },
440
440
  {
@@ -447,7 +447,7 @@
447
447
  "repository": "1aboveio/ai",
448
448
  "revision": "main"
449
449
  },
450
- "contentDigest": "c595e281773af00b485dcb7d18e762f487b85761db42afa8287015581acdd8b5",
450
+ "contentDigest": "d7552f7681020f9cd4ed72dbde105adb5b172e40ba4119bcbb0d4685688faf18",
451
451
  "digestExcludes": []
452
452
  },
453
453
  {
@@ -460,7 +460,7 @@
460
460
  "repository": "1aboveio/ai",
461
461
  "revision": "main"
462
462
  },
463
- "contentDigest": "ec21e8eb116ccf6b3c1e798f4039fc2fa05558e63cae157e0bcb75ea81627d68",
463
+ "contentDigest": "414606c12207509b0d9207b0021dbb29bcb1689ca7d7486496ab2bc6a1dfecfc",
464
464
  "digestExcludes": []
465
465
  },
466
466
  {
@@ -473,7 +473,7 @@
473
473
  "repository": "1aboveio/ai",
474
474
  "revision": "main"
475
475
  },
476
- "contentDigest": "d973f6bb977f4cba06e26afa42a54bbaa90d29001086c87a83d84f335df590d4",
476
+ "contentDigest": "274f5ac6be3224dfdafaa4264cfa0ed223e3b98cf3cbd2c083b6c85314a92791",
477
477
  "digestExcludes": []
478
478
  },
479
479
  {
@@ -486,7 +486,7 @@
486
486
  "repository": "1aboveio/ai",
487
487
  "revision": "main"
488
488
  },
489
- "contentDigest": "43d2be290e65e536f0b9ff21087cce81c337158948edbdf901c609d3e73b9b0b",
489
+ "contentDigest": "a6efa258db14db8a4cab8600bcbdc2563c61531a51a486508ed42da70824be86",
490
490
  "digestExcludes": []
491
491
  },
492
492
  {
@@ -499,7 +499,7 @@
499
499
  "repository": "1aboveio/ai",
500
500
  "revision": "main"
501
501
  },
502
- "contentDigest": "73163c04711d6901162bd3cdb3a847db2845e8e51dbd53169ad13e7d2817f45c",
502
+ "contentDigest": "869bf4214b7e80e4968e4488f2f6ad4a944b2393a343ad40157e45f694457814",
503
503
  "digestExcludes": []
504
504
  },
505
505
  {
@@ -512,13 +512,13 @@
512
512
  "repository": "1aboveio/ai",
513
513
  "revision": "main"
514
514
  },
515
- "contentDigest": "9086b011f69d48e264c00241c6c1864e04678f791f575625cff2e788a2b58163",
515
+ "contentDigest": "bc78899c2a745aedee9f547a16b8c2be2ffab8a128695b033991802d033db303",
516
516
  "digestExcludes": [
517
517
  "coherence/workflow.json"
518
518
  ]
519
519
  }
520
520
  ],
521
- "releaseIdentity": "986e36012356e16fd54d77f0844860cd5ed9c4cac6f18ef1d3d540a3697dcfdf",
521
+ "releaseIdentity": "fed4e4c161cf525a08eee89fb30ba578ec21962b2d4cb9c9226fc61146fe4225",
522
522
  "lifecycleAuthority": "native-skills-cli",
523
523
  "repairRecipe": {
524
524
  "id": "engineering-workflow-dependency-first",
@@ -2,7 +2,7 @@
2
2
  name: ensure-coverage
3
3
  description: "Define or audit behavior-first test criteria — ACs, required test levels, mock/integration/E2E policy — across three axes: breadth (Coverage Ledger), depth (over-mocking), presentation (perceivability of browser surfaces). NOT judging whether a single test is any good (test-quality), authoring browser tests (e2e-test), reviewing a PR (better-review), or delivering issues (resolve-issues)."
4
4
  disable-model-invocation: true
5
- release-version: 0.45.0
5
+ release-version: 0.45.1
6
6
  ---
7
7
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
8
8
  # Ensure Coverage
@@ -3,7 +3,7 @@ name: golden-path
3
3
  description: "Golden-path E2E: the short list of user journeys whose failure blocks a release, kept in a repo as one contract (golden-paths.json) with a generated GOLDEN_PATHS.md and a generated GitHub Actions workflow, and run against a local build or a deployed URL for an ALIVE/DEAD verdict. Use to set golden paths up in a repo ('init golden paths', 'add golden-path CI'), to migrate an older smoke.manifest.json or a hand-built smoke setup ('audit', 'migrate smoke'), to add, change, or remove a golden path, to ask 'is the build alive?' or run them before a PR or release, or when a change touches a flow listed in GOLDEN_PATHS.md. NOT for writing the Playwright specs themselves (e2e-test), deciding what a change must prove (ensure-coverage), or general workflow YAML (github-actions)."
4
4
  dependencies:
5
5
  - e2e-test
6
- release-version: 0.45.0
6
+ release-version: 0.45.1
7
7
  ---
8
8
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
9
9
  # Golden path
@@ -3,7 +3,7 @@ name: harness-runtime
3
3
  description: Internal import-only library shared by first-party engineering packages. Not a workflow skill; never select or invoke it as a user capability.
4
4
  disable-model-invocation: true
5
5
  user-invocable: false
6
- release-version: 0.45.0
6
+ release-version: 0.45.1
7
7
  ---
8
8
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
9
9
  # Harness Runtime
@@ -8,7 +8,7 @@ dependencies:
8
8
  - better-review
9
9
  - golden-path
10
10
  - harness-runtime
11
- release-version: 0.45.0
11
+ release-version: 0.45.1
12
12
  ---
13
13
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
14
14
  # Resolve issues
@@ -4,7 +4,7 @@ description: "Slash/explicit-only (/resolve-release). Full GitHub Flow release f
4
4
  disable-model-invocation: true
5
5
  metadata:
6
6
  workflow-role: coordinator
7
- release-version: 0.45.0
7
+ release-version: 0.45.1
8
8
  ---
9
9
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
10
10
  # Resolve release
@@ -6,7 +6,7 @@ metadata:
6
6
  workflow-role: coordinator
7
7
  dependencies:
8
8
  - resolve-issues
9
- release-version: 0.45.0
9
+ release-version: 0.45.1
10
10
  ---
11
11
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
12
12
  # Rush issues (shortcut of resolve-issues)
@@ -6,7 +6,7 @@ metadata:
6
6
  workflow-role: coordinator
7
7
  dependencies:
8
8
  - resolve-release
9
- release-version: 0.45.0
9
+ release-version: 0.45.1
10
10
  ---
11
11
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
12
12
  # Rush release (shortcut of resolve-release)
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: test-quality
3
3
  description: "Seven principles for tests that catch real bugs, and an audit that reports weak, redundant, and not-coverage tests without fixing them. Use when writing, changing, or reviewing tests, or when asked whether tests are useful, redundant, over-mocked, flaky, only assert static text, or test config files, or asked to make a slow test suite faster without losing coverage, or when the user asks to write the testing conventions into a repo's CONTRIBUTING.md. NOT defining what a spec must prove (ensure-coverage) or authoring browser tests (e2e-test)."
4
- release-version: 0.45.0
4
+ release-version: 0.45.1
5
5
  ---
6
6
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
7
7
  # Test Quality