docs(router): flag placeholder vertical docs in CLAUDE.md routing table

[9Olive]

CLAUDE.md's Routing Table lists context/verticals/fraud-detection.md and context/verticals/demand-forecasting.md as the context docs to load for fraud and demand-forecasting tasks, with no indication that both files are explicitly marked > **PLACEHOLDER** at the top - structural scaffolds with TODO markers throughout (unverified PQL patterns, blank time-window guidance, blank evaluation guidance) rather than validated content.

Since the router is the first (and most-loaded) file an agent session reads, and it drives which context doc to load without the agent necessarily opening the target file first, a beginner-facing session can silently treat these scaffolds as authoritative guidance for two entire verticals.

This is a one-line-per-row annotation fix: append "(placeholder scaffold, verify before use)" to both routing table entries so the placeholder status is visible at the point of routing, not just after opening the target file. No other lines changed.

[9Olive]

Verified: consistent with the _sources.yaml placeholder notes for the two vertical docs. Recommend merge. Duplicates #29 on the same two lines (this wording is clearer) - #29 is being closed.

---

Automated internal-consistency review (cross-checked against the repo's own authoritative docs; a few SDK-surface claims spot-checked against installed kumoai 2.22.0).

[Manushpm8]

Leaving open for maintainer triage. The '(placeholder scaffold, verify before use)' annotation is accurate (both files are unvalidated scaffolds), but the routing table was already fine — low-value. Defer to @9Olive.

[leena-kang]

Verified - recommend merge

I independently verified the CLAUDE.md routing-table annotation against the referenced files in kumo-coding-agent. This PR does not introduce a Kumo SDK/API behavior claim, so SDK validation was not applicable; the repo-local evidence supports the change.

Evidence

# context/verticals/fraud-detection.md:3-5
The target doc is marked PLACEHOLDER, calls itself a structural scaffold, and says its guidance is not verified yet.

# context/verticals/demand-forecasting.md:3-5
The target doc is marked PLACEHOLDER, calls itself a structural scaffold, and says its guidance is not verified yet.

# context/_sources.yaml:106-118
Both vertical docs are authored docs with notes marking them as placeholder scaffolds and not yet validated.

Accurate checks

• CLAUDE.md:24 now flags context/verticals/fraud-detection.md as a placeholder scaffold, matching the referenced doc and _sources.yaml.
• CLAUDE.md:25 now flags context/verticals/demand-forecasting.md as a placeholder scaffold, matching the referenced doc and _sources.yaml.
• PR docs: flag unvalidated vertical routing entries in CLAUDE.md #29 appears to duplicate the same underlying fix with shorter wording; PR docs(router): flag placeholder vertical docs in CLAUDE.md routing table #96 is the clearer version.

Local checks

• git diff --check origin/main...HEAD passed in an isolated PR checkout.
• Targeted SDK tests skipped: this PR does not change or claim Kumo SDK/API behavior.
• GitHub checks: none reported on the PR at review time.

Grammar/spelling: no standalone issues found.

[9Olive]

Thanks @leena-kang — verified and I agree this is ready to merge. CLAUDE.md:24-25 now flag both vertical docs as placeholder scaffolds, matching the docs themselves (context/verticals/fraud-detection.md:3-5, demand-forecasting.md:3-5) and _sources.yaml. No SDK/API behavior claim; nothing to change.

⚠️ One thing I can't do myself: this PR is from a fork and my account has no push/merge access to the base repo (reviewDecision: REVIEW_REQUIRED, and enabling auto-merge is denied for me). A maintainer with write access needs to approve + merge. As you noted, this supersedes the shorter-worded #29 duplicate, which can be closed in favor of this one.