chore(release): finalize v0.7.0

[fvadicamo]

What

• Bump version 0.6.0 -> 0.7.0 across the 8 workspace components; refresh uv.lock
• Promote the [Unreleased] CHANGELOG entries to [0.7.0] - 2026-07-18 with a fresh empty [Unreleased] block on top

Why

Prepares the develop -> main release PR for v0.7.0. This is a minor release: it adds new public endpoints and removes two config variables, so it is not just hardening. Headline contents of the release:

• New endpoints: GET /api/v1/documents/{id}/chunks; DELETE /api/v1/index-versions/{version} reclaims superseded index versions and refuses to delete the live one (DEBT-032, ERR-INDEX-001 / 409)
• Removed config: VEKTRA_PARENT_CHILD_LEVELS (DEBT-027), VEKTRA_RERANK_TOP_K (DEBT-013); new VEKTRA_RERANK_FETCH_K
• Error contract: REQ-010 envelope now sits at the JSON document root on every error path (DEBT-033/034)
• Fixes / hardening: top_k bounded 1..100 on /query + /learn/query (BUG-026); namespace binding on DELETE /documents/{id} and the chunk endpoints; every Qdrant chunk path routed through the VectorStoreProvider Protocol (BUG-023); startup traceback fixed (BUG-025); sparse provider registration (BUG-024); empty VEKTRA_LLM_PROVIDER rejected at startup; DEBT-028/029/030/031; Qdrant healthcheck; CMD_TARGET=migrate
• CI / infra: publish ghcr.io/vektralabs/vektra:{version} + :{version}-ocr on tag push (INFRA-007); guard that fails when a test suite is executed by nothing (DEBT-031)

Excluded from this release: PR #99 (TECH-005 textbook eval, ground truth pending review) — orthogonal eval material, not a backend blocker.

Checklist

• Version bumped consistently across the 8 components
• CHANGELOG promoted with release header + fresh empty [Unreleased]
• uv.lock refreshed (only the 8 workspace version pins changed)
• make lint clean (ruff + ruff format + mypy 77 files + import-linter 8/8 contracts)
• make test passing (800 passed, 3 skipped, 52 integration deselected)
• Commit SSH-signed (branch protection), Signed-off-by + Co-Authored-By trailers

Follow-up (after merge to develop)

• Open the develop -> main release PR
• After that merge, create the signed tag v0.7.0 on main — this triggers publish.yml (GHCR image publish)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Release
  • Released version 0.7.0 across the platform’s packages.
  • Added the 0.7.0 release entry dated July 18, 2026.

[coderabbitai]

Warning

Review limit reached

@fvadicamo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 30 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: cd4a5771-67a3-4e5a-bdd2-edfebfe3395c

📥 Commits

Reviewing files that changed from the base of the PR and between ab9c3ef and 870c669.

📒 Files selected for processing (3)

• vektra-analytics/src/vektra_analytics/__init__.py
• vektra-app/src/vektra_app/__init__.py
• vektra-shared/src/vektra_shared/__init__.py

📝 Walkthrough

Walkthrough

The release metadata updates add a 0.7.0 changelog heading dated 2026-07-18 and bump all workspace package versions from 0.6.0 to 0.7.0.

Changes

Release metadata

Layer / File(s)	Summary
Release version alignment CHANGELOG.md, vektra-*/pyproject.toml	The changelog declares version 0.7.0, and all workspace packages update their project version to 0.7.0.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• vektralabs/vektra-stack#81: Similar release-finalization changes updated the changelog and workspace package versions.

Suggested labels: dependencies

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the release finalization for v0.7.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/v0.7.0-release

---

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

[gemini-code-assist]

Code Review

This pull request bumps the version of all Vektra platform components (vektra-admin, vektra-analytics, vektra-app, vektra-core, vektra-index, vektra-ingest, vektra-learn, and vektra-shared) from 0.6.0 to 0.7.0, and adds a corresponding release entry in the CHANGELOG.md. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[coderabbitai]

Actionable comments posted: 1

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

Inline comments:
In `@vektra-analytics/pyproject.toml`:
- Line 3: Align each package’s runtime version constant with the 0.7.0 metadata,
preferably deriving it from package metadata: update the version constant in
vektra-analytics/src/vektra_analytics/__init__.py from 0.4.0-dev,
vektra-app/src/vektra_app/__init__.py from 0.6.0, and
vektra-shared/src/vektra_shared/__init__.py from 0.4.0-dev. The existing
metadata entries require no direct change in vektra-analytics/pyproject.toml:3,
vektra-app/pyproject.toml:3, or vektra-shared/pyproject.toml:3.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3db95f4a-e233-45d1-bc4a-096726c8dad0

📥 Commits

Reviewing files that changed from the base of the PR and between cd77f9e and ab9c3ef.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock, !**/*.lock

📒 Files selected for processing (9)

• CHANGELOG.md
• vektra-admin/pyproject.toml
• vektra-analytics/pyproject.toml
• vektra-app/pyproject.toml
• vektra-core/pyproject.toml
• vektra-index/pyproject.toml
• vektra-ingest/pyproject.toml
• vektra-learn/pyproject.toml
• vektra-shared/pyproject.toml