v0.24.3

This release changes only the distributed skills. The analyzer, shrink and the subcommands behave as in v0.24.2.

Skills

Both skills told an agent to ask the owner and wait at several decisions. An agent that nobody answers, such as one in CI, then stopped with nothing done. Each of those places now says what to do when nobody can answer (#365).

Where	When nobody can answer
authoring: a change that cannot pass the check without an answer, such as a namespace on an existing file	Carry out the option you would recommend, and say in the report what you chose and why. Never a bent name, an ignore, or a config change other than a vocabulary entry
authoring: a declaration that states its own //declscope:private	The same rule. The recommended option never flips a directive the declaration states
authoring: a vocabulary entry	Add it, and say so in the report
authoring: other config changes	Do not make them. Never change a rule's mode, the filter or the baseline path on your own
adoption: config and code before any answer	Do not wait. Adopt the minimum, with no config file, and report which settings the owner may still want
adoption: shrink -fix	Apply it when the request allows changing exported names. shrink judges only under internal/, so no importer outside the module breaks. Otherwise, baseline the reports

When someone can answer, the skills still ask and wait, as before.

The change comes from declscope-in-practice experiment 2. An agent adding a feature to parser.go asked whether to set //declscope:namespace parse, and stopped before writing any code.

Install

mise use "github:mpyw/declscope@0.24.3"

Full changelog: v0.24.2...v0.24.3

Changelog

• c44bcac docs(skills): give every ask-and-wait a way forward when nobody can answer (#365)