codeassembly-guidance 0.3.0 â 0.5.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/.meta/changelog.json +385 -272
- package/CHANGELOG.md +39 -0
- package/README.md +8 -40
- package/content/_partials/guidance-change-since-capture.md +9 -0
- package/content/codeassembly-content.yaml +2 -0
- package/content/collections/recommended.md +1 -1
- package/content/guidance/rulebooks/shared-data-conventions.md +4 -2
- package/content/scripts/check-prose.mjs +38 -38
- package/content/scripts/select-lede-exemplars.mjs +53 -53
- package/content/skills/_data/artifact-conventions.md +9 -423
- package/content/skills/_partials/cluster-feedback-events.md +21 -0
- package/content/skills/_partials/plan-template.md +1 -1
- package/content/skills/_partials/ticket-criteria-conventions.md +1 -1
- package/content/skills/capture-event/capture-event.mjs +32 -32
- package/content/skills/curate-feedback/SKILL.md +102 -0
- package/content/skills/curate-feedback/curate-feedback.mjs +211 -0
- package/content/skills/kb-add/kb-add.mjs +53 -53
- package/content/skills/kb-curate/kb-curate.mjs +64 -64
- package/content/skills/kb-edit/kb-edit.mjs +61 -61
- package/content/skills/kb-update-events/kb-update-events.mjs +19 -19
- package/content/skills/lesson-clusters/lesson-clusters.mjs +47 -47
- package/content/skills/migrate-feedback-memories/feedback-memories.mjs +75 -75
- package/content/skills/refine-guidance/SKILL.md +1 -1
- package/content/skills/revise-prose/revise-prose.mjs +66 -66
- package/content/skills/save-artifact/SKILL.md +2 -2
- package/content/skills/streamline-guidance/streamline-guidance.mjs +30 -30
- package/content/skills/triage-feedback/SKILL.md +8 -23
- package/content/skills/triage-feedback/triage-feedback.mjs +7 -7
- package/content/skills/triage-spike-findings/SKILL.md +1 -1
- package/content/subagents/feedback-coverage-judge.md +95 -0
- package/content/subagents/feedback-triage-challenger.md +10 -5
- package/content/subagents/plan-reviewer.md +8 -7
- package/package.json +6 -6
- package/schemas/preferences.v1.json +1 -1
- package/schemas/work-types.v1.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,45 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
|
4
4
|
|
|
5
|
+
## 0.5.0 â 2026-11-02
|
|
6
|
+
|
|
7
|
+
### ð Features
|
|
8
|
+
|
|
9
|
+
- Adds rules to the `shared-data-conventions` rulebook stating that an agent's verdict that decides a write to shared state includes evidence that a script checks before the write, and that a skill writing to shared state runs against the real data before merge, stopping at its approval checkpoint or in a dry run. (#2245)
|
|
10
|
+
- Extends the data-change guidance in `create-ticket`, `design-and-plan`, `plan`, and `align-ticket-with-implementation` to require an acceptance criterion for the evidence check and a `## Verification` step that runs the skill against the real data without writing. (#2245)
|
|
11
|
+
- Adds a "Judged writes" check to `plan-reviewer`, which reports a plan for a skill that writes to shared state when the plan does not run the skill against the real data before merge or does not name the script that checks a verdict's evidence. (#2245)
|
|
12
|
+
|
|
13
|
+
### ðĶ Dependencies
|
|
14
|
+
|
|
15
|
+
- Pins `codeassembly` and `@williamthorsen/kb` in guidance to their published releases `0.20.0` and `0.11.1` in place of `workspace:*`, and exempts both from the 24-hour `minimumReleaseAge` in `pnpm-workspace.yaml` so that guidance can install a release as soon as this repository's CI publishes it. (#2246)
|
|
16
|
+
|
|
17
|
+
### ð Documentation
|
|
18
|
+
|
|
19
|
+
- Moves the `run-index.json`, `run-log.jsonl`, and `status.json` specification from guidance's `artifact-conventions.md` to `packages/run-core/docs/run-data-format.md`, beside the Zod schemas that implement it. (#2246)
|
|
20
|
+
|
|
21
|
+
## 0.4.0 â 2026-11-02
|
|
22
|
+
|
|
23
|
+
### ð Features
|
|
24
|
+
|
|
25
|
+
- Adds the `curate-feedback` skill, which has `feedback-coverage-judge` subagents sort each open feedback event into covered, duplicate, obsolete, or kept against guidance pinned at a commit, and then, after approval or under `--apply`, marks every event that is not kept through `kb-update-events` and records the run in a `feedback-curation` artifact. (#2231)
|
|
26
|
+
- Adds each covered entry's quote to the `feedback-curation` artifact's events table and to the approval table that `curate-feedback --list` presents, so that the developer can check every covered verdict against its stating sentence before approving the marks. (#2236)
|
|
27
|
+
|
|
28
|
+
### ðŠĶ Removed
|
|
29
|
+
|
|
30
|
+
- Remove the factory and the demos (#2234)
|
|
31
|
+
|
|
32
|
+
Removes the dormant factory visualization package and the catwalk demos, together with the docs, repo-local skills, dependencies, and configuration that only they used. Adds to `docs/repository-split.md` the command that finds the last commit containing the factory, which is the commit from which a revival restores it.
|
|
33
|
+
|
|
34
|
+
### ð Bug fixes
|
|
35
|
+
|
|
36
|
+
- Fixes the issue that the `feedback-coverage-judge` subagent of `curate-feedback` marked a feedback event `obsolete` when the change that removed the event's target had renamed or moved it, or had named a replacement for it. (#2233)
|
|
37
|
+
- Fixes the issue that `curate-feedback validate` accepted a `covered` entry after checking only that the cited guidance file existed, by requiring a verbatim `quote` of the stating sentence and rejecting the entry when the file at the pin does not contain it, ignoring differences in whitespace and in `*`, `_`, and backtick markers. (#2236)
|
|
38
|
+
- Fixes the issue that `triage-feedback` ranked a feedback cluster by its events even when all of them predated a change to the guidance that governs its lesson, and directs the skill and its `feedback-triage-challenger` subagent to check that guidance's commit history and set such a cluster to `low` unless evidence shows the failure recurring under the changed guidance. (#2243)
|
|
39
|
+
- Fixes the issue that `triage-feedback` and `triage-spike-findings` accepted a defense against the challenger that rested on grounds other than the evidence named by the challenger's argument. (#2243)
|
|
40
|
+
- Remove the unshipped `source` export condition from the published packages (#2244)
|
|
41
|
+
|
|
42
|
+
Removes the `source` export condition from `codeassembly`, `@williamthorsen/kb`, and `codeassembly-run-core`, because it pointed at TypeScript files that their tarballs don't contain, so that a consumer that enables the condition resolves the shipped `dist/` output instead of failing.
|
|
43
|
+
|
|
5
44
|
## 0.3.0 â 2026-11-01
|
|
6
45
|
|
|
7
46
|
### ð Features
|
package/README.md
CHANGED
|
@@ -2,49 +2,16 @@
|
|
|
2
2
|
|
|
3
3
|
# codeassembly-guidance
|
|
4
4
|
|
|
5
|
-
The CodeAssembly library of agent guidance: rulebooks, skills, and subagents for coding harnesses, which the [`codeassembly`](
|
|
5
|
+
The CodeAssembly library of agent guidance: rulebooks, skills, and subagents for coding harnesses, which the [`codeassembly`](https://github.com/williamthorsen/codeassembly/blob/main/packages/agents/README.md) CLI deploys into Claude Code and Rovo Dev.
|
|
6
6
|
|
|
7
7
|
<!-- section:release-notes -->
|
|
8
|
-
## Release notes â v0.
|
|
8
|
+
## Release notes â v0.5.0 (2026-11-02)
|
|
9
9
|
|
|
10
10
|
### ð Features
|
|
11
11
|
|
|
12
|
-
- Adds
|
|
13
|
-
-
|
|
14
|
-
- Adds a
|
|
15
|
-
- Adds a rule to the `williamthorsen-collaboration-preferences` rulebook that directs the agent, once the developer signals overload, to stop adding asks and to end each turn without an action-items block until the developer asks for something, and points `action-items.md` and the `collaborate` skill to it. (#2175)
|
|
16
|
-
- Adds a "Check results" section to the `cli-conventions` rulebook, which requires a `check` or `verify` mode, a health probe, or a pre-flight to state on each item's line what it checked and the state that it found, to show a failure's evidence (a diff or the actual state) without `--verbose`, and to probe end to end the function that a configuration-only check serves. (#2178)
|
|
17
|
-
- Adds a "Documentation placement" section to the shared `AGENTS.md` guidance, which directs an agent that writes a guidance or documentation file to point to the config, code, README section, or rulebook that defines a fact and to add only what that source does not state. (#2181)
|
|
18
|
-
- Directs the plan template used by `plan` and `design-and-plan` to name, in the key decisions of each task that writes guidance or documentation, the source that defines each documented fact. (#2181)
|
|
19
|
-
- Adds a placement item to the diff audit run by `implement-plan`, `respond-to-review`, and `revise-comments`, which checks that each guidance or documentation hunk points to a fact's source rather than copying the fact. (#2181)
|
|
20
|
-
- Extends the duplication check in `update-project-guidance` from the global guidance file to rulebooks loaded into the session and to repository files, so that the skill omits what loaded guidance already states and points to a repository file that defines a fact. (#2181)
|
|
21
|
-
- Changes the marker that the `williamthorsen-collaboration-preferences` rulebook and the plan and option-format templates prescribe for a decision awaiting the developer's checkpoint from âģ to ðē, an unchecked box that reads as an item still to approve rather than as work in progress. (#2185)
|
|
22
|
-
- Adds a `defects` field to the JSON output of `consolidate-entries`, which lists each entry whose breaking marker violates its type's policy or whose type the taxonomy does not declare, naming the entry by its 0-based index with the same `policy-violation` and `undeclared-type` kinds that `resolve-merge` reports. (#2186)
|
|
23
|
-
- Directs `summarize-change` to report each entry defect that `consolidate-entries` returns, naming the entry by its `text`, and to continue without changing anything. (#2186)
|
|
24
|
-
- Adds the closing post to `spike-conventions.md`, a ticket comment that contains the answers to the ticket's questions, the recommendations on its decisions, and links to the findings artifact and, when the spike published one, to its page, and names the post in the deliverables of the spike ticket and plan templates. (#2196)
|
|
25
|
-
- Adds an offer of the closing post to the action-items block of the `assess-usability` report step, and replaces the skill's statement that it writes nothing remote with one that names this post, made on consent, as its one remote write. (#2196)
|
|
26
|
-
- Extends the ðŽ Investigate option for a spike plan, shown in the next-steps menu of `design-and-plan`, `plan`, `refine-plan`, and `save-plan`, to end the run with the plan's `## Deliverable`, which includes the offer of the closing post. (#2196)
|
|
27
|
-
- Adds a rule to `artifact-conventions.md` that a conclusion needed by a reader of the ticket is posted on the ticket, while the artifact keeps the evidence. (#2196)
|
|
28
|
-
- Adds the `pr.initial_state` preference (`draft` or `ready`, default `draft`), which `create-pr` reads from the project or global preferences file to open a pull request as a draft or ready for review, and makes `pr.title_format` optional so that a `pr` section can set only the state. (#2198)
|
|
29
|
-
- Adds the `--add-tag` operation to `kb-update-events`, which appends the given tags, canonicalized through the store's alias map, to each named event's tags and leaves an event that already has all of them untouched, unlike `--retag`, which replaces the whole set. (#2208)
|
|
30
|
-
- Adds `--help` to the `kb-update-events` helper, which prints usage describing every operation and exits without updating any event. (#2208)
|
|
31
|
-
- Adds an `--exclude-tag` flag to `kb-retrieve-events` that takes a comma-separated list of tags, matched in canonical or alias form, and drops every event that has any of them; a repeated flag adds to the list. (#2209)
|
|
32
|
-
- Adds a "Standard tags" section, generated from `STANDARD_TAGS`, to the skills that write or filter knowledge-base tags, such as `capture-event` and `kb-update-events`, which directs the agent to tag a record's disposition by a standard name rather than a variant spelling. (#2212)
|
|
33
|
-
- Adds an optional `evidence` field (a stable `key` and the `paths` that it covers) to each item of the `triage-spike-findings` record and an optional `commit` field to the record, which `validate` requires once any item has evidence, and adds to the end of the dispositions comment a hidden, versioned JSON block that the exported `parseEvidenceBlock` function reads back. (#2213)
|
|
34
|
-
- Has the `triage-spike-findings` skill copy each item's evidence key and paths from the findings into the inventory and the record, and set the record's `commit` to the HEAD at which the developer approved the dispositions. (#2213)
|
|
35
|
-
- Adds the `assess-code-health` skill, which measures git hotspots and test coverage for one package or subtree, dispatches five `code-health-assessor` subagents (conventions, structure, extraction, error handling, and tests), and ranks the proposals whose cited evidence resolves against the tree in a `code-health-findings` artifact that `triage-spike-findings` now accepts as input. (#2216)
|
|
36
|
-
- Adds the `triage-feedback` skill, which groups the open events of a feedback store by lesson, shows the top `--limit` clusters with each one's recurrence, impact, and latest capture, has a subagent without session context challenge every priority, and after one approval files a ticket, comments on an open issue that already covers the lesson, defers the cluster, or changes its impact rating. (#2217)
|
|
37
|
-
- Adds the `triage_feedback.defer_days` preference, which sets the number of days for which `triage-feedback` leaves a deferred cluster out of a triage unless the cluster gains a new event, 30 by default. (#2217)
|
|
38
|
-
- Adds the `refine-guidance` skill, which finds the rule that already states a lesson or places a new artifact, drafts the edits for approval, opens a pull request, and marks the lesson's feedback events as addressed by it. (#2227)
|
|
39
|
-
- Adds a "Choosing a kind" section to the `codeassembly-content-specification` rulebook, which states the kind of artifact and the content root in which a lesson belongs, and when to change an existing rule rather than add a parallel one. (#2227)
|
|
40
|
-
|
|
41
|
-
### ð Bug fixes
|
|
42
|
-
|
|
43
|
-
- Fixes the issue that the commit guidance did not say which source sets a commit title's format, by stating in `commit-conventions` that `commit.title_format` alone sets it and by directing agents in `create-commit` and the shared `AGENTS.md` not to change a rendered title to match other commits or comment on whether it contains a ticket reference. (#2172)
|
|
44
|
-
- Fixes the issue that `create-commit` and `condense-branch` did not give agents a title to use when `commit.title_format` is empty or unset and the renderer printed an empty title; both now fall back to the bare title. (#2172)
|
|
45
|
-
- Fixes the issue that `index-prototypes` had the agent ask the developer to run `chrome-debug`, which is no longer installed, on a refused Playwright connection, rather than run `thor-chrome` itself and ask only when `thor-chrome` refuses the launch with `session-unavailable`. (#2192)
|
|
46
|
-
- Fixes the issue that a section in the project `.agents/preferences.yaml` hid every global key of the same section, such as a `ticket.base_url` set only in `~/.agents/preferences.yaml`, which made `derive-session-context` report `ticket_base_url: null` and leave a Jira ticket ID without a URL. (#2199)
|
|
47
|
-
- Fixes the issue that the `--tag` filter of `kb-retrieve` and `kb-retrieve-events` compared tags literally and missed a note tagged with an alias of the requested tag, although both skills document a match on the canonical or alias form. (#2209)
|
|
12
|
+
- Adds rules to the `shared-data-conventions` rulebook stating that an agent's verdict that decides a write to shared state includes evidence that a script checks before the write, and that a skill writing to shared state runs against the real data before merge, stopping at its approval checkpoint or in a dry run. (#2245)
|
|
13
|
+
- Extends the data-change guidance in `create-ticket`, `design-and-plan`, `plan`, and `align-ticket-with-implementation` to require an acceptance criterion for the evidence check and a `## Verification` step that runs the skill against the real data without writing. (#2245)
|
|
14
|
+
- Adds a "Judged writes" check to `plan-reviewer`, which reports a plan for a skill that writes to shared state when the plan does not run the skill against the real data before merge or does not name the script that checks a verdict's evidence. (#2245)
|
|
48
15
|
<!-- /section:release-notes -->
|
|
49
16
|
|
|
50
17
|
## Using the library
|
|
@@ -54,13 +21,13 @@ A declaration names the library as a source and selects artifacts from it, usual
|
|
|
54
21
|
```yaml
|
|
55
22
|
sources:
|
|
56
23
|
- name: codeassembly-guidance
|
|
57
|
-
path: ~/repos/codeassembly/packages/guidance/content
|
|
24
|
+
path: ~/repos/codeassembly-guidance/packages/guidance/content
|
|
58
25
|
collections:
|
|
59
26
|
use:
|
|
60
27
|
- recommended
|
|
61
28
|
```
|
|
62
29
|
|
|
63
|
-
Then run `codeassembly install` and `codeassembly sync --global`. A project declares the same in its own `.agents/codeassembly.yaml` and runs `codeassembly sync`. [Project declaration](
|
|
30
|
+
Then run `codeassembly install` and `codeassembly sync --global`. A project declares the same in its own `.agents/codeassembly.yaml` and runs `codeassembly sync`. [Project declaration](https://github.com/williamthorsen/codeassembly/blob/main/packages/agents/docs/project-declaration.md) documents the declaration format.
|
|
64
31
|
|
|
65
32
|
## What the content contains
|
|
66
33
|
|
|
@@ -109,3 +76,4 @@ codeassembly-validate-preferences --strict .agents/preferences.yaml
|
|
|
109
76
|
- [Findings triage helper](docs/triage-spike-findings-helper.md): the helper that the `triage-spike-findings` skill runs.
|
|
110
77
|
- [Code-health helper](docs/assess-code-health-helper.md): the helper that the `assess-code-health` skill runs.
|
|
111
78
|
- [Feedback triage helpers](docs/triage-feedback-helper.md): the helpers that the `triage-feedback` skill runs.
|
|
79
|
+
- [Feedback curation helper](docs/curate-feedback-helper.md): the helper that the `curate-feedback` skill runs.
|
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
A cluster whose events all predate a change to the guidance that governs its lesson is evidence about guidance that no longer exists: It does not show that the failure recurs under the current guidance. Before you judge a cluster's priority, check whether that guidance changed after the cluster's latest capture, `signals.latestCapturedAt` in the clusters file.
|
|
2
|
+
|
|
3
|
+
Check each artifact that states or should state the lesson: the target, every artifact that your search found stating the lesson, and every partial that one of them includes.
|
|
4
|
+
|
|
5
|
+
1. Find the artifact's source file in the repository that owns it. A guidance-library artifact's source is under `packages/guidance/content/` in the CodeAssembly guidance repository (`williamthorsen/codeassembly-guidance`), at its path relative to the content root, such as `subagents/entry-drafter.md`.
|
|
6
|
+
2. List the commits on the owning repository's default branch that touched the source file after the latest capture: `gh api 'repos/{owner}/{repo}/commits?path={path}&since={latestCapturedAt}' --jq '.[] | [.sha[0:8], .commit.committer.date, (.commit.message | split("\n")[0])] | @tsv'`. Only when `gh` cannot reach the repository, read a local clone of it at its remote's default branch, never at the checked-out branch, which may predate the change: `git -C {clone} log --first-parent --since={latestCapturedAt} --format='%h %cs %s' origin/HEAD -- {path}`. The clone shows history only up to its last fetch.
|
|
7
|
+
3. Read the message of each listed commit, with `gh api repos/{owner}/{repo}/commits/{sha} --jq .commit.message`, or with `git -C {clone} show --no-patch --format=%B {sha}` on the fallback route. A commit changed the guidance when it changed what the artifact tells the agent to do about the lesson. A commit that only repairs prose, reformats, or renames does not.
|
|
8
|
+
|
|
9
|
+
The guidance changed after the latest capture when at least one commit changed it; name the latest such commit by its short SHA, date, and subject. Otherwise, it did not change.
|
|
@@ -53,6 +53,8 @@ helpers:
|
|
|
53
53
|
out: skills/create-ticket/resolve-ticket-target.mjs
|
|
54
54
|
- entry: ../src/assess-code-health/cli.ts
|
|
55
55
|
out: skills/assess-code-health/assess-code-health.mjs
|
|
56
|
+
- entry: ../src/curate-feedback/cli.ts
|
|
57
|
+
out: skills/curate-feedback/curate-feedback.mjs
|
|
56
58
|
- entry: ../src/lesson-clusters/cli.ts
|
|
57
59
|
out: skills/lesson-clusters/lesson-clusters.mjs
|
|
58
60
|
- entry: ../src/triage-feedback/cli.ts
|
|
@@ -36,6 +36,6 @@ The skills belong here on different grounds. A rulebook of the personal collecti
|
|
|
36
36
|
|
|
37
37
|
Adding a skill that declares a guidance hook has a drawback that the current members do not have. A project declaring this collection deploys its own copy of that skill, and that copy shadows the user's home-bound one. Because guidance-hook bindings do not cross the boundary between the user-global and project domains, guidance bound globally by the developer goes missing in that repository until the project binds it too. Weigh that against the general applicability claimed by membership before admitting such a skill.
|
|
38
38
|
|
|
39
|
-
`shared-data-conventions` qualifies on its own terms too. It states a standard practice, expand, migrate, contract,
|
|
39
|
+
`shared-data-conventions` qualifies on its own terms too. It states a standard practice, expand, migrate, contract, the rule that unmerged code does not write to shared state, and the checks that a skill writing to shared state needs before merge, and it does not name any author, platform, or store: Each repository's `AGENTS.md` names its own. Its body does not contain any invocation token, so its closure is empty.
|
|
40
40
|
|
|
41
41
|
`ui-copy-conventions` qualifies on its own terms as well. What it asks of the text on a page follows from who reads that text, the person who returns to the page every week, rather than from a preference, and it does not name any author, repository, product, or tool. A project that has content guidelines of its own names them, and they take precedence. Its body does not contain any invocation token, so its closure is empty.
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
slug: shared-data-conventions
|
|
3
|
-
description: 'Changes to shared data: unmerged code never writes to a shared store, and a change to the shape of persisted data proceeds as expand, migrate, contract. Consult before planning, implementing, or reviewing a change that alters the shape of persisted data or writes to a shared store.'
|
|
3
|
+
description: 'Changes to shared data: unmerged code never writes to a shared store, a verdict that decides such a write includes evidence that a script checks, a skill that makes such writes runs read-only against the real data before merge, and a change to the shape of persisted data proceeds as expand, migrate, contract. Consult before planning, implementing, or reviewing a change that alters the shape of persisted data or writes to a shared store.'
|
|
4
4
|
delivery: [skill]
|
|
5
|
-
version: '
|
|
5
|
+
version: '2'
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Shared data conventions
|
|
@@ -10,5 +10,7 @@ version: '1'
|
|
|
10
10
|
Shared state is any store that a deployed product or another person reads, such as a production database or a content dataset. A local or disposable copy is not shared. The repository's `AGENTS.md` names which stores are shared and how their migrations run.
|
|
11
11
|
|
|
12
12
|
- **Writes.** Unmerged code never writes to shared state, even when a plan or a ticket directs it. Asked to run a migration or another write against shared state from a branch, decline and name the route: Merge, then run it from merged code.
|
|
13
|
+
- **Judged writes.** When the verdict of an agent or a subagent decides a write to shared state, the verdict includes evidence that a script checks before the write, such as a quote that the script finds in the cited file, a commit that exists, or a date that it compares with history. The script refuses a verdict whose evidence fails the check. A prose instruction to the judge does not replace the check: Fixtures exercise the mechanics around a verdict, not the judgment on real data.
|
|
14
|
+
- **Real-data run.** Before merge, a skill that writes to shared state runs against the real data in a mode that stops before the write: its approval checkpoint, or a dry run. The agent reviews each verdict that the run would act on, and a wrong verdict is fixed on the branch. The run only reads, so **Writes.** still holds.
|
|
13
15
|
- **Sequence.** A change to the shape of data proceeds as expand, migrate, contract. Expand adds the new shape alongside the old one, migrate moves the data, and contract removes the old shape once the deployed code no longer reads it. Each step is its own change, merged and deployed before the next begins, so that every order of deploy and migration leaves the product working.
|
|
14
16
|
- **Migrations.** A migration runs from merged code, by automation or by the developer, and by an agent only when the developer directs that run. It defaults to a dry run and is idempotent.
|