feat: Cleaning - #87
Merged
Merged
Conversation
Two stacked campaigns over the non-critical surfaces. Anti-slop lint campaign (waves I/J/K + shape): 849 -> 366 findings; ledger docs/anti-slop-curiosities.md; system core freeze intact. Contract-change alignment sweep: 271 authority claims audited across six lanes (vocabulary, boundary, flow, state, policy, proof), 16 remediation clusters, unresolved = 0. Ledger docs/contract-change-ledger.md carries per-iteration instruments, collision re-scans, and every flagged owner decision. Highlights: shared JSON + lane-receipt vocabulary in _assertions; verification harnesses driven through the production engine adapter; producer-owned ProjectManifest (dead snake/camel tolerance removed); session publication exclusivity + ExtractionSession.close(); one owner each for the commit/lock wire contracts (EPERM=alive); engine-transform extension-gate unification (.mjs divergence fixed); fail-loud parse policy for internal wires; C-016 loader seam (no-module-mocking now 0); hygiene live-gate gitignore-vacuity fix; build graph de-duplication (toolchain gate + double-writer race); withAnimus type portability (TS2742) repairing the next-app/next16-app lanes. Ratchet: .abstraction-owners.json (16 canonical names, exceptions calibrated non-vacuous) + .collision-report.json (hooks remain OFF; enabling is an owner decision). Verification: compile/types/canary/unit-ts(1808)/unit-rust/clippy/ workers/hygiene:rust/parity(65/65, baselines untouched)/integration plus 7 consumer owner lanes green. Known reds: verify:lint (standing 366 anti-slop debt) and verify:packed (environmental next 15.5.23 vs @types/react 18 drift; instrument unchanged — see ledger closeout). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two follow-up chips from the contract-change campaign: - parseFilesJson now decodes through parseInternalWire, naming the wire, reader, and cause on malformed JSON (recorded contract reversal: the bare-SyntaxError pin asserted the asymmetry itself) - storedManifest: any retired in vite-plugin's PluginContext (ProjectManifest | null); the three dependent local manifest models plus a fourth private re-model deleted (net -93 lines); dead partial-manifest guards removed with impossibility arguments; test fakes completed via a local makeManifest/makeComponent fixture Proven: compile 0; vite-plugin 205/205; extract/next/unplugin suites 466 green; integration 165; vite-plugin owner lane (16 tasks) green; tests type-checked clean including the cross-package prerequisite import (0 errors); anti-slop 366 unchanged. Follow-up chip filed: snapshotFilePlans(manifest: any) + run-analysis's sheets guard, kept alive by ~18 next-plugin partial-manifest mocks. Co-Authored-By: Claude Fable 5 <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.
No description provided.