Skip to content

docs(backlog): track v0.5.0 release-PR review feedback#72

Merged
fvadicamo merged 2 commits into
developfrom
docs/backlog-v050-pr71-feedback
Apr 26, 2026
Merged

docs(backlog): track v0.5.0 release-PR review feedback#72
fvadicamo merged 2 commits into
developfrom
docs/backlog-v050-pr71-feedback

Conversation

@fvadicamo
Copy link
Copy Markdown
Contributor

Summary

Two new BACKLOG entries from the Gemini review on the v0.5.0 release PR (#71).
All medium/low severity, deferred from v0.5.0 per zero-new-commit policy on
release PRs.

New entries

  • DEBT-020 (medium): audit log skipped when request_id is missing on admin writes. patch_namespace_config and similar endpoints should synthesize a fallback uuid4() so NFR-007 holds even if the request-id middleware misbehaves.
  • DEBT-021 (low): _fetch_document_names adds a separate Postgres round-trip per query. The WI-2 plan called for a JOIN with source_documents inside the existing chunk-fetch query; v0.5.0 opted for a clarity-first separate call, consolidation tracked here.

Other Gemini feedback (not new entries)

Comment Disposition
:root injection scope (chat-ui.js:145) Already DEBT-018
Missing UTC, datetime imports (api.py:32) False positive — imports present at line 13
self_inner in nested test fakes (test_pipeline.py x4) Style noise on disambiguating closure-bound mocks; no action

Test plan

  • CI green (lint + tests)
  • BACKLOG.md renders correctly on GitHub

Refs

Two new DEBT entries from Gemini review on the develop->main release PR
(#71). All medium/low severity, deferred from v0.5.0 release per
zero-new-commit policy on release PRs:

- DEBT-020 (medium): audit log skipped when request_id is missing on
  admin writes. patch_namespace_config and similar endpoints should
  synthesize a fallback uuid4 so NFR-007 holds even if the request-id
  middleware misbehaves.

- DEBT-021 (low): _fetch_document_names adds a separate Postgres
  round-trip per query. The WI-2 plan called for a JOIN with
  source_documents inside the existing chunk-fetch query; v0.5.0 opted
  for a clarity-first separate call, consolidation tracked here.

Three other Gemini comments on the same review map to existing items
(DEBT-018 for :root scope) or were false positives (claimed missing
imports already present at line 13). The four code-quality bot LOW
nitpicks ("self_inner" in nested test fakes) are style noise on
disambiguating closure-bound mocks; no entry created.
@fvadicamo fvadicamo added the documentation Improvements or additions to documentation label Apr 26, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 26, 2026

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • .s2s/BACKLOG.md is excluded by !.s2s/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6cf80b47-1793-44e3-b608-f2fd15985add

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/backlog-v050-pr71-feedback

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

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

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds two new technical debt entries to the backlog: DEBT-020, which addresses missing audit logs when a request ID is absent, and DEBT-021, which aims to optimize document name retrieval. Feedback suggests broadening the scope of DEBT-020 to include all sensitive endpoints rather than just admin writes to ensure comprehensive audit coverage. Additionally, for DEBT-021, the proposed optimization should be generalized to support non-SQL providers like Qdrant, ensuring consistency with the project's multi-provider architecture.

Comment thread .s2s/BACKLOG.md Outdated
Comment thread .s2s/BACKLOG.md Outdated
Address two Gemini review comments on PR #72:

- DEBT-020 (3143979031): title "on admin writes" too narrow per NFR-007
  ("audit every sensitive content access"). Sensitive read endpoints like
  `get_conversation_turns` (vektra-admin/api.py:491-539) share the same
  `if request_id:` pattern. Renamed to "on sensitive endpoints" and
  expanded the sweep + acceptance criteria to cover both reads and writes.

- DEBT-021 (3143979036): "Single Postgres query" was Pgvector-centric and
  ignored the multi-provider architecture. Reframed as
  "provider-aligned filename resolution" with two explicit paths:
  (A) Postgres-side JOIN — provider-agnostic since chunks live in
  document_chunks for both pgvector and qdrant deployments,
  (B) Qdrant-native payload denormalization — follow-up for
  Qdrant-heavy deployments, separate ingest-side change.
Copy link
Copy Markdown
Contributor Author

@fvadicamo fvadicamo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both Gemini comments addressed in 855bebd. DEBT-020 scope broadened to sensitive endpoints (reads + writes); DEBT-021 reframed for multi-provider architecture with explicit pgvector and qdrant optimization paths.

@fvadicamo fvadicamo self-assigned this Apr 26, 2026
@fvadicamo fvadicamo merged commit 1ddcd7d into develop Apr 26, 2026
19 checks passed
@fvadicamo fvadicamo deleted the docs/backlog-v050-pr71-feedback branch April 26, 2026 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant