feat(sbir): filter topics by DSIP cycle_name - #72
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
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.
What
list_sbir_topics()takes a newcycle_namefilter, which selects topics by their DSIP solicitation cycle (e.g.DOD_SBIR_2026_P1_CBZ).SbirTopicgains acycle_namefield.scripts/refresh_contract.py, and the shape overlay is regenerated; the only field it adds iscycle_name.Why
Tango API 5.3.1 (makegov/tango#3729) added
cycle_nameto SBIR topics now that DoD topics are ingested straight from DSIP.tango-mcp needs this to let topic searches filter by cycle.
Testing
test_list_sbir_topics_cycle_name.ruff check .reports 23 findings, all in files this PR doesn't touch.🤖 Generated with Claude Code