AgentConfigScore v0.23.0

AgentConfigScore v0.23.0

This release packages the English core workflow: a dependency-free, local
instruction linter and baseline-aware CI regression gate. It remains Beta.
No accuracy comparison with AI review or independent user validation is claimed.

Install or upgrade

python -m pip install --upgrade "agent-config-score==0.23.0"
agent-config-score --version

Expected version: AgentConfigScore 0.23.0. Python 3.10+ is required; Git is
needed for diff. Both console aliases (agent-config-score, acs) and the
PATH-independent python -m agent_config_score entrypoint are available.

What is included

• Shared Markdown context for more conservative handling of explicit prohibited
  command blocks/lists, matching code fences and command-option parsing.
• Local Markdown-link checks relative to the instruction file.
• Narrow English rules for explicitly false success reports and bulk environment
  transfers. These are evidence-based lint signals, not general intent detection.
• Baseline-owned regression policy and expiring suppressions, local diff and
  compare, initialization, integration doctor, rule inspection and reports.
• An optional copy-ready PR-comment workflow; posting is opt-in, not an automatic
  action of the scanner.
• Windows Unicode Git-path fixes and concise diagnostics for invalid UTF-8
  integration files or unwritable reports.
• A user guide
  covering setup, exit codes and troubleshooting, plus a
  documentation index.
• Installed-wheel acceptance on Linux, Windows and macOS, required before
  publication alongside the full source regression suite.

Compatibility and adoption

Existing command names, configuration version 1 and JSON field names remain
unchanged. Rule additions and interpretation fixes can change scores and findings
on the same input compared with v0.22.0. Review new signals when upgrading; a
score change is not a new real-world accuracy measurement.

The new stable rule IDs are false-success-report and broad-environment-upload.
They are included in rule inspection, suppression schema and SARIF metadata.
Operational filesystem/encoding failures return exit 2; doctor error checks
return 1. These failures are not clean scan results.

For reproducible CI, pin the Action to LE0-Lin/AgentConfigScore@v0.23.0 (or its
verified commit). @v0 remains a rolling pre-1.0 reference and can change on a
later release. The tool applies the baseline policy to both trees so a PR cannot
use its own weaker policy or new suppression to approve itself.

Existing generated workflows do not need to be reinitialized merely to upgrade
the installed package. Review whether they use a fixed Action version or rolling
v0, since those determine the CI tool separately from your local installation.

Evidence and known limits

Maintained deterministic contracts and synthetic installed-package journeys
verify expected engineering behavior; they do not establish real-world precision,
recall or usefulness. The unresolved AI pilot and failed source acquisitions
remain explicitly unscored; research preparation is separate from the runtime.

An A 100 means no active deterministic rule matched, not semantic perfection
or a security approval. Arbitrary paraphrases, contradictions and other-language
instruction semantics still need review. Read the
limitations
and full changelog.

Simplified and Traditional Chinese documentation/language links are the next
optional milestone; they are not included in v0.23.0. Translating documentation
will not by itself add Chinese semantic detection or change machine-readable
interfaces.