chore(tools): mark flow_* deprecated with 2026-05-18 sunset (closes #38)#42
Open
stackbilt-admin wants to merge 1 commit intomainfrom
Open
chore(tools): mark flow_* deprecated with 2026-05-18 sunset (closes #38)#42stackbilt-admin wants to merge 1 commit intomainfrom
stackbilt-admin wants to merge 1 commit intomainfrom
Conversation
Adds deprecated/deprecationTarget/sunsetDate annotations to the five flow_* tool specs and prefixes each description with a [DEPRECATED — sunset YYYY-MM-DD, migrate to <target>] marker so MCP clients render the sunset to users. flow_create and flow_status point to their 1:1 scaffold successors; flow_summary/quality/governance point to the generic scaffold_* family since no direct counterpart exists yet. Chosen over option 1 (hard delete) and option 2 (split clone semantics): a 30-day deprecation window gives known downstream consumers a heads-up without wasting effort splitting flow_quality vs. flow_governance payloads on an interface scheduled for removal. The follow-up PR lands after 2026-05-18 and removes the specs + their route-table entries + their registry mapping in one change. Regression guards in tool-registry.test.ts: all five flow_* entries are deprecated with the shared sunset date, the 1:1 successors are correctly named, descriptions carry the deprecation marker, and no non-flow tool is marked deprecated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
deprecated,deprecationTarget, andsunsetDateannotations to the fiveflow_*tool specs insrc/tool-registry.ts.flow_*description with[DEPRECATED — sunset 2026-05-18, migrate to <target>]so MCP clients surface the sunset in tool catalogs.flow_create→scaffold_create(1:1),flow_status→scaffold_status(1:1),flow_summary/flow_quality/flow_governance→ genericscaffold_*(no direct counterpart exists yet).Why this option (closes #38)
Three options were on the table: (1) hard-delete
flow_*now, (2) keep but splitflow_quality/flow_governanceclone semantics, (3) keep as deprecated wrappers with a sunset date. Picked (3). A 30-day window gives known downstream consumers (codebeast, CLI) time to migrate without catalog churn. Splitting the clone semantics is wasted work on an interface scheduled for removal. The follow-up removal PR lands after 2026-05-18 and deletes the specs +route-table.tsentries + registry mapping in one change.Consumers who still need receipt-based governance inspection after sunset should flag it on #38 before the date so the semantics can be ported forward into
scaffold_*.Test plan
npm run typecheck— cleannpm run test— 180 / 180 passing (4 new)flow_*entry carriesdeprecated: true, the sharedsunsetDate, and adeprecationTargetflow_create/flow_statuspoint to their 1:1 scaffold successorsflow_*description contains the deprecation marker and the datetools/listcall from an MCP client renders the deprecation marker in the tool description (visible to Claude Code / Claude.ai)flow_*fromtool-registry.ts,route-table.ts, andTOOL_NAME_MAP.flow🤖 Generated with Claude Code