feat(linkedin-studio): S14 — journey layer (create/measure front-doors + 5-journey router), v4.1.0
14a's cold command-rationalization found ZERO redundancy across the 27 commands (no defensible merge/cut), so the operator reframed S14 from "merge/cut" to "add a journey layer over the kept atomics". - Add /linkedin:create + /linkedin:measure — delegate-only guided front-doors (Read/Glob/AskUserQuestion only; route to the command that owns the work) - Re-tier commands/linkedin.md into 5 journeys (Start/Create/Engage/Measure/Grow); onboarding/strategy elevated as Start/Grow front-doors; Engage = calendar+firsthour tier - 14a honesty nits: router now lists firsthour; calendar cross-links to firsthour; competitive confirmed UNGATED (the claimed 1K-gating inconsistency was unfounded) - Lockstep: EXPECT_COMMANDS 27->29, v4.0.0->4.1.0 across plugin.json / README badges / plugin+root CLAUDE.md / README / CHANGELOG; new README commands-badge lint guard - 14a deliverable corrected: multiplatform entry added (26/27 -> 27/27), header counts, competitive nit withdrawn - Independent /trekreview (2 Opus reviewers) raised 3 MAJORs (stale commands badge, router competitive self-contradiction, STATE.md count) — ALL remediated in-session; verdict ALLOW Gate: test-runner.sh 74/0/0; node --test 98/98; commands=29; v4.1.0 consistent. Additive/minor — no command removed/renamed/behavior-changed; reload registers create+measure. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
431a893f7c
commit
baca30feb1
16 changed files with 885 additions and 208 deletions
|
|
@ -42,7 +42,7 @@ warn() { echo -e "${YELLOW}⚠${NC} $1"; WARN=$((WARN + 1)); }
|
|||
# Source of truth: CLAUDE.md headers + STATE.md Telling. Bump these together
|
||||
# with the files when adding/removing an agent, command, reference, or skill.
|
||||
EXPECT_AGENTS=19
|
||||
EXPECT_COMMANDS=27
|
||||
EXPECT_COMMANDS=29
|
||||
EXPECT_REFS=25
|
||||
EXPECT_SKILLS=6
|
||||
|
||||
|
|
@ -101,6 +101,17 @@ else
|
|||
fail "CLAUDE.md commands header ($DOC_COMMANDS) != contract ($EXPECT_COMMANDS)"
|
||||
fi
|
||||
|
||||
# README shields commands-count badge must match the contract too. Added after an
|
||||
# S14 /trekreview found the badge stale at commands-27 while the surface shipped 29:
|
||||
# the version-consistency grep (Section 9) checks only the version badge, and the
|
||||
# count guards above check the CLAUDE.md header, so the README count badge slipped
|
||||
# both. This closes that gap (the count-badge analogue of the version-badge check).
|
||||
if grep -q "badge/commands-${EXPECT_COMMANDS}-" README.md; then
|
||||
pass "README commands badge declares ${EXPECT_COMMANDS}"
|
||||
else
|
||||
fail "README commands badge != ${EXPECT_COMMANDS} (expected shields badge/commands-${EXPECT_COMMANDS}-)"
|
||||
fi
|
||||
|
||||
echo ""
|
||||
|
||||
# --- Section 3: Agent Frontmatter ---
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue