Repository navigation
Release 1.0: cross-recipe audit, documentation pass, and tag #73
Description
Goal
Check the finished cookbook as one piece of work before calling it 1.0.
Scope
- Run every notebook offline from a fresh clone on Linux and Windows.
- Audit every recipe against the contract in
CONTRIBUTING.md. File an issue for each gap and fix it. - Check consistency across recipes: section order, terminology, chart style, run-mode header.
- Search all notebooks and READMEs for any claim about Jev's quality, latency, or cost. Each one either has recorded live evidence or is removed.
- Link check across the repository.
- Confirm the README shows 60 of 60 published and every row links to a notebook.
- Write release notes that state what was exercised live and what was not, then tag
v1.0.0.
Acceptance criteria
- All sixty recipe issues and all foundation issues are closed
- CI is green on
main - Release notes include the live-evidence statement
- A person has approved the tag. Agents prepare the release and stop before publishing it
Dependencies
- Blocked by Epic: Foundation #74
- Blocked by Epic: Level 1 · Beginner recipes #75
- Blocked by Epic: Level 2 · Easy recipes #76
- Blocked by Epic: Level 3 · Intermediate recipes #77
- Blocked by Epic: Level 4 · Advanced recipes #78
- Blocked by Epic: Level 5 · Expert recipes #79
- Tracked in Cookbook roadmap: 60 recipes from foundation to release #80
References
- Recipe contract
- Catalog
- TypeSafe documentation index for tools: https://docs.typesafe.ai/llms.txt
- Python SDK: https://docs.typesafe.ai/sdk/python
Activity
CompleteDotTech commentedon Oct 20, 2026
Scope amendment (2026-10-20). Per the owner decisions for this run, the release audit covers 100 recipes (ranks 1–100, including the multimodal track 61–100), not 60. Wherever this issue says 60, read 100. One release,
v1.0.0, after all 100; the orchestrator stops before the tag and the owner tags. The original text is left as written.