Release: working-process 0.17.0, salesforce-standards 0.4.0, project-memory 0.5.1, python-standards 0.3.2

.claude-plugin/marketplace.json

@@ -17,7 +17,7 @@
     {
       "name": "salesforce-standards",
       "source": "./plugins/salesforce-standards",
-      "description": "Salesforce coding standards for the sf CLI toolchain: area skills for Apex, LWC, Flow, data and security model plus maintenance-first legacy UI, a code-review stack, a plan-review checklist, and a salesforce-toolchain rule"
+      "description": "Salesforce coding standards for the sf CLI toolchain: area skills for Apex, Apex triggers, LWC, Flow, data and security model plus maintenance-first legacy UI, a code-review stack, a plan-review checklist, and a salesforce-toolchain rule"
     },
     {
       "name": "project-memory",

.claude/rules/plugin-versioning.md

@@ -18,27 +18,39 @@ paths:
   merging to master without changing that string delivers nothing to
   existing users, so a release PR with no bumps for its changed
   plugins is invalid.
+- Every plugin keeps a `CHANGELOG.md` at its root: released versions
+  newest first, each heading carrying the version and its date. The file
+  installs with the plugin, so a copy on disk carries the history of
+  exactly that copy, and a plugin whose only change is that file still
+  takes a patch bump.
+- A topic branch writes its entry under an `## Unreleased` heading at
+  the top of the file, before it merges into `develop`, while the author
+  still knows what the change means. The release PR renames that heading
+  to `## <version> — <date>` in the commit that mints the version, and
+  the PR body is assembled from the entries that changed.
 - Dogfooding unreleased content needs a changed version string — the
   plugin cache keys content by version. A topic branch that dogfoods a
   plugin sets `X.Y.Z-dev.<discriminator>` on it — the issue number the
   branch name carries, or the branch short-name when the topic has no
-  issue (e.g. `-dev.design-personas`). Widening the discriminator
-  instead of minting another channel keeps one channel for one purpose;
-  the discriminator only needs to be unique among parallel topics. The
-  suffix flows into develop as-is. A topic that
-  does not dogfood never touches the version. On a version-line merge
-  conflict between parallel topics, the merging topic's own
-  `-dev.<discriminator>` wins — both strings are provisional. The release PR
-  strips every `-dev` suffix while minting the final numbers; the
-  `release-guard` workflow fails any PR to master that carries a
-  prerelease version or a changed plugin without a bump.
+  issue (e.g. `-dev.design-personas`). The suffix hangs off a version
+  above the one `develop` currently carries — never a re-suffix of a
+  version already minted. Widening the discriminator instead of minting
+  another channel keeps one channel for one purpose; the discriminator
+  only needs to be unique among parallel topics. The suffix flows into
+  develop as-is. A topic that does not dogfood never
+  touches the version. On a version-line merge conflict between parallel
+  topics, the merging topic's own `-dev.<discriminator>` wins — both
+  strings are provisional. The release PR strips every `-dev` suffix
+  while minting the final numbers; the `release-guard` workflow fails
+  any PR to master that carries a prerelease version or a changed plugin
+  without a bump.
 - Prerelease grammar: `-<channel>.<discriminator>`. Defined channels:
-  `dev.<discriminator>` (topic-branch dogfooding, above) and `rc.<n>` (release
-  candidate — a freeze of develop dogfooded as one bundle when a
-  release warrants whole-unit validation; minted by a release-prep
-  commit and stripped by the release PR like any prerelease). Future
-  channels extend this list by editing this rule only — the
-  release-guard workflow rejects every prerelease on master
+  `dev.<discriminator>` (topic-branch dogfooding, above) and
+  `rc.<n>` (release candidate — a freeze of develop dogfooded as one
+  bundle when a release warrants whole-unit validation; minted by a
+  release-prep commit and stripped by the release PR like any
+  prerelease). Future channels extend this list by editing this rule
+  only — the release-guard workflow rejects every prerelease on master
   (`*-*`), so new channels never need a CI change.
   - **patch** — wording or docs fixes, no behavior change;
   - **minor** — a new component or section, backward-compatible behavior

.github/workflows/release-guard.yml

@@ -1,7 +1,9 @@
 # Release guard — runs on PRs targeting master (release PRs from develop).
 # Enforces the plugin-versioning rule's release-time invariants:
 #   1. no prerelease (-dev.*) version string reaches master;
-#   2. every plugin changed since master carries a version bump.
+#   2. every plugin changed since master carries a version bump;
+#   3. a bumped plugin's changelog names that version at its top;
+#   4. no Unreleased section survives the release.
 name: release-guard
 
 on:
@@ -30,6 +32,43 @@ jobs:
           done
           exit $fail
 
+      - name: A bumped plugin's changelog names the new version
+        run: |
+          base="origin/${{ github.base_ref }}"
+          fail=0
+          for d in plugins/*/; do
+            name=$(basename "$d")
+            manifest="${d}.claude-plugin/plugin.json"
+            head_v=$(jq -r .version "$manifest")
+            base_v=$(git show "$base:$manifest" 2>/dev/null | jq -r .version || echo "<absent>")
+            if [ "$base_v" = "$head_v" ]; then continue; fi
+            changelog="${d}CHANGELOG.md"
+            if [ ! -f "$changelog" ]; then
+              echo "::error file=$manifest::plugin '$name' moved to '$head_v' but ships no CHANGELOG.md"
+              fail=1
+              continue
+            fi
+            top=$(grep -m1 '^## ' "$changelog" || true)
+            escaped=$(printf '%s' "$head_v" | sed 's/[.]/\\./g')
+            if ! printf '%s\n' "$top" | grep -qE "^## $escaped — [0-9]{4}-[0-9]{2}-[0-9]{2}$"; then
+              echo "::error file=$changelog::plugin '$name' moved to '$head_v' but its top heading reads '$top' — expected '## $head_v — <YYYY-MM-DD>'"
+              fail=1
+            fi
+          done
+          exit $fail
+
+      - name: No Unreleased section reaches master
+        run: |
+          fail=0
+          for f in plugins/*/CHANGELOG.md; do
+            [ -f "$f" ] || continue
+            if grep -q '^## Unreleased' "$f"; then
+              echo "::error file=$f::rename the Unreleased heading to the minted version before releasing"
+              fail=1
+            fi
+          done
+          exit $fail
+
       - name: Changed plugins carry a bump
         run: |
           base="origin/${{ github.base_ref }}"

README.md

@@ -18,7 +18,7 @@ Marketplace of [Claude Code](https://code.claude.com) plugins by Missing Bits.
 |--------|------|-------------|
 | `working-process` | [README](plugins/working-process/README.md) | Spec-driven working process: grilling-session, architect-session, system-designer-session, process-status and sync-rules skills, architect and plan-adversary verdict agents, two verdict-free consultation agents, propagation-auditor and integrity-auditor audit agents, distributed process rules |
 | `python-standards` | [README](plugins/python-standards/README.md) | Python coding standards for uv + ruff + pytest + pyright: area skills, code-review stack, plan-review checklist, distributed toolchain rule |
-| `salesforce-standards` | [README](plugins/salesforce-standards/README.md) | Salesforce coding standards for the sf CLI toolchain: area skills (Apex, LWC, Flow, data/security model, legacy UI), code-review stack, plan-review checklist, distributed toolchain rule |
+| `salesforce-standards` | [README](plugins/salesforce-standards/README.md) | Salesforce coding standards for the sf CLI toolchain: area skills (Apex, Apex triggers, LWC, Flow, data/security model, legacy UI), code-review stack, plan-review checklist, distributed toolchain rule |
 | `project-memory` | [README](plugins/project-memory/README.md) | In-repo project memory: committed Team memory (`docs/memory/`) and per-user Private memory (`.claude/memory/`), with `memory-review-session`, `migrate-memory`, and `redirect-memory` skills, distributed as a Rules payload |
 
 ## License

docs/domain/glossary.md

@@ -134,6 +134,14 @@ bracket slot (`[Minor]`). The collective noun is
 model-capability ladder.
 _Avoid_: severity tier
 
+**Origin**:
+The document a review finding traces to — `plan`, `spec`, or `both` —
+named by the reviewer that found it rather than derived at triage. A
+finding originating in the spec is held unless a written decision
+licenses the edit, since editing a spec from inside a plan review is
+design work.
+_Avoid_: owner (for a document), source
+
 **Rule tag**:
 The inline parenthesized annotation at a rule's (or sub-rule's)
 definition site carrying its identity and grade:
@@ -339,7 +347,11 @@ scope. Those dispatch-time fields are immutable — they say what one
 reviewer was given and returned — while a later event about that round
 appends after the heading's closing parenthesis, never inside it. The
 loop's derived state — round count, the all-Minor signal, the
-diff-scoped chain — is read by folding these.
+diff-scoped chain — is read by folding these. The latest round heading
+is the one carrying the highest ordinal, wherever it sits in the
+section: the rules prescribe no order for the blocks, and live ledgers
+run both ways. Ordinals run per document and per field, and continue
+across loops rather than restarting.
 _Avoid_: round title, round record (for the heading alone)
 
 **Disposition line**:
@@ -363,14 +375,30 @@ responsibility for the part no round re-read — or explicitly decline to.
 The consumption gate owns it, not the loop, which owes nothing further
 once it terminates. Discharged three ways: an integrity audit, any later
 full-document round whatever its verdict, or the developer's recorded
-decline — of the gate's pair offer, or, where the document is already
-implemented and the gate never fired, of the question that offer would
-have put. Recorded as `, debt discharged <date>` appended to that LGTM's
-round heading, and the record says only that it happened and when, never
-how or how well. Distinct from the diff-scoped chain itself, the
-round-one-plus-reviewed-waves structure the LGTM certifies.
+decline. What they decline is the gate's pair offer — or, where the
+document is already implemented and the gate never fired, the question
+that offer would have put. Recorded as `, debt discharged <date>`
+appended to that LGTM's round heading, and the record says only that it
+happened and when, never how or how well. Distinct from the diff-scoped
+chain itself, the round-one-plus-reviewed-waves structure the LGTM
+certifies.
 _Avoid_: chain accepted, chain closed, unclosed chain
 
+**Confirming round**:
+The full-document round a plan's loop owes before it may close, whenever
+the latest round heading is diff-scoped — whatever path would otherwise
+end the rounds. A plan already `implemented` owes none: there the round
+is discharged by recorded decline without any dispatch, as the sibling
+chain debt is, since completed work is not re-reviewed. It runs as the
+same loop's last round, counts against the round cap like any other, and
+its verdict is the one stamped; on a plan the resolution annotation and
+the adjudication wait for it. It inherits the gating of whatever ended
+the rounds: autonomous where autonomy still stands, the developer's to
+order after a terminator that suspends it. A spec owes none: its
+diff-scoped chain is discharged at the consumption gate, where a
+full-document round is one arm of the pair offer.
+_Avoid_: final round, closing round, full read (as the name)
+
 **Document branch**:
 The local branch a review loop's per-round commits live on, named
 `<topic>.docs` — git refuses a ref nested under an existing branch, so a
@@ -392,12 +420,26 @@ _Avoid_: review agent (unqualified), reviewer agent
 
 **Relay**:
 The delivery of a background agent's result to the developer before any
-further action on it — a verdict agent's report before its stamp (the
-verdict, the model self-report, and every finding in substance), a
-consultation's Contribution attributed and substantially verbatim. The
-developer's standing veto point.
+further action on it — a verdict agent's report before its stamp (a
+header carrying the verdict, the model self-report and the counts, then
+one line per finding, that list never condensed), a consultation's
+Contribution digested one paragraph per focusing question. Either way it
+names the Dispatch record holding the full text. The developer's
+standing veto point.
 _Avoid_: report back, forward (as the term)
 
+**Dispatch record**:
+The file a dispatcher writes before relaying a background agent's
+result — one dispatch, one file, holding what the agent returned
+verbatim under a four-line header (date, agent, model self-report,
+subject). Kept per subject under `.claude/working-process/<stem>/`,
+git-ignored, and NOT a Process directory — a per-checkout store under
+the `.claude/` config namespace, as Private memory is a per-user one. It
+survives compaction, the session's end and a branch switch, and no more:
+that bound is what lets a Relay condense. Never a Review report, the
+counted document a code-review run writes under `docs/code-review/`.
+_Avoid_: dispatch log, transcript file
+
 **Session skill**:
 A skill whose content is an open-ended conversation, named `*-session` —
 `architect-session`, `grilling-session`, `memory-review-session` among
@@ -416,9 +458,10 @@ _Avoid_: informal review, advisory review
 
 **Contribution**:
 What a consultation returns: reasoning, options, and the questions the
-persona would need answered next, relayed to the developer attributed and
-substantially verbatim. Never graded and never counted — the graded,
-counted unit is a Finding, which belongs to verdict-bearing reviews.
+persona would need answered next, held attributed and substantially
+verbatim in its Dispatch record and relayed from there as a digest.
+Never graded and never counted — the graded, counted unit is a Finding,
+which belongs to verdict-bearing reviews.
 _Avoid_: consultation finding, recommendation
 
 **Project memory**: