Six places still told users to `pip install 'markitdown[all]'`: the
"markitdown library not available" error hints in arxiv_tool, core_tool and
semantic_scholar_tool, plus the fulltext access guide and the markitdown
example.
That is the extra the previous commit removed, and for the same reasons: it
pins youtube-transcript-api~=1.0.0 (`Requires-Python <3.14`), and since
markitdown 0.1.6 it also requires a prerelease-only Azure dependency, so a
default resolver silently backtracks to markitdown 0.1.5. A user following
the hint on Python 3.14 lands on a MarkItDown whose YouTube converter is
registered but cannot fetch transcripts.
All six now name the same converter extras the project declares. No test
asserts on these strings.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A2xx4ELgtuMxiDema4LaEh
Both branches solved the same problem (a lost CI runner discarding the
whole weekly tool sweep) independently: main shipped sharded matrix jobs
with per-shard log parsing (scripts/summarize_health_sweep.py, already in
production), while this branch restores an unsharded checkpoint/resume
system (--json-output/--resume, atomic JSON checkpointing).
Resolution:
- .github/workflows/weekly-tool-healthcheck.yml and the run_all_patterns()
call site: took main's sharded design, since it's already shipped and
replacing it would reintroduce the exact failure mode it was built to
fix. The checkpoint/resume machinery itself stays -- it's still useful
standalone for a developer resuming an interrupted local sweep.
- Fixed a real interaction bug this merge would otherwise have introduced:
checkpoint_complete compared `results` against the full `expected_patterns`
universe, which is never true for a single shard's `selected` subset, so
every successful sharded CI run would have incorrectly exited 1. Now
compared against `selected` -- identical to `expected_patterns` when
--shard isn't used, correctly scoped when it is. Verified with a manual
shard simulation.
- Removed test_weekly_workflow_consumes_the_checkpoint_contract: it
asserted the workflow YAML wires up --json-output and executes an inline
job-summary heredoc, both part of the design main's sharding replaced.
Its premise no longer holds under the shipped design.
zhihaovme50