v0.36.3

Fixed

• Budgeted definition bodies across hosts: implementation_lookup no longer stops at a fixed 30-line preview. Optional tokenBudget bounds visible text to 128–4,000 estimated ordinary-text cl100k_base tokens (default 1,200). Full retrieved source is shown when it fits; otherwise whole-line prefixes, closed fences and explicit partial/omission notices preserve the distinction between source and explanation.
• Distinct-file discovery: Reserve unclipped original-ranked file/range citations before spending the remaining budget on source bodies. Large early declarations no longer hide later files whose citations fit. If citation metadata itself cannot fit, retain a ranked prefix and disclose omitted locations.
• Structural prose ranking: Do not prepend a synthetic definition-priority lane merely because descriptive prose incidentally matches declaration names or paths. Explicit identifier/definition lookups, scopes and hybrid lane behavior remain intact.
• Ordinary source token counting: Valid literal spellings such as <|endoftext|> and FIM markers are preserved rather than rejected by the token estimator. The declared minimum tiktoken 1.0.15 ordinary-encoding API was exercised with exact literal round-trip proof.

Compatibility and limits

Preferred package: open-codebase-index@0.36.3. opencode-codebase-index@0.36.3 remains the synchronized compatibility identity; native names, persisted indexes and host configuration paths are unchanged. The publication workflow builds five required native targets plus experimental Windows ARM64.

The visible-text budget does not reduce MCP structured results or Pi/omp details. Those payloads can exceed the text budget. Retrieved chunks/citations are not proof of complete declarations or dependency closure. Citation reservation can reduce body detail in tight budgets; generic search previews keep their existing limits.

The frozen studies and development-exposed format diagnostic remain unchanged. This patch does not establish an unseen-quality, speed or general-superiority claim.

Observed source verification

• Independent implementation and tokenizer-remedy review: no remaining blockers.
• Source full local gate: 2,680 tests passed / 6 skipped; 142 files passed / 1 skipped, with serialized local workers and unchanged assertions.
• Exact merged-source-main CI passed at 2b0dae451117b56bcb8570b355290d2dadec9aa3; all 13 current exact-head main checks succeeded. All three open security-alert boards were empty.
• Actual built-source MCP: 44-line marker-bearing source complete at 1,200 (344 estimated tokens), marked whole-line prefix at 128 (125 tokens), unchanged structured data; both original-ranked citations for two 324-line declarations remain visible at 1,200 (1,198 tokens).

Observed release preparation

• Full release gate passed after native bootstrap in the fresh owned worktree: build/CLI smoke, native build, typecheck, lint, 2,680 tests passed / 6 skipped; 142 files passed / 1 skipped. Serialized local workers, unchanged assertions. The initial missing-binding prerequisite failure is retained; no production-code change was made for it.
• Release PR #435 passed exact-head CI 37894001297 and all 19 current checks before merging at ae438b2ac60ae6254f2e9b6a796110e0789dac02.
• Actual built release-version MCP reports 0.36.3 and passes the same marker-body, unchanged structured-payload and two-file original-citation assertions. Registry installation is a separate post-publication check.
• Exact merged-release-main CI 37895339659 completed successfully at ae438b2ac60ae6254f2e9b6a796110e0789dac02; all 13 individual latest-head checks succeeded. All three alert boards were rechecked empty before the annotated tag.

Registry 0.36.3 installation, cryptographically verified npm provenance and fresh normal-profile native omp results are not claimed before publication. Observed post-publication verification will be recorded on release PR #435; published GitHub releases are immutable.

Full changelog · Complete delta