fix(linkedin-studio): S11 — model-name declaration drift + model-consistency lint guard
Cold full-brief re-review (S10) reached a class the S7->S9 algorithm-stat lens never did: BLOCKER — post-feedback-monitor published as Haiku in four surfaces (README:259, skills/linkedin-studio:159 with wrong color Green too, skills/linkedin-analytics:41, agents-capability-matrix:20) while agents/post-feedback-monitor.md runs Opus. v4.0.0's Opus promotion never reached the user-facing tables. Synced all to Opus/Lime. Refreshed agents-capability-matrix.md (frozen at the v2.0 14-agent era): header 14->19, +5 missing longform agents, tier counts Opus 2->8 / Haiku 1->0, longform-gate diagram updated to the real 8-Opus-agent chain. MAJOR — de-branded docs/plan-fullspektrum-innholdsmotor.md:70 (model brand + jan-2026 asserted as fact -> no-name/no-month relevance-model phrasing). It was the only tracked survivor; the rest live in gitignored ROADMAP.md / .claude/research/ (not shipped, out of honesty scope). META — added Section 10 model-consistency guard (scripts/check-model-consistency.mjs): each agents/*.md model: must match every surface declaration AND the canonical rosters must list all 19 agents. Permanent non-vacuity self-test + e2e mutation-proven. Pre-patch sweep confirmed post-feedback-monitor was the sole drifted agent (89 model rows, 0 other mismatches). test-runner.sh 68/0/0, node --test 94/94. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
853cad3ade
commit
433c2efb3d
8 changed files with 223 additions and 17 deletions
|
|
@ -10,7 +10,9 @@
|
|||
#
|
||||
# The stat-consistency grep (one magnitude per algorithm effect across the
|
||||
# tree) was added in remediation Step 3; the version-consistency grep in
|
||||
# Step 21. Both are live below (Sections 8 and 9).
|
||||
# Step 21; the agent model-consistency guard (each agents/<name>.md frontmatter
|
||||
# model: must match every surface declaration, and canonical rosters must list
|
||||
# every agent) in S11. All three are live below (Sections 8, 9 and 10).
|
||||
#
|
||||
# Usage: bash scripts/test-runner.sh
|
||||
# bash 3.2-safe: plain arrays only, no `declare -A`, no `mapfile`/`readarray`.
|
||||
|
|
@ -319,6 +321,26 @@ fi
|
|||
|
||||
echo ""
|
||||
|
||||
# --- Section 10: Agent Model-Consistency ---
|
||||
echo "--- Agent Model-Consistency ---"
|
||||
|
||||
# Each agents/<name>.md frontmatter `model:` is the source of truth; every
|
||||
# surface that DECLARES an agent's model (README, CLAUDE.md, the capability
|
||||
# matrix, the SKILL rosters) must match it, and the canonical rosters must list
|
||||
# every agent. Added in S11 after a cold full-brief review found
|
||||
# post-feedback-monitor published as Haiku across four surfaces while the agent
|
||||
# runs Opus — declaration drift the version/count/stat guards could not see. The
|
||||
# checker self-tests its own non-vacuity on every run (see the .mjs header):
|
||||
# a deliberately-mismatched probe must be caught and a correct one ignored, else
|
||||
# the suite fails instead of certifying an unenforced criterion.
|
||||
if node scripts/check-model-consistency.mjs; then
|
||||
pass "agent model-consistency: all surface declarations match frontmatter + canonical rosters complete"
|
||||
else
|
||||
fail "agent model-consistency drift — see check-model-consistency.mjs output above"
|
||||
fi
|
||||
|
||||
echo ""
|
||||
|
||||
# --- Summary ---
|
||||
echo "================================================"
|
||||
echo "RESULTS"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue