release v0.7.0: post-merge polish + archive MPS changes - #49
Merged
Conversation
Bumps version 0.6.0 → 0.7.0 and lands the post-merge documentation sync after PR #46 (`add-mps-concept-encoding`) and PR #48 (`fix-mps-encoding-non-factorizing`). - README: move MPS concept encoding (rung 1) from "Near-term — implementation pending" into "Recently shipped" with PR refs and the cross-coupled-by-sum encoding formula. - CHANGELOG: convert "Unreleased" → "0.7.0 (2026-05-01)"; correct the stale tier values (`super-group-sibling [0.47, 0.54]` → `{0.335, 0.593, 0.753}`, `cross-group [0.12, 0.25]` → `[0.000, 0.178]`) and the encoding (single-bound-param → cross-coupled-by- sum) in the hierarchical-polysemy entry; add Changed entry for the generalized angle parser; add Fixed entry for `fix-mps-encoding-non-factorizing` referencing PR #48 and tech- debt §5.7. - Research doc: link the rung-1 entry in `docs/research/polysemantic-encoding-beyond-product-states.md` to the merged PRs (#46 + #48) and the post-mortem in `add-mps-concept-encoding/design.md`. - OpenSpec: archive `add-mps-concept-encoding` (25/26 — task 4.2 superseded by `fix-mps-encoding-non-factorizing`) and `fix-mps-encoding-non-factorizing` (✓ Complete) under `openspec/changes/archive/2026-05-02-…`. Both updates flow through to `openspec/specs/{compiler,language}/spec.md`. - Tech debt: append §5.8–§5.15 from a post-merge self-review of PR #48 (HIGH: scientific-notation regression in `_split_linear_combination`; MEDIUM: error-message drift, etc.). Note: the demo-smoke step in `verify-examples.yml` is split out of this commit (PAT lacks workflow scope) — to be added via the GitHub UI as a follow-up. Co-Authored-By: Claude Opus 4.7 <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
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
{0.335, 0.593, 0.753}, cross-group[0.000, 0.178]) and the cross-coupled-by-sum encoding formula in the hierarchical-polysemy entry; add Fixed entry forfix-mps-encoding-non-factorizingreferencing PR fix-mps-encoding-non-factorizing: §1-§8 implementation #48.docs/research/polysemantic-encoding-beyond-product-states.mdrung-1 entry to merged PRs.add-mps-concept-encodingandfix-mps-encoding-non-factorizingunderopenspec/changes/archive/2026-05-02-…; spec deltas flow through toopenspec/specs/{compiler,language}/spec.md._split_linear_combination; MEDIUM: error-message drift, etc.).Out of scope (follow-up)
demos/larql_polysemantic_hierarchical/demo.pyend-to-end (.github/workflows/verify-examples.yml) — split out of this PR because the local PAT lacksworkflowscope. Will be added via the GitHub UI in a separate one-line edit.benchmarks/mps/scaffold, SAE-pattern validation against arXiv 2209.10652 / 2309.08600) — substantial enough to warrant its own OpenSpec changemps-rung-1-validation. To be drafted after this PR lands.Test plan
tech-debt-backlogfailure is a pre-existing issue: that change has no spec deltas because it's a meta tracking doc, not a feature change)🤖 Generated with Claude Code