Skip to content

Document PR #105 in public docs, landing, guide, and changelogs#106

Merged
mkreyman merged 1 commit into
masterfrom
docs/pr105-followup
Apr 17, 2026
Merged

Document PR #105 in public docs, landing, guide, and changelogs#106
mkreyman merged 1 commit into
masterfrom
docs/pr105-followup

Conversation

@mkreyman
Copy link
Copy Markdown
Owner

Summary

PR #105 shipped new MCP tools and endpoints but the public docs still pointed at the old tool count and made no mention of the new functionality. This follow-up fixes the drift.

  • loopctl.com/docs — tool count 41/42 → 50; new "Work Breakdown Tools" subsection for import_stories, create_story, backfill_story
  • Landing page — tool count fixed, step-3 onboarding mentions ?merge=true
  • docs/orchestration-guide.md — Pattern 1 mentions merge=true + create_story; new Pattern 3 for per-story backfill with provenance
  • docs/articles/chain-of-custody.md — new section explaining why backfill is structurally safe (dispatch-lineage refusal prevents force_unclaim → backfill laundering)
  • CHANGELOG.md + mcp-server/CHANGELOG.md — full entries for v2.1.0 MCP and the unreleased server changes
  • mcp-server/smoke_test.mjs — the stdio harness we used to verify the new tools before publishing; useful as a regression check going forward

2286 tests, Credo, Dialyzer all still clean.

Test plan

  • CI green
  • Visual check at loopctl.com/docs and /#get-started after deploy
  • Run node mcp-server/smoke_test.mjs locally (needs LOOPCTL_ORCH_KEY)

🤖 Generated with Claude Code

PR #105 shipped new functionality but the public-facing docs still
pointed at the old tool count and made no mention of the new tools.
This follow-up fixes that so agents and humans hitting loopctl.com
see accurate guidance.

## loopctl.com/docs (page_html/docs.html.heex)

- "41 typed tools" -> "50 typed tools" (section intro)
- "42 tools" -> "50 tools" (Other Notable Tools summary)
- New "Work Breakdown Tools" subsection documenting import_stories
  (with merge + payload_path), create_story (with epic_number
  convenience), and backfill_story (with the dispatch-lineage refusal
  warning). Matches the pattern of the existing Knowledge Wiki Tools
  enumeration.

## Landing page (home.html.heex)

- "42 typed tools" -> "50 typed tools" (two occurrences)
- Getting-started step 3 now mentions ?merge=true for appending to an
  existing epic.

## Orchestration guide (docs/orchestration-guide.md)

- Pattern 1 section now mentions merge=true for incremental adds, plus
  an inline create_story example.
- New Pattern 3 "Per-story backfill with provenance" documenting the
  backfill_story tool, its structural guard (no dispatch lineage), its
  idempotent-retry semantics, and the audit/webhook it emits. Old
  Pattern 3 "Epic-wide verification" becomes Pattern 4.

## Chain-of-custody wiki article (docs/articles/chain-of-custody.md)

- New "Pre-loopctl work: the backfill exception" section explaining
  why backfill is safe (structural dispatch-lineage refusal prevents
  force_unclaim + backfill from laundering dispatched work) and when
  to use it (honest onboarding of pre-existing work with provenance).

## Changelogs

- mcp-server/CHANGELOG.md: new 2.1.0 entry for the MCP package
  (merge, payload_path, create_story, backfill_story, type tolerance,
  path-safety validation, domain error translation).
- CHANGELOG.md: new [Unreleased] entry covering the server-side
  changes (new endpoints, role policy, security scoping of the
  unique-constraint translation).

2286 tests still pass. Credo + Dialyzer clean.
@mkreyman mkreyman merged commit 8624af4 into master Apr 17, 2026
6 checks passed
@mkreyman mkreyman deleted the docs/pr105-followup branch April 17, 2026 04:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant