v0.105.0

v0.105.0 is a non-breaking acquisition release that lets planner tasks become reviewed connector workflows instead of stopping at suggestions.

What Changed

Area	Change	Why it matters
Go SDK	AcquisitionExecutionPreview and AcquisitionExecutionExecute	Turns existing acquisition-plan tasks into dry-run or explicitly executed connector runs
REST API	POST /v1/namespaces/{ns}/acquisition/execute	Gives operators and dashboards a source-constrained execution workflow beside /acquisition/plan
Connectors	search and crawler connector types	Lets teams plug existing search/crawl systems into contextdb without baking in one vendor
Source controls	Request and connector allowed_source_ids filters	Prevents unreviewed connectors from writing results outside approved source lanes
SDKs	TypeScript and Python helpers	Makes connector previews available from app clients without hand-writing REST calls
Feature metadata	acquisition-execution-connectors	Lets live services advertise the new connector execution surface

Operator Flow

Start with the dry run:

curl -X POST http://localhost:7701/v1/namespaces/my-app/acquisition/execute \
  -H "Content-Type: application/json" \
  -d '{
    "budget": 2,
    "allowed_source_ids": ["docs/runbook"],
    "connectors": [
      {
        "id": "docs-search",
        "type": "search",
        "endpoint": "https://search.example.internal/contextdb",
        "allowed_source_ids": ["docs/runbook"]
      }
    ]
  }'

After reviewing the connector calls and source allow-list, repeat with "execute": true. Execution sends each connector the task query and prompt, accepts either an item array or { "items": [...] }, filters returned items by source, and writes admitted content through the normal namespace write path.

Compatibility

This release is additive. Existing acquisition planning, knowledge gaps, writes, retrieval, GraphQL planner queries, and SDK clients continue to work unchanged. Connector execution is opt-in and dry-run by default; writes require explicit execute.

Verification

The release includes Go SDK coverage for dry-run preview, explicit execution gating, connector response ingestion, and source allow-list filtering. REST contract coverage verifies the dry-run endpoint shape.