docs(registry): refresh deep-research description for v0.2.0#36
Merged
Conversation
The toolspace federated index carries a denormalized description that
predated the v0.2.0 ship — it still framed the Python reference impl
as future work ("lands in v0.2.0"). v0.2.0 merged at 2026-06-02T10:37Z
(drknowhow/deep-research PR #2), Release cut at
https://github.com/drknowhow/deep-research/releases/tag/v0.2.0.
Updated description to past tense: v0.1.0 shipped X, v0.2.0 adds Y
(stdlib-urllib scholar adapter + python-docx synthesis builder with
pluggable upload). Upstream manifest tool.version was already 0.2.0;
this just syncs the registry copy.
federation-sync runs daily but doesn't pull free-text description from
upstream — that's a separate gap worth filing.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the registry index entry for deep-research to reflect that the v0.2.0 Python reference implementation has already shipped, keeping the Toolspace registry description in sync with the upstream release status.
Changes:
- Rewrites the
deep-researchentry description from future-tense (“lands in v0.2.0”) to past/present-tense with a concrete summary of v0.2.0 additions. - Expands the description to enumerate the scholar adapter sources and the optional visualization/docx builder packaging detail (
[viz]extra).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
CI check 'registry pages match a fresh build' caught the manifests.json edit without the matching per-tool page regen. Hand-applied the description from manifests.json into the rendered HTML, keeping the existing pinned timestamps (Pages generated, Last fetched) so the diff is description-only. `python scripts/build_registry_pages.py --check` now passes locally. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
5 tasks
drknowhow
added a commit
that referenced
this pull request
Jun 2, 2026
Example entries (status='example') that track a real external manifest were preserved verbatim across syncs, so when upstream bumped tool.version + description, the registry drifted. Surfaced 2026-06-02 after drknowhow/deep-research v0.2.0 ship — registry still framed the Python reference impl as "lands in v0.2.0" (future tense) for ~hour after upstream had it. Per-entry opt-in: an example carries `auto_refresh_from_upstream: true` to have its `description` (and `capabilities`) refreshed from `tool.description` / `tool.tags` at `manifest_url` on every sync. The refresh fails soft — flaky upstream surfaces as a warning, entry preserved unchanged. Self-hosted spec-mirrored examples (gmail-*, muninn-flowing, vi-federation) leave the flag off and stay verbatim; hand-curated wording survives. Flagged: deep-research + yep-memory. Both descriptions in manifests.json re-synced to current upstream wording so the next nightly run is a no-op diff. Tests: 3 new — refresh replaces, no-flag preserves, fetch-failure fails soft with warning. All 31 federation pipeline tests pass. Follow-on to #36 (manual touch-up). Co-authored-by: Claude Opus 4.6 <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
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
deep-researchframed the Python reference impl as future work ("lands in v0.2.0"). v0.2.0 merged earlier today.Provenance
tool.version: 0.2.0Gap noted (not fixed here)
federation-syncran today (workflow_dispatch + scheduled) but didn't pull the description change from upstream. Appears to sync structural fields only, not free-textdescription. Worth a follow-up PR to teach it to overwrite the denormalized description.Test plan
🤖 Generated with Claude Code