docs: update slides after v0.1.42

[sonichi]

PR Title Format

Your PR title must follow the format: <type>: <brief description>

Valid types:

• fix: - Bug fixes
• feat: - New features
• breaking: - Breaking changes
• docs: - Documentation updates
• refactor: - Code refactoring
• test: - Test additions/modifications
• chore: - Maintenance tasks
• perf: - Performance improvements
• style: - Code style changes
• ci: - CI/CD configuration changes

Examples:

• fix: resolve memory leak in data processing
• feat: add export to CSV functionality
• breaking: change API response format
• docs: update installation guide

Description

Brief description of the changes in this PR

Type of change

• Bug fix (fix:) - Non-breaking change which fixes an issue
• New feature (feat:) - Non-breaking change which adds functionality
• Breaking change (breaking:) - Fix or feature that would cause existing functionality to not work as expected
• Documentation (docs:) - Documentation updates
• Code refactoring (refactor:) - Code changes that neither fix a bug nor add a feature
• Tests (test:) - Adding missing tests or correcting existing tests
• Chore (chore:) - Maintenance tasks, dependency updates, etc.
• Performance improvement (perf:) - Code changes that improve performance
• Code style (style:) - Changes that do not affect the meaning of the code (formatting, missing semi-colons, etc.)
• CI/CD (ci:) - Changes to CI/CD configuration files and scripts

Checklist

• I have run pre-commit on my changed files and all checks pass
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Pre-commit status

# Paste the output of running pre-commit on your changed files:
# uv run pre-commit install
# git diff --name-only HEAD~1 | xargs uv run pre-commit run --files # for last commit
# git diff --name-only origin/<base branch>...HEAD | xargs uv run pre-commit run --files # for all commits in PR
# git add <your file> # if any fixes were applied
# git commit -m "chore: apply pre-commit fixes"
# git push origin <branch-name>

How to Test

Add test method for this PR.

Test CLI Command

Write down the test bash command. If there is pre-requests, please emphasize.

Expected Results

Description/screenshots of expected results.

Additional context

Add any other context about the PR here.

Summary by CodeRabbit

• Documentation
  • Updated presentation slide to reflect latest release range (now through v0.1.42) and bumped releases count to 74+.
  • Added "Planning Mode" to the UI/UX Interfaces list in the Getting Started slide.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated two presentation slides: in slide-evolution-from-v001.html the version range advanced to v0.0.3 → v0.1.42 and Releases count to 74+; in slide-getting-started.html added "Planning Mode" to the UI/UX Interfaces list.

Changes

Cohort / File(s)	Change Summary
Rapid Evolution slide docs/presentation/components/slide-evolution-from-v001.html	Updated version range text to v0.0.3 → v0.1.42 and bumped Releases count to 74+.
Getting Started slide docs/presentation/components/slide-getting-started.html	Added "Planning Mode" to the UI/UX Interfaces bullet list.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• docs: update slides post v0.1.32 #719: Similar edits to the same presentation slide files (version/release text and UI items).
• docs: update slides after v0.1.36 #779: Prior incremental content updates to these slide HTML files.
• docs: update slides after v0.1.35 #772: Related modifications to the same slide files adjusting version/release labels and UI list entries.

Suggested reviewers

• stellaxiang
• a5507203
• shubham2345
• voidcenter
• praneeth999
• franklinnwren
• john-the-dev
• Eric-Shang
• ncrispino
• kitrakrev

🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description contains only the template boilerplate without any actual content filled in. Critical sections like description, type of change selection, checklist completion, test commands, expected results, and additional context are all empty or unchecked.	Fill in the 'Description' section with details about the slide updates, check the appropriate 'Type of change' box, complete the pre-commit status, and provide testing instructions or rationale for why testing is not applicable.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title 'docs: update slides after v0.1.42' follows the required format and accurately describes the main changes: documentation slide updates reflecting the v0.1.42 release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Documentation Updated	✅ Passed	This PR is a post-release documentation update that only modifies presentation slide HTML files with version information updates and a reference to an existing feature (Planning Mode). The custom check requires documentation for user-facing features, YAML parameters, new models, and breaking changes in specific locations. Since this PR is updating presentation slides after v0.1.42 was released, any new features like Planning Mode would have already received appropriate documentation when the v0.1.42 release was made. This PR simply updates presentation materials to reflect previously-released and documented features.
Capabilities Registry Check	✅ Passed	The custom check for Capabilities Registry Check is not applicable to this PR. The PR contains only documentation updates to HTML slide files with no backend code, model changes, or modifications to capabilities definitions.
Config Parameter Sync	✅ Passed	The PR only modifies HTML presentation files with no new YAML parameters added, so the YAML parameter synchronization check does not apply.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}