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

[vircung]

working-process 0.17.0

• A plan's review loop closes only on a full-document round: a
  diff-scoped LGTM certifies a chain, so one confirming round follows it
  and carries the stamp. The rules define which heading counts as the
  latest, widen the plan exception to the relay-then-stamp order, and
  bound what the round cap promises.
• The propagation duties ship as an author-facing rule, so an author
  meets them while writing rather than through the auditor's hits. Two
  hits on one document are reported as a shape, and the co-firing line
  states a shape rather than a judgment.
• The verdict relay opens with a header line — verdict, model
  self-report, findings by severity, decisions awaiting the developer —
  and every dispatch writes a record to .claude/working-process/
  before the relay. A consultation meets the same floor in its record,
  and its relay digests one paragraph per focusing question.
• The plan adversary emits each finding's origin, triage holds a
  spec-origin finding unless a written decision licenses the edit, and a
  licensed cross-document fix lands in the spec's own ledger.
• Feature work follows the published branch-naming convention,
  feature/<ticket>-<short-name>.
• The plugin ships this changelog.

salesforce-standards 0.4.0

• The new salesforce-triggers skill carries the rules that hold
  whatever framework a project uses, and the trigger content leaves
  salesforce-apex.
• A resolution protocol identifies the project's trigger framework
  before Apex is graded, and three documents describe what each one
  expects — frameworkless, base-class, and metadata-driven — with a
  comparison for choosing among them.
• The toolchain rule routes triggers and documents the declaration keys,
  naming .claude/CLAUDE.md among the homes a declaration may take.
• The plugin ships this changelog.

project-memory 0.5.1

• The plugin ships this changelog.

python-standards 0.3.2

• The plugin ships this changelog.

Repo conventions

• The plugin-versioning rule states where a plugin's changelog lives, when
  its entry is written, and what version a -dev prerelease hangs off.
• release-guard gains two steps: a bumped plugin's changelog must name
  the new version at its top, and no ## Unreleased section may reach
  master.