Skip to content

Remove duplicate fresh-index embedding pass - #5

Merged
unicornz-code merged 3 commits into
mainfrom
fix-cold-double-embedding
Sep 5, 2026
Merged

Remove duplicate fresh-index embedding pass#5
unicornz-code merged 3 commits into
mainfrom
fix-cold-double-embedding

Conversation

@unicornz-code

Copy link
Copy Markdown

Summary

  • port only MinishLab/semble PR fix: Double embedding pass on fresh index MinishLab/semble#260's fresh-index correction
  • reuse the already-produced ordered per-file vectors instead of embedding every cold chunk twice
  • prove total encoded texts equal produced chunks and preserve vector/order identity
  • add benchmark-only phase instrumentation for exact cold-index and Model2Vec boundaries
  • stabilize one unrelated random-mock ranking assertion exposed by the changed encode-call schedule

Provenance

Production src/semble/index/create.py is byte-identical to upstream commit a79078007f21842eb8325c8217b3acd4d050d578. No upstream installer/version/assets/result claims were imported. Context-bound Semble 0.7.1 MCP behavior is unchanged.

Validation

  • 361 tests passed, 97% coverage
  • Ruff check/format passed
  • pydoclint passed
  • mypy passed
  • all pre-commit hooks passed
  • wheel and sdist built
  • independent read-only review: PASS after profiler findings were remediated

The profiler explicitly labels instrumented totals, nested boundaries, derived residuals, process-lifetime RSS, and single-thread limitations; it adds no production telemetry.

Port MinishLab/semble a790780's indexing correction and add benchmark-only cold-path phase instrumentation.
Keep source/status timing scoped to production call sites, label instrumented totals and unattributed overhead honestly, aggregate embedding invariants, and cover zero-chunk fresh indexes.
@unicornz-code
unicornz-code merged commit 1579201 into main Sep 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant