Skip to content

v16.4.0 "Sharper Reasoning and Safer Service Draining"

Latest

Choose a tag to compare

@sickn33 sickn33 released this 30 Aug 10:12
d91ed42

[16.4.0] - 2026-08-30 - "Sharper Reasoning and Safer Service Draining"

Refined falsification routing and graceful-shutdown guidance, retired a
discontinued UIZZE skill, and hardened canonical reference validation. The
published catalog contains 2,097 skills.

This release helps Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and
related AI coding assistants choose the right reasoning depth, drain production
services without fighting their process manager, and avoid stale catalog
references after a canonical skill is removed.

Start here:

Changed

  • Updated falsify with a mandatory mode-selection gate so
    incidents, simple requests, rough estimates, questions, and deep analysis do
    not all enter the same heavyweight reasoning protocol
    (#1287).
  • Refined graceful-shutdown so liveness probes
    remain available during draining, aborted HTTP requests release their active
    counters, and FastAPI shutdown guidance preserves Uvicorn's signal ownership
    (#1289).

Removed

  • Removed the retired ui-slop-score skill after the canonical UIZZE project
    stopped publishing it; the maintained anti-ui-slop, ui-design, and
    ui-radar skills remain available
    (#1288).

Fixed

  • Reordered protected-main validation so canonical repository state is
    regenerated before cross-reference validation. Source-only skill deletions
    can now remove stale bundle and web references before the reference gate runs
    (#1291).
  • Regenerated the canonical catalog, offline AAS Core data, tracked web assets,
    marketplaces, editorial bundles, compatibility reports, and Codex/Claude
    plugin distributions for 2,097 skills
    (#1292).

Security and Reliability

  • Kept the updated skills documentation-only: they do not bundle or execute a
    server runtime, install dependencies, or take ownership of production
    signals.
  • Preserved explicit shutdown deadlines and forced-exit fallbacks so draining
    cannot wait forever, while keeping readiness and liveness semantics separate.
  • Bound canonical-reference checks to freshly regenerated trusted state and
    locked the workflow ordering with regression tests.

Who should care

  • Engineers using agent reasoning protocols who need fast incident handling and
    direct, useful rough estimates without unnecessary ceremony.
  • Platform teams operating Node.js, FastAPI, Kubernetes, workers, and long-lived
    connections that need predictable termination behavior.
  • Maintainers removing retired skills from a source-only catalog without
    leaving stale generated references behind.

Validation

  • Passed repository and reference validation, documentation-security checks,
    warning-budget enforcement, the complete 113-group repository test suite,
    176 web-app tests, the production web build, npm audits, plugin compatibility,
    bundle and marketplace checks, and protected canonical synchronization.
  • Verified final source and canonical CI plus CodeQL on the exact protected
    main commit, with zero open pull requests, issues, security alerts, or
    generated-state drift before release preparation.

Limitations

  • falsify structures routing and evidence checks but cannot guarantee truth or
    replace domain expertise and higher-quality evidence.
  • Graceful shutdown remains runtime- and infrastructure-dependent; align probe,
    load-balancer, process-manager, and orchestrator deadlines in the deployed
    environment.
  • Removing ui-slop-score does not remove the maintained UIZZE design-analysis
    skills or affect projects that independently pinned the retired upstream
    package.

Credits