release(0.13.0): bump version + archive add-encoding-partition change - #108
Merged
Conversation
Tags the polygram release that ships add-encoding-partition Phase 1 (#107) and archives the now-completed openspec change directory. Wave C unblocker: this release locks the API surface (BlockSpec, CompressionConfig.encoding_partition, CompressionReport.blocks, from_sae_lens kwarg) that sae-forge's add-block-structured-sae proposal explicitly cites as its Phase 0 prerequisite. Once this tag publishes, sae-forge can bump its polygram>=0.13.0 pin and begin Phase 2 of its own change. Phase 2 (the actual per-block dispatch in Compressor.apply) is a separate impl follow-up filed against this proposal — not in 0.13.0. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tags the polygram release that ships
add-encoding-partitionPhase 1 (#107) and archives the now-completed openspec change directory.What ships in 0.13.0
BlockSpec+ per-family validator registry + custom__hash__.PartitionCoverageError+validate_partition_coverage(disjointness + completeness; names up to 10 offending ids).make_default_block(...)convenience constructor.CompressionConfig.encoding_partition: tuple[BlockSpec, ...] | Nonefield.CompressionReport.blocks: tuple[BlockReport, ...] | None+ newBlockReportdataclass. Schema bump v2 → v3 with back-compat loader.from_sae_lens(..., encoding_partition=...)kwarg accepted + type-validated.Compressor.applyraisesNotImplementedErrorwith an actionable pointer when a partitioned config is supplied (Phase 2 deferral).polygram.compression:BlockSpec,BlockReport,PartitionCoverageError,make_default_block,validate_partition_coverage.33 new tests; full suite 1037 → 1070. Ruff clean. CI green on both 3.11 and 3.12.
Wave C unblocker
This release locks the API surface that sae-forge's
add-block-structured-saePhase 0 explicitly cites as its prerequisite. After this tag publishes:polygram>=0.13.0.add-block-structured-sae's Phase 0.1 task clears.auto_materialise.py,sweep.py,forge.py) can begin against the locked surface.Phase 2 follow-up (separate change, not in 0.13.0)
The actual per-block dispatch in
Compressor.apply— sliceW_dec/W_enc/b_encper block, run compress-strategy pipeline per sub-state, stitch results back into a single output SAE, aggregate per-block diagnostics into the top-levelCompressionReport.blocks. ~150 LOC + per-block smoke matrix tests.Test plan
polygram.__version__ == '0.13.0').v0.13.0tag push (verified post-merge).🤖 Generated with Claude Code