v8.5.0

Charness 8.5.0

Changes

• Finish related issues with a current shared review and per-issue bug/feature
  classification, without commissioning another review just to reformat evidence.
• Release preparation defers the semantic subject suite to the final,
  claims-bound resume. Current publication checks remain required; this is
  scheduling, not a cross-commit test cache.
• Spec, debug and retro guidance can reuse applicable known context. Missing or
  changed context, uncertain causes and recurrence keep their diagnostic routes.

Observed limits

The delegation pilot did not establish an efficiency gain. The valid higher-tier
candidate completed correctly but cost more; the lower-tier comparison had
preservation failures and an unfrozen installed-helper dependency. Original
results and limitations remain in the
comparison record.

Update

Run charness update, then charness version and charness doctor to inspect
your installation. No configuration migration is required.

Derived claim surfaces

id: json-declaring-scripts
question: which repo-owned Python sources declare their own `--json` option
count: 0
items: []
scanned:
- scripts/**/*.py
- skills/**/scripts/**/*.py
- charness
unscanned:
- the exported `plugins/charness/**` mirror and `mutants/**`, which are generated
  copies of these same sources
- flag names composed at runtime from a variable rather than written as a string literal
- flags a wrapper forwards without declaring, which no parser in this tree names

id: charness-subcommands
question: which top-level subcommands the `charness` CLI declares
count: 12
items:
- capability
- catalog
- doctor
- goal
- init
- reset
- task
- tool
- uninstall
- update
- version
- worktree
scanned:
- charness
unscanned:
- nested subcommand groups such as `charness task run`, which are declared on their
  own subparser
- subcommands a host adapter adds outside this entrypoint

id: public-skills
question: which public skills this repo ships
count: 19
items:
- achieve
- announcement
- create-cli
- create-skill
- critique
- debug
- gather
- hitl
- hotl
- ideation
- impl
- issue
- narrative
- prove
- quality
- release
- retro
- setup
- spec
scanned:
- skills/public/*/SKILL.md
unscanned:
- support, profile, and integration skills, which are not part of the public surface
- skills a consuming repo installs from elsewhere

id: repo-shell-gates
question: which `check-*.sh` shell gates this repo ships
count: 8
items:
- check-docs.sh
- check-links-external.sh
- check-links-internal.sh
- check-markdown.sh
- check-python-lint.sh
- check-rust.sh
- check-secrets.sh
- check-shell.sh
scanned:
- scripts/**/check-*.sh
unscanned:
- Python gates under `scripts/`, which are far more numerous and are not this surface
- gates a consuming repo wires from its own tree