
PRIOR ITERATIONS FINDINGS (avoid duplicate flags — these are already covered):

--- iteration-001.md ---
| L-001-001 | P1 | correctness | .opencode/skills/system-spec-kit/shared/embeddings/profile.ts:147 | "return 'hf-local';" | confirmed-residue | Align `resolveActiveProfileProvider()` with the canonical resolver by including the llama-cpp availability step before hf-local, or delegate active profile creation to `getStartupEmbeddingProfile()`. |
| L-001-002 | P1 | correctness | .opencode/skills/system-spec-kit/scripts/evals/run-ablation.ts:51 | "const PROD_DB_PATH = resolveActiveProfileDbPath(undefined, DB_DIR);" | confirmed-residue | After fixing the shared profile resolver, keep this caller covered with a no-key + llama-cpp-installed regression test so ablation reads the llama-cpp profile DB. |
| L-001-003 | P1 | correctness | .opencode/skills/system-spec-kit/scripts/evals/run-bm25-baseline.ts:40 | "const PROD_DB_PATH = resolveActiveProfileDbPath(undefined, DB_DIR);" | confirmed-residue | Route BM25 baseline DB selection through the canonical startup profile so the no-cloud-key default is llama-cpp, not hf-local. |
| L-001-004 | P1 | correctness | .opencode/skills/system-spec-kit/scripts/evals/map-ground-truth-ids.ts:35 | "const DB_PATH = resolveActiveProfileDbPath(undefined, DB_DIR);" | confirmed-residue | Use the canonical provider profile for ground-truth mapping; otherwise the mapper targets the hf-local DB while runtime writes llama-cpp. |
| L-001-005 | P1 | correctness | .opencode/skills/system-spec-kit/mcp_server/lib/eval/memory-state-baseline.ts:64 | "return resolveActiveProfileDbPath(undefined, DEFAULT_DB_DIR);" | confirmed-residue | Replace or repair this helper dependency so memory baseline captures the actual active profile DB under the llama-cpp default. |
| L-001-006 | P1 | correctness | .opencode/skills/system-spec-kit/mcp_server/scripts/migrations/create-checkpoint.ts:38 | "resolveActiveProfileDbPath(undefined, path.resolve(process.cwd(), '.opencode/skills/system-spec-kit/mcp_server/database'))," | confirmed-residue | Make checkpoint creation resolve the same active DB as runtime; a no-key llama-cpp install should checkpoint `context-index__llama-cpp__...sqlite`. |
| L-001-007 | P1 | correctness | .opencode/skills/system-spec-kit/mcp_server/scripts/migrations/restore-checkpoint.ts:37 | "resolveActiveProfileDbPath(undefined, path.resolve(process.cwd(), '.opencode/skills/system-spec-kit/mcp_server/database'))," | confirmed-residue | Make checkpoint restore use the canonical active profile path so restores do not silently target hf-local on llama-cpp default installs. |
| L-001-008 | P1 | correctness | .opencode/skills/system-spec-kit/config/config.jsonc:28 | "\"databasePath\": \".opencode/skills/system-spec-kit/mcp_server/dist/database/context-index.sqlite\"," | confirmed-residue | Remove or rewrite this doc-only config field to describe provider-keyed DB derivation; the fixed literal conflicts with post-014 filenames. |
| L-001-009 | P1 | correctness | .opencode/skills/system-spec-kit/package-lock.json:17 | "\"onnxruntime-common\": \"^1.21.0\"" | confirmed-residue | Regenerate the lockfile after the package.json removals so the root lock package no longer declares `onnxruntime-common` as a direct dependency. |
| L-001-010 | P1 | correctness | .opencode/skills/system-spec-kit/package-lock.json:40 | "\"onnxruntime-common\": \"^1.21.0\"," | confirmed-residue | Regenerate the lockfile so the `mcp_server` package lock entry matches `mcp_server/package.json` and drops the direct ONNX runtime dependency. |
| L-001-011 | P1 | correctness | .opencode/skills/system-spec-kit/shared/embeddings/providers/hf-local.ts:301 | "// Detect native module version mismatch (onnxruntime-node, sharp)" | confirmed-residue | Remove the `onnxruntime-node` production-code reference or generalize the message to native module failures without naming the rejected runtime. |

--- iteration-002.md ---
| L-002-001 | P1 | traceability | PUBLIC_RELEASE.md:25 | "context-index.sqlite" | confirmed-residue | Replace the single-file consumer-project database example with the provider-keyed active profile filename pattern, preferably naming the llama-cpp default DB when no cloud keys are set. |
| L-002-002 | P1 | traceability | .opencode/skills/system-spec-kit/mcp_server/INSTALL_GUIDE.md:113 | "\| `.opencode/skills/system-spec-kit/mcp_server/database/context-index.sqlite` \| Default repo-local memory database used by the checked-in configs \|" | confirmed-residue | Rewrite the install guide's runtime-path section to say configs point at `SPEC_KIT_DB_DIR` and runtime derives `context-index__<provider>__<safe-model>__<dim>__<dtype>.sqlite`; sweep the repeated sqlite inspection and backup snippets in the same file. |
| L-002-003 | P1 | traceability | .opencode/skills/system-spec-kit/mcp_server/INSTALL_GUIDE.md:116 | "local fallback stays on `context-index.sqlite`, while Voyage and OpenAI profiles get their own profile-specific filenames" | confirmed-residue | Remove the special-case claim that local fallback stays on the legacy filename; all Memory MCP embedding profiles should be documented as provider-keyed filenames. |
| L-002-004 | P1 | traceability | .opencode/skills/system-spec-kit/mcp_server/INSTALL_GUIDE.md:212 | "- `onnxruntime-common` (ONNX model runtime)" | confirmed-residue | Update the current dependency list after the ONNX runtime package removal; keep hf-local EmbeddingGemma documentation, but do not claim `onnxruntime-common` is installed directly. |
| L-002-005 | P1 | traceability | .opencode/skills/system-spec-kit/references/memory/memory_system.md:25 | "\| Database \| `mcp_server/dist/database/context-index.sqlite` \| SQLite with FTS5 + vector embeddings (canonical runtime path; `mcp_server/database/context-index.sqlite` is a compatibility symlink) \|" | confirmed-residue | Replace the canonical database row with the active-profile DB path contract and mention compatibility only as historical/legacy behavior if still needed. |
| L-002-006 | P1 | traceability | .opencode/skills/system-spec-kit/manual_testing_playbook/23--doctor-commands/323-doctor-memory-fresh-install.md:10 | "bootstrap the active hf-local default profile database, `mcp_server/database/context-index__hf-local__onnx-community_embeddinggemma-300m-onnx__768__q8.sqlite`" | confirmed-residue | Rebase the fresh-install doctor scenario on the canonical auto resolver: cloud keys first, otherwise llama-cpp when GGUF runtime is installed, with hf-local only as fallback. |
| L-002-007 | P1 | traceability | .opencode/skills/system-spec-kit/manual_testing_playbook/23--doctor-commands/324-doctor-memory-drift-detection.md:39 | "such as `.opencode/skills/system-spec-kit/mcp_server/database/context-index__hf-local__onnx-community_embeddinggemma-300m-onnx__768__q8.sqlite` for the hf-local default." | confirmed-residue | Change the example default database to the llama-cpp profile DB, or phrase hf-local as an explicit fallback/override scenario. |
| L-002-008 | P1 | traceability | .opencode/skills/system-spec-kit/manual_testing_playbook/23--doctor-commands/325-doctor-memory-long-pole-rebuild.md:39 | "Use a disposable workspace with a populated active hf-local default profile database and vector DB." | confirmed-residue | Update the long-pole rebuild scenario to use the active resolved profile DB instead of assuming hf-local is the default profile. |
| L-002-009 | P1 | traceability | .opencode/skills/system-spec-kit/manual_testing_playbook/23--doctor-commands/327-doctor-memory-disk-pressure.md:43 | "free space is less than `2 * (active hf-local default profile DB bytes + vector DB bytes)`" | confirmed-residue | Make the disk-pressure precondition compute against the active resolved profile DB; keep Voyage as a cloud-key branch, but add llama-cpp as the no-cloud-key default. |
| L-002-010 | P2 | traceability | .opencode/skills/system-spec-kit/feature_catalog/16--tooling-and-scripts/29-setup-native-module-health-and-mcp-installation.md:32 | "attempts to load `better-sqlite3` plus optional `onnxruntime-node` and `sharp` installs" | confirmed-residue | Refresh the feature catalog to match the post-022 native-module health surface; remove the rejected `onnxruntime-node` probe from current behavior docs unless the code still intentionally probes it. |

--- iteration-003.md ---
| L-003-001 | P1 | maintainability | .codex/config.toml:16 | "e.g., context-index__hf-local__onnx-community_embeddinggemma-300m-onnx__768__q8.sqlite" | confirmed-residue | Update the Codex config comment to use the llama-cpp default DB example, or phrase the hf-local filename strictly as fallback/override. |
| L-003-002 | P1 | maintainability | .codex/config.toml:17 | "for the Setup A default since 014/012" | confirmed-residue | Remove the stale Setup A default claim; post-014 no-cloud-key default is llama-cpp when GGUF runtime is installed. |
| L-003-003 | P2 | maintainability | .opencode/commands/doctor/update.md:213 | "`mcp_server/database/context-index.sqlite`" | confirmed-residue | Refresh the `/doctor:update` subsystem contract so memory DB examples use the active provider-keyed profile path instead of the legacy singleton filename. |
| L-003-004 | P2 | maintainability | .opencode/commands/doctor/update.md:268 | "`mcp_server/database/context-index.sqlite` and `mcp_server/database/context-index.sqlite.pre-doctor-update.*.bak`" | confirmed-residue | Update the allowed-target example to describe provider-keyed memory DBs and their matching backup pattern. |
| L-003-005 | P2 | maintainability | .opencode/commands/doctor/assets/doctor_update.yaml:102 | "- \"mcp_server/database/context-index.sqlite\"  # memory FTS/metadata DB" | confirmed-residue | Replace the hardcoded update workflow target with active-profile DB resolution language or a provider-keyed glob constrained by the canonical resolver. |
| L-003-006 | P2 | maintainability | .opencode/commands/doctor/assets/doctor_update.yaml:416 | "const db = new Database('.opencode/skills/system-spec-kit/mcp_server/database/context-index.sqlite');" | confirmed-residue | Make the embedded count snippet resolve the active profile DB before opening SQLite, otherwise the workflow can audit the wrong file. |
| L-003-007 | P2 | maintainability | .opencode/commands/doctor/assets/doctor_causal-graph.yaml:78 | "- \"mcp_server/database/context-index.sqlite\"  # host DB for causal_edges table" | confirmed-residue | Reword the causal-graph mutation boundary around the active memory DB path instead of the legacy singleton filename. |
| L-003-008 | P2 | maintainability | .opencode/commands/doctor/assets/doctor_causal-graph.yaml:174 | "context-index.sqlite missing -> STATUS=MISSING with recommendation to run /doctor memory" | confirmed-residue | Change the missing-DB halt condition to check the active resolved profile DB, not `context-index.sqlite`. |
| L-003-009 | P2 | maintainability | .opencode/skills/system-spec-kit/scripts/tests/fixtures/manual-playbook-fixture.ts:609 | "MEMORY_DB_PATH points directly to the active hf-local default profile database" | confirmed-residue | Rebase the manual playbook fixture text on the canonical active profile, with hf-local described only as fallback. |
| L-003-010 | P2 | maintainability | .opencode/skills/system-spec-kit/scripts/tests/fixtures/manual-playbook-fixture.js:380 | "MEMORY_DB_PATH points directly to context-index.sqlite for disposable fixtures." | confirmed-residue | Keep the disposable fixture DB if tests need it, but update the generated fixture prose so it does not teach the legacy singleton DB as the memory path. |

--- iteration-004.md ---
| L-004-001 | P1 | correctness | .gemini/scripts/spec-kit-memory.sh:11 | "EMBEDDINGS_PROVIDER   - auto \| voyage \| openai \| hf-local (default: auto)" | confirmed-residue | Add `llama-cpp` to the launcher contract so Gemini users see the canonical provider set. |
| L-004-002 | P1 | correctness | .gemini/scripts/spec-kit-memory.sh:32 | "DEFAULT_DB_PATH=\"${REPO_ROOT}/.opencode/skills/system-spec-kit/mcp_server/database/context-index.sqlite\"" | confirmed-residue | Stop defaulting `MEMORY_DB_PATH` to the singleton sqlite file; let the server derive the provider-keyed DB from `SPEC_KIT_DB_DIR` or the active profile. |
| L-004-003 | P1 | correctness | .gemini/scripts/spec-kit-memory.sh:33 | "HF_LOCAL_DB_PATH=\"${REPO_ROOT}/.opencode/skills/system-spec-kit/mcp_server/database/context-index__hf-local__nomic-ai_nomic-embed-text-v1.5__768.sqlite\"" | confirmed-residue | Remove the stale nomic hf-local path or replace it with the current EmbeddingGemma q8 fallback only for explicit hf-local fallback scenarios. |
| L-004-004 | P1 | correctness | .gemini/scripts/spec-kit-memory.sh:50 | "Fall back to HF-local database when no API keys are available" | confirmed-residue | Change the no-cloud-key branch to respect the canonical llama-cpp-when-installed default before hf-local fallback. |
| L-004-005 | P1 | correctness | .gemini/scripts/spec-kit-memory.sh:53 | "auto\|hf-local)" | confirmed-residue | Do not route `auto` through the hf-local DB override; reserve hf-local path pinning for explicit `EMBEDDINGS_PROVIDER=hf-local` if any override remains. |
| L-004-006 | P1 | correctness | .opencode/commands/doctor/scripts/mcp-doctor.sh:200 | "local db_file=\"$db_dir/context-index.sqlite\"" | confirmed-residue | Resolve the active provider profile DB for the database health check instead of checking only the legacy singleton filename. |
| L-004-007 | P1 | correctness | .opencode/commands/doctor/assets/doctor_memory.yaml:22 | "Memory doctor workflows treat context-index.sqlite and the voyage vector DB as" | confirmed-residue | Rewrite the memory doctor invariant around active provider-keyed profile DBs, including llama-cpp and OpenAI profiles. |
| L-004-008 | P1 | correctness | .opencode/commands/doctor/assets/doctor_memory.yaml:64 | "- \"mcp_server/database/context-index.sqlite\"  # primary memory FTS/metadata DB" | confirmed-residue | Replace the fixed allowed target with canonical active-profile DB resolution or a constrained provider-keyed target set. |
| L-004-009 | P1 | correctness | .opencode/commands/doctor/assets/doctor_memory.yaml:145 | "- \"Bash: stat -f '%m %z' database/context-index.sqlite (mtime + size)\"" | confirmed-residue | Make Phase 0 discovery stat the active resolved profile DB rather than the legacy singleton file. |

--- iteration-005.md ---
| L-005-001 | P1 | traceability | .opencode/install_guides/README.md:600 | `"EMBEDDINGS_PROVIDER": "hf-local"` | confirmed-residue | Change the install-guide `opencode.json` example to leave `EMBEDDINGS_PROVIDER` unset or set it to `auto`, so the sample does not pin new installs to the fallback provider. |
| L-005-002 | P1 | traceability | .opencode/install_guides/README.md:925 | `"Ollama running with nomic-embed-text model"` | confirmed-residue | Remove the Ollama/nomic checklist item or replace it with verification of the active `llama-cpp`/EmbeddingGemma profile DB. |
| L-005-003 | P1 | traceability | .opencode/install_guides/README.md:938 | `"ollama list \| grep -q \"nomic-embed-text\" &&"` | confirmed-residue | Replace the final verification command with a provider-cascade check that does not require Ollama or the legacy nomic model. |
| L-005-004 | P1 | traceability | .opencode/install_guides/README.md:1427 | `"ollama pull nomic-embed-text"` | confirmed-residue | Remove the quick-reference nomic pull command from the default install path; if retained, label it as unrelated optional Ollama usage. |
| L-005-005 | P2 | traceability | .opencode/install_guides/README.md:376 | `"Prerequisites → Ollama → Code Mode → Spec Kit Memory →"` | confirmed-residue | Refresh the full-bundle sequence so Ollama is not shown as a required step before Spec Kit Memory. |

--- iteration-006.md ---
| L-006-001 | P1 | maintainability | .opencode/skills/system-spec-kit/scripts/setup/install.sh:195 | "otherwise HF local fallback stays active" | confirmed-residue | Update the generated MCP config note so auto mode documents Voyage -> OpenAI -> llama-cpp -> hf-local, with hf-local only as the final fallback. |
| L-006-002 | P1 | maintainability | .opencode/skills/system-spec-kit/mcp_server/tests/embeddings.vitest.ts:103 | "auto mode defaults to hf-local with no keys" | confirmed-residue | Rework this test to model llama-cpp availability explicitly: assert llama-cpp when the GGUF runtime is available and hf-local only when the availability probe fails. |
| L-006-003 | P1 | maintainability | .opencode/skills/system-spec-kit/mcp_server/tests/embeddings.vitest.ts:249 | "startup profile keeps the local fallback database path when no API keys are present" | confirmed-residue | Change the startup-profile test to expect the llama-cpp profile DB under the installed-runtime path, or rename/setup it as an explicit llama-cpp-unavailable fallback case. |
| L-006-004 | P1 | maintainability | .opencode/commands/doctor/_routes.yaml:29 | "mcp_server/database/context-index.sqlite + context-index__voyage__voyage-4__1024.sqlite" | confirmed-residue | Replace the fixed memory route boundary with active provider-keyed profile DB language; do not single out the legacy singleton or Voyage-only vector DB as the mutation target set. |
| L-006-005 | P2 | maintainability | .opencode/commands/doctor.md:43 | "`mcp_server/database/context-index.sqlite` + voyage embedding DB" | confirmed-residue | Refresh the human-readable doctor router mirror to match `_routes.yaml` after the active-profile wording is fixed, including the help text that still teaches a singleton missing-DB warning. |
| L-006-006 | P1 | maintainability | .opencode/skills/system-spec-kit/mcp_server/lib/eval/ground-truth-generator.ts:100 | "production context-index.sqlite DB" | confirmed-residue | Reword the eval helper comment around the active provider-keyed production DB, or reference the mapping script without naming the obsolete singleton file. |

--- iteration-007.md ---
| L-007-001 | P1 | correctness | .opencode/skills/system-spec-kit/.env.example:11 | "Provider selection (auto \| voyage \| openai \| hf-local)" | confirmed-residue | Add `llama-cpp` to the provider list so the env template exposes the canonical auto-selectable local provider. |
| L-007-002 | P1 | correctness | .opencode/skills/system-spec-kit/.env.example:12 | "Default: auto (detects from API keys, falls back to hf-local)" | confirmed-residue | Rewrite the auto description to include the full Voyage -> OpenAI -> llama-cpp -> hf-local cascade. |
| L-007-003 | P1 | correctness | .opencode/skills/system-spec-kit/.env.example:23 | "HuggingFace local model (default when no API keys set)" | confirmed-residue | Rephrase hf-local as the final fallback, not the no-cloud-key default when llama-cpp is installed. |
| L-007-004 | P1 | correctness | .opencode/skills/system-spec-kit/.env.example:25 | "EMBEDDINGS_MODEL=nomic-ai/nomic-embed-text-v1.5" | confirmed-residue | Replace the commented current-model example with `onnx-community/embeddinggemma-300m-ONNX`, or label nomic strictly as a legacy opt-in example. |
| L-007-005 | P1 | correctness | .opencode/skills/system-spec-kit/.env.example:66 | "Choose a provider (or use default hf-local)" | confirmed-residue | Update the setup checklist to say `auto` defaults through cloud keys, then llama-cpp when available, then hf-local fallback. |
| L-007-006 | P1 | correctness | .vscode/mcp.json:20 | "Current: 'auto' (VOYAGE_API_KEY -> OPENAI_API_KEY -> hf-local). Options: 'auto', 'voyage', 'openai', 'hf-local'" | confirmed-residue | Bring the VS Code MCP config mirror in line with the canonical provider list and cascade by inserting `llama-cpp` before hf-local. |
| L-007-007 | P1 | correctness | .vscode/mcp.json:22 | "Get Voyage key: https://dash.voyageai.com/api-keys (recommended, 8% better than OpenAI)" | confirmed-residue | Remove the stale marketing comparison from the committed config note; keep only neutral key-acquisition guidance. |
| L-007-008 | P1 | correctness | .vscode/mcp.json:39 | "Default embedding: all-MiniLM-L6-v2 (local, no API key needed)" | confirmed-residue | Change the CocoIndex VS Code config note to `google/embeddinggemma-300m` with sentence-transformers/bf16/768-dim wording. |
| L-007-009 | P1 | correctness | .opencode/skills/system-spec-kit/scripts/tests/test-folder-detector-functional.js:22 | "const REAL_DB_PATH = path.join(SKILL_ROOT, 'mcp_server/database/context-index.sqlite');" | confirmed-residue | Stop the functional test from targeting the legacy singleton DB; resolve the active provider-keyed profile path or use an isolated fixture DB. |

--- iteration-008.md ---
| L-008-001 | P1 | traceability | .opencode/specs/system-spec-kit/026-graph-and-context-optimization/014-local-embeddings-setup-a/017-llama-cpp-default-flip/description.json:5 | "auto mode was restored to hf-local and llama-cpp remains explicit opt-in." | confirmed-residue | Refresh the 017 packet metadata to match the accepted ship state: llama-cpp became the no-cloud-key auto default when the GGUF runtime is installed, with hf-local as fallback. |
| L-008-002 | P1 | traceability | .opencode/specs/system-spec-kit/026-graph-and-context-optimization/014-local-embeddings-setup-a/017-llama-cpp-default-flip/graph-metadata.json:54 | "auto mode was restored to hf-local and llama-cpp remains explicit opt-in." | confirmed-residue | Regenerate or patch graph metadata so memory/review discovery does not resurface the reversed 017 conclusion. |
| L-008-003 | P1 | traceability | .opencode/skills/system-spec-kit/manual_testing_playbook/23--doctor-commands/326-doctor-memory-sigint-cancellation.md:45 | "`shasum .opencode/skills/system-spec-kit/mcp_server/database/context-index__hf-local__onnx-community_embeddinggemma-300m-onnx__768__q8.sqlite`" | confirmed-residue | Make the SIGINT playbook record the active resolved provider DB checksum, using the llama-cpp profile for the no-cloud-key installed-runtime case and hf-local only for fallback/override cases. |
| L-008-004 | P2 | traceability | README.md:142 | "# Option A: Voyage AI (cloud, requires API key, opt-in only)" | confirmed-residue | Rephrase Voyage setup as auto-selected when `VOYAGE_API_KEY` exists; avoid "opt-in only" wording unless it explicitly means "provide a key." |
| L-008-005 | P2 | traceability | .opencode/install_guides/README.md:191 | "Voyage (cloud opt-in), OpenAI (cloud opt-in)." | confirmed-residue | Update the install-guide provider note to say cloud providers are selected automatically by key presence in the canonical cascade. |
| L-008-006 | P2 | traceability | .opencode/skills/system-spec-kit/README.md:693 | "Cloud opt-in. Requires `VOYAGE_API_KEY`. Gated by egress guard." | confirmed-residue | Reword the provider table so Voyage is not presented as a separate explicit opt-in path; it should say `auto` selects Voyage first when the key is present. |

--- iteration-009.md ---
| L-009-001 | P1 | maintainability | .opencode/skills/system-spec-kit/mcp_server/scripts/migrations/restore-checkpoint.ts:169 | "`${toTimestampId(now)}__pre-restore-context-index.sqlite`," | confirmed-residue | Include the active profile key in pre-restore backup filenames, or use a neutral `pre-restore-memory-db.sqlite` suffix so checkpoint artifacts do not preserve the legacy singleton DB name. |
| L-009-002 | P2 | maintainability | .opencode/skills/system-spec-kit/scripts/evals/run-bm25-baseline.ts:10 | "// Live production context-index.sqlite and record results in the" | confirmed-residue | Refresh the eval script header to describe the active provider-keyed production DB path resolved by `resolveActiveProfileDbPath()`. |
| L-009-003 | P2 | maintainability | .opencode/skills/system-spec-kit/shared/chunking.ts:18 | "* Based on nomic-embed-text-v1.5 context window (~8192 tokens)." | confirmed-residue | Re-anchor the shared chunking constant comment to provider-agnostic limits or the current EmbeddingGemma/Voyage/OpenAI envelope instead of a nomic-era model. |
| L-009-004 | P2 | maintainability | .opencode/skills/system-spec-kit/mcp_server/lib/parsing/content-normalizer.ts:210 | "* embedding models (nomic-embed-text-v1.5 and compatible providers)." | confirmed-residue | Replace the nomic-specific prose with provider-neutral wording, or name the current supported provider family without implying nomic is the semantic normalization baseline. |
| L-009-005 | P2 | maintainability | .opencode/skills/system-spec-kit/shared/embeddings/providers/openai.ts:248 | "// OpenAI does not use task prefixes like nomic - same method for documents and queries" | confirmed-residue | Reword the comment to say OpenAI uses the same method for documents and queries, without preserving nomic as the comparison anchor. |
