Skip to content

docs(qdrant): deployment inventory, Compose binding and 2026-11-05 runtime triage - #110

Merged
ViperJuice merged 2 commits into
mainfrom
docs/q106-readback-inventory-20261105
Nov 6, 2026
Merged

ViperJuice merged 2 commits into
mainfrom
docs/q106-readback-inventory-20261105

Conversation

@ViperJuice

@ViperJuice ViperJuice commented Nov 6, 2026 •

Copy link
Copy Markdown
Collaborator

Refs #106

Docs only. This changes no source, tests, lockfile, workflows or repository settings.

Why

Track B of the #106 verification found two gaps in the durable docs:

  • Unlisted client credential source: the migration procedure lists .mcp.env, .mcp.json, CI and shells as client environments. Source and editable checkouts also auto-load .env.local, .env and .env.native from the checkout root (mcp_server/config/environment.py::load_local_env_files) unless PYTHON_DOTENV_DISABLED=1 is set, and those files were missing from the list.
  • Readback not tied to the running service: the readback checked behaviour but nothing tied it to the Compose inputs the running container was created from.

Changes

  • docs/operations/qdrant-authentication.md
    • Lists the dotenv files as client credential sources.
    • Adds a deployment consumer-inventory rule: credential source names only, and "unknown" stays unknown with a named owner.
    • Adds a readback step that compares the container's com.docker.compose.config-hash label with docker compose … config --hash qdrant. That command prints only a hash and never renders the config.
    • Backups get a SHA-256 manifest, and a restore keeps the failed storage aside.
    • States that synthetic CRUD proves authentication, not semantic search.
  • docs/security/dependency-triage-2026-10-31.md: dated 2026-11-05 addendum.
    • The re-scan at 1a61533 finds 278 distinct advisories in 35 packages, with per-package counts identical to the 2026-10-31 triage. No new advisories, and every disposition stands.
    • The certifi advisory now recommends 2026.10.19. That is an availability-only difference, so no security action is needed.
    • Starlette and certifi on pre-upgrade lexical STDIO installs: AuthenticationMiddleware is never instantiated, and no HTTPS consumer is reachable. The addendum lists explicit conditions for reopening.

Verification

  • git diff --check is clean.
  • The Qdrant auth unit and workflow suite passed 94 tests, and the disposable container integration test passed 5 with 0 skipped. Both ran at 1a61533.

Operational acceptance of #106 (live readback, consumer inventory and residual owners) is tracked separately. This PR does not close the issue.

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

ViperJuice and others added 2 commits November 5, 2026 21:07
…riage

Document that source and editable checkouts load .env.local, .env and
.env.native as Qdrant client credential sources, and add a scoped
consumer-inventory rule (credential source names only; unknown is not
none). Bind the live readback to the running container through the
Compose config-hash label, and check the backup against its SHA-256
manifest before a restore. State that synthetic CRUD is not semantic
search acceptance.

Add a dated 2026-11-05 re-scan to the dependency triage: no new
advisories, the certifi 2026.10.19 guidance, and why starlette and
certifi advisories do not apply to pre-upgrade lexical STDIO installs.

Refs #106

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Make the semantic search check optional and separate from the auth readback.
- Bind the config-hash check to step 5's exact op-run/compose invocation.
- Note that PYTHON_DOTENV_DISABLED needs python-dotenv 1.2+ (locked 1.2.2).
- Name the repository's AuthenticationMiddleware, add reranking to the
  no-HTTPS-client conditions, state the count-based re-scan basis, and point
  the residual-risk bullet at the 2026-11-05 host addendum.

Refs #106

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ViperJuice
ViperJuice marked this pull request as ready for review November 6, 2026 16:00
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-06T16:01:30.955121Z 2b94466 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@ViperJuice
ViperJuice merged commit 7ce99e0 into main Nov 6, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant