Release: working-process 0.18.0, project-memory 0.6.0, python-standards 0.4.0, salesforce-standards 0.5.0

[vircung]

working-process 0.18.0

• New technical-design rule: a third document class between the design
  spec and the plan, saying what a thing is made of. The consumption gate
  offers it where the repository has code, and a design spec and its
  technical design are audited as one target under one integrity: stamp.
• origin on a plan-adversary finding is a list of named documents, and
  the class a design spec and a technical design share is named
  judged document.
• Decision register: a design spec may carry decisions: registered and a
  ## Decisions section; a plan descending from it marks every task with
  **Realizes:** and records deferrals and predecessors.
• The propagation auditor gains decision coverage, derived by
  scripts/decision-coverage.py, and table closure; a coverage hit that
  needs a missing decision is held for the developer as a hit held line.
• Standing process answers get one home: .working-process/settings.md
  (team, committed) and settings.local.md (personal, ignored), one
  key: value grammar, and a key registry, SETTINGS_REGISTRY.md.
• A second SessionStart handler, scripts/load-settings.sh, emits every
  key's effective value and source as one block capped at 4 KB; the same
  loader offers --print, --validate and --set (with --dry-run) and
  owns every write.
• New always-on rule process-settings.md and new process-setup skill,
  which shows the effective settings, asks about the unset keys and
  records every answer through the loader.
• The rules read named keys instead of "the developer's own
  instructions" — persona consent, review autonomy and per-round commits,
  the technical-design offer, the .docs branch merge, the propagation
  gate's tier, and the Process directory modes — and a standing question
  asked in ordinary work offers ", and record".
• Run a rules re-sync after this update: it installs the new rule and the
  changed ones the updated agents expect.

project-memory 0.6.0

• When the working-process rules are installed, the core rule reads
  dir.docs/memory as Team memory's declared mode, asks which stands when
  a visible signal contradicts it, and offers "and record" with its
  first-create question.

python-standards 0.4.0

• /python-review reads dir.docs/code-review from a settings block
  before asking the first-create question, and asks which stands when a
  visible signal contradicts it.

salesforce-standards 0.5.0

• /salesforce-review reads dir.docs/code-review the same way.

Repo conventions

• develop owns the -dev.<n> prerelease counter.
• The repository declares that it does not get the technical-design offer
  by default.
• Tests for the decision-coverage script and the settings loader live
  under tests/working-process/.