Follow-ups from the post-merge review of #158 (switch to crates.io duroxide-pg).

Changes

• src/lib.rs: drop unused DUROXIDE_SCHEMA imports in two #[pg_test] helpers (wait_for_completion, get_duroxide_status); only ensure_store_ready actually uses it.
• docs/dep_issues.md:
  • bump Last Updated to 2026-05-26.
  • restore the historical duroxide-pg-opt#6 reference as plain text with a note explaining the private-repo origin (the blanket duroxide-pg-opt \u2192 duroxide-pg rewrite in Switch duroxide-pg-opt → duroxide-pg #158 turned it into a 404).
  • refresh the Version Compatibility Matrix to the current 0.2.2 / duroxide 0.1.29 / duroxide-pg 0.1.34 row and collapse legacy entries into a single \u22640.2.1 row noting Azure's fork owns that line.
• docs/extension_lifecycle.md: bump Last Updated to 2026-05-26 (substantive content changed in Switch duroxide-pg-opt → duroxide-pg #158 when the long-poll text was removed).
• docs/upgrade-testing.md: restructure the Minor release checklist so step 3 (provider-compat-line bump) clearly applies to every minor release, and move the first-minor-after-major items into bullets under "additionally". Previously the global numbering 1 \u2192 2 \u2192 3 \u2192 (heading) \u2192 4 \u2192 5 made it look like step 3 was conditional.

Validation

• cargo check --features pg17,pg_test clean (only preexisting extract_host warning in src/ssrf.rs).
• No functional code changes; doc-only otherwise.

Out of scope (operator follow-up)

• Removing the repo/org Codespaces/Actions secrets GH_PAT and DUROXIDE_PG_OPT_TOKEN, since no workflow references them anymore.