feat(ontology): traverse evidence-backed projects - #663
Conversation
* fix(ask): release pool before embedding provider work * style: keep load evidence reviewable * docs(gaps): refresh protected delivery evidence * fix(ask): reject blank embedding requests * fix(ask): preserve unavailable embedding short circuit * fix(ask): honor validated precomputed embeddings * fix(ask): honor precomputed embedding envelope * fix(k6): reject unitless request timeouts * fix(migrations): replay global ask queue safely * fix(ask): reject nonfinite embeddings * perf: keep authenticated web reads responsive (#633) * fix(backend): make the similar-VOC SQL audit reason adjacent (hotfix main) The similar-VOC candidate fetch already carried a suppression, but its Safe SQL reason sat three lines above the audited call while the review contract requires the immediately preceding line. Collapse the comment to one adjacent line; the counted total stays 36 because this repairs an existing site rather than adding one. * perf: keep authenticated web reads responsive * docs: record authenticated capacity comparison --------- Co-authored-by: seonghobae <seonghobae@users.noreply.github.com> * feat(semantic): nominate Ask evidence candidates --------- Co-authored-by: seonghobae <seonghobae@users.noreply.github.com>
* feat(ask): verify public semantic claims * docs(gaps): record public verification stack --------- Co-authored-by: seonghobae <seonghobae@users.noreply.github.com>
…ance' into repair-pr632-verification-contract
Co-authored-by: seonghobae <seonghobae@users.noreply.github.com>
* feat(ask): ground answers at knowledge cutoff * docs(gaps): record cutoff candidate exact head --------- Co-authored-by: seonghobae <seonghobae@users.noreply.github.com>
* feat(ask): ground answers at knowledge cutoff * docs(gaps): record cutoff candidate exact head * fix(ci): keep static lineage SQL outside calls --------- Co-authored-by: seonghobae <seonghobae@users.noreply.github.com>
|
Merged current protected-main base and resolved the baseline conflict. New exact head: |
|
Confirmed the label-less ontology behavior is deliberate fail-closed handling: |
|
Confirmed the |
|
Implemented at exact head 7ac1483: both PostgreSQL integration fixtures now apply migrations with autocommit enabled, matching production psql -X semantics for CREATE INDEX CONCURRENTLY; the API fixture returns to transactional mode before seed inserts. The MCP Compose profile now depends on the backend worker, so the documented MCP-only startup has a durable Global Ask consumer. Fixture compilation passed; hosted required Checks remain pending. |
|
Root cause fixed at exact head |
|
Fixed the exact-head Full-suite failures at |
|
Confirmed this informational note at exact head |
Outcome
Closes the PRD-FR-2 gap between persisted
post_project_mentionevidence and the bounded ontology neighborhood.node_project/edge_mention_projectvocabulary mappingstruth_proposedVerification
uv run --extra dev --extra backend pytest tests/test_ontology_neighborhood.py tests/test_ontology_neighborhood_ingestion.py tests/test_ontology.py tests/test_ontology_shapes.py tests/test_migration_replay.py tests/test_public_docstrings.py tests/test_schema.py -q— 102 passedBoundaries
PostgreSQL remains authoritative. This PR does not create a project catalog, promote extracted mentions, expose hidden counts, or add mathematical weights.