Cycle-1 probe follow-ups: advisory routing, pricing-tool priority, backlog - #171
Merged
Conversation
…itions Three corrections from the 2026-08-20 coverage-probe run: - Advisory-question routing (probe P05): a sizing question produced a high-quality answer with zero tool calls - the cadence table and the commitments guidance never surfaced. The server instructions now tell the agent to fetch the matching reference BEFORE answering sizing, commitment, allocation or chargeback questions. - Pricing-tool priority (probe P14): the model web-fetched a provider pricing page instead of calling the connected Pricing Hub, satisfying the letter of "prefer a live source" while bypassing the hub. The rule now states in all four copies (SKILL.md, POWER.md, the INSTALLATION response contract, the server instructions) that a connected pricing tool outranks web browsing. - Backlog additions (probe P02): Kubernetes coverage gap (item 9) and the obvious-tier product note (non-AWS obvious playbooks = 2); the storage-tiering item is annotated as seeded by probe P11. - Frontmatter audit (probe P04's question): fcp_phases is deliberately independent of fcp_domain - confirmed intentional for kubernetes, oci and for-ai, and now documented in CLAUDE.md so the apparent mismatch does not get "fixed".
OptimNow
enabled auto-merge (squash)
August 20, 2026 09:10
OptimNow
disabled auto-merge
August 20, 2026 09:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-ups from the first coverage-probe cycle (8 probes, run log in the maintainer doctrine):
Guards and tests green. Alpic redeploy needed after merge (instructions string changed).