docs: fix version mismatches, config paths, and broken links

[ajianaz]

Summary

Fixes audit findings from website/docs validation after v0.0.10 release.

Changes

Issue	Fix	Files
#199	Bump version references from v0.0.8 → v0.0.10	README.md, docs/cli-reference.md, docs/roadmap.md
#200	Fix config resolution path to match source code	docs/configuration.md
#201	Fix broken pi agent link (was self-referencing)	docs/extensions.md

Details

• Version bump: README badge, CLI Reference header, roadmap current marker
• Roadmap: Added v0.0.9 (VitePress migration) and v0.0.10 (Codebase quality) sections from CHANGELOG
• Config paths: Updated configuration.md resolution order to match actual implementation: defaults → ~/.uteke/uteke.toml → .uteke/uteke.toml
• Extensions: Changed pi agent link from uteke repo to https://pi.dev

Also closed

Closed #178 (Hermes branding removed in v0.0.10), #182 (dual-write fixed), #183 (768d docs corrected) — all already in v0.0.10 CHANGELOG.

Closes #199, Closes #200, Closes #201

Summary by CodeRabbit

Documentation

• Updated version references to v0.0.10 across documentation
• Clarified configuration discovery order and per-project configuration placement
• Extended roadmap with completed milestones for versions v0.0.8 through v0.0.10
• Updated extension reference links

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation-only PR synchronizing version numbers from v0.0.8 to v0.0.10 across README and CLI reference, clarifying configuration resolution paths to "last match wins" with .uteke/uteke.toml directory layout, fixing a broken pi agent extension link, and expanding the roadmap with completed v0.0.8 through v0.0.10 entries.

Changes

Documentation Updates

Layer / File(s)	Summary
Version Synchronization README.md, docs/cli-reference.md	Version badge and CLI reference heading bumped from v0.0.8 to v0.0.10; README roadmap/changelog section updated to mark v0.0.10 as current with expanded feature details.
Configuration Path Clarification docs/configuration.md	Configuration resolution order rewritten to document "last match wins" strategy (built-in defaults → global ~/.uteke/uteke.toml → project-level .uteke/uteke.toml). Per-project config instructions updated from root-level uteke.toml to .uteke/uteke.toml under .uteke/ directory.
Roadmap Expansion and Link Fixes docs/roadmap.md, docs/extensions.md	Roadmap restructured with v0.0.8 (Stability & Architecture) as done, and new sections for v0.0.9 (Website Migration) and v0.0.10 (Codebase Quality) with detailed completion items. Pi extension documentation link corrected from uteke GitHub repository to pi.dev.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Possibly related PRs

• ajianaz/uteke#174: Prior PR updated README roadmap and version sections to v0.0.8; this PR continues the version updates, bumping those same sections to v0.0.10 alongside additional roadmap/changelog expansion.

Poem

🐰 A rabbit hops through documentation,
Updating versions with dedication!
v0.0.10 shines so bright,
Config paths clarified just right,
Links fixed and roadmap expanded—thump thump! 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR addresses issues #199, #200, and #201 comprehensively, but does not address issue #178 (removing Hermes branding), which is listed in the linked issues.	Issue #178 requires removing Hermes branding from file names (python_hermes.py → python_wrapper.py, test_hermes_integration.py → test_python_wrapper.py), docstrings, and documentation references. These changes are not present in this PR.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the PR's main changes: fixing documentation version mismatches, configuration paths, and broken extension links.
Out of Scope Changes check	✅ Passed	All changes in the PR are directly scoped to the four linked issues, with no extraneous modifications beyond fixing versions, config paths, and links.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/docs-version-and-consistency

---

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.}

[github-actions]

🔍 Cora AI Code Review

✅ No issues found. Code looks good!

---

Review powered by cora-cli · BYOK · MIT

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

README.md (1)

337-339: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Configuration precedence order is reversed in README.

Line 337–339 lists project → global → defaults, but the PR objective states resolution should be defaults → ~/.uteke/uteke.toml → .uteke/uteke.toml (last match wins). Please update this list to match implementation and docs/configuration.md to avoid contradictory setup guidance.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 337 - 339, The README's configuration precedence list
is reversed; change the three-line ordered list that currently reads
".uteke/uteke.toml (project-level, in cwd)", "~/.uteke/uteke.toml (global
user-level)", "Built-in defaults" so it matches the implemented and documented
resolution order by reordering to "Built-in defaults", "~/.uteke/uteke.toml
(global user-level)", ".uteke/uteke.toml (project-level, in cwd)" and ensure the
wording matches docs/configuration.md so the README and docs are consistent.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@README.md`:
- Around line 337-339: The README's configuration precedence list is reversed;
change the three-line ordered list that currently reads ".uteke/uteke.toml
(project-level, in cwd)", "~/.uteke/uteke.toml (global user-level)", "Built-in
defaults" so it matches the implemented and documented resolution order by
reordering to "Built-in defaults", "~/.uteke/uteke.toml (global user-level)",
".uteke/uteke.toml (project-level, in cwd)" and ensure the wording matches
docs/configuration.md so the README and docs are consistent.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 54b1aefc-51da-4172-843d-8efc53cf4641

📥 Commits

Reviewing files that changed from the base of the PR and between b3eb47a and 9b5a190.

📒 Files selected for processing (5)

• README.md
• docs/cli-reference.md
• docs/configuration.md
• docs/extensions.md
• docs/roadmap.md