Changelog
[Unreleased] Latest
Added
- LSP workspace folders (
workspace.workspaceFolders+workspace/didChangeWorkspaceFolders): the session records the folder set it serves — seeded from the client’s initialize folder list (the deprecatedrootUrias the fallback) and re-derived on change events (known removals drop, unknown removals skip, re-adds keep their first recording) — and answers which recorded folders contain a path, the scoping primitive per-folder work slots into. Folders are session metadata keyed by the spelled path; a folder whose URI does not resolve to a file path is skipped, never invented. - LSP document color (
textDocument/documentColor+textDocument/colorPresentation): every string literal that spells a hex color payload (#RGB,#RGBA,#RRGGBB,#RRGGBBAA) answers as the swatch site an editor renders inline (the payload extent, quotes excluded), and the picker’s recolor echo answers the canonical lowercase hex spelling over the reported extent — one notation, one presentation. The capability walks the stored parse trees, so it works on broken code; a presentation over a range no site occupies is never offered. - LSP document links (
textDocument/documentLink): the string literals of the file-taking builtin macros (include!,include_str!,include_bytes!) become clickable file links, resolved against the containing document’s directory (absolute literals as-is). Non-file macros and non-literal arguments answer no link; the capability walks the stored parse trees, so it works on broken code. - LSP linked editing ranges (
textDocument/linkedEditingRange): same-scope occurrences of the cursor’s symbol answer as one edit group for multi-cursor editing, composing the document-highlight occurrence seam (the reference graph’s T129 scope-owner filter included).
Fixed
- Site getting-started tutorial (en/fr) now states the real MSRV (1.95,
matching
Cargo.tomland the CImsrvjob) instead of the stale 1.94/1.85 pair. - README + site language reference (en/fr) now list every registered
builtin macro (
format!,vec!,matches!, theassert!family,write!/writeln!) and note the stdlib’s declarativeprintln!/print!/eprintln!/eprint!/panic!. - Site crate reference (en/fr) now covers the
tools/harnesses (glyim-ledger, glyim-bench, glyim-metrics, glyim-pilot, ledger-schema). glyim-lspno longer silently swallows rejected analysis sends and publish-diagnostics notifications: both surface atracing::warnnaming the affected file.
[0.10.0]
Added
-
**
inventory ignore/inventory unignore(glyim-ledger inventory ignore [ROOT] --item <KEY> --reason <TEXT> [--format text|json]/glyim-ledger inventory unignore [ROOT] --item <KEY> [--format text|json])**: the §3.5 exemption-lifecycle write faces —ledger/inventory-ignore.tomlwas the last hand-edited registry the §3.5 gate reads: the check fails withLEDGER-INVENTORY-UNMAPPEDwhen an extracted item is neither claimed nor ignored, but until these faces filing the demanded exemption (or retiring one once the item gains a claiming feature) meant hand-editing the curated TOML file.inventory ignorefiles one[[ignore]]block through the newIgnoreSinkseam (FileIgnoreSink/InMemoryIgnoreSink): the key must be produced by an extractor *right now* (exact keys, never globs — a pre-registered phantom exemption would silently swallow future drift), must not be claimed by a feature (claimed-and-ignored is theLEDGER-INVENTORY-CONFLICTfailure), and must not already be ignored;inventory unignoreremoves exactly the one matching block through the newIgnoreRewriterseam (FileIgnoreRewriter/InMemoryIgnoreRewriter), rewriting the remaining entries canonically — the item is unmapped again the moment the rewrite lands, and the §3.5 gate is the loud follow-up that forces a feature claim. Both faces refuse a tree that does not load cleanly and never leave a partial write behind, emit theglyim.ledger-inventory-ignore/1/glyim.ledger-inventory-unignore/1JSON contracts with–format json, and carry typedLedgerCliErrorvariants withhelp()remedy lines (InventoryIgnoreBadItem,InventoryIgnoreMissingField,InventoryIgnoreLoad,InventoryIgnoreUnknownItem,InventoryIgnoreClaimed,InventoryIgnoreDuplicate,InventoryIgnoreWrite,InventoryUnignoreBadItem,InventoryUnignoreLoad,InventoryUnignoreMissingField,InventoryUnignoreUnknownItem,InventoryUnignoreWrite); the consumer walkthrough iscargo run -p glyim-ledger –example inventory_ignore_lifecycleand the bench iscargo bench -p glyim-ledger –bench inventory_ignore`. -
**
gaps unwitness(glyim-ledger gaps unwitness [ROOT] --id <GAP-ID> [--format text|json])**: the remedy half of the gap trust loop — detaches one witnessed gap's witness, restoring honest witness debt. The audit face'smissingverdict is the finding (the registry claims a fixture the tree no longer carries); until this face the remedy did not exist as a sanctioned command — the witness face refuses an already-witnessed gap, so fixing a stale or wrong witness path (a fixture moved, renamed, or deleted aftergaps witnessattached it) meant hand-editing the curated TOML block. The newGapWitnessDetacherseam has two implementations —FileGapWitnessDetacher(reads, edits the matched block, replaces the registry file) andInMemoryGapWitnessDetacher(tests and in-process consumers, with the detach edits recorded for the audit). The detachers are deliberately *surgical* like the witness face they invert: only the matched[[gap]]block'sstatusvalue flips back tounwitnessedand the alignedwitnessline is removed (the detached path retires to the git history of the registry, the retire-face contract), so the curated header prose survives byte-for-byte —gaps witnessfollowed bygaps unwitnessround-trips the registry bytes.run_gaps_unwitnessvalidates the request — a usable ID, a registry that loads with zero error-severity diagnostics (the witness-face load rule), and a gap that actually carries a witness (an unwitnessed gap has nothing to detach; the remedy never mints a silent no-op) — and never leaves a partial write behind. The dispatch layer refreshes the generatedKNOWN_GAPS.mdin the same run through therender-gapspipeline, so the–checkdrift gate stays green. 6 new typedLedgerCliErrorvariants (GapsUnwitnessMissingField,GapsUnwitnessBadId,GapsUnwitnessUnknownId,GapsUnwitnessNotWitnessed,GapsUnwitnessRegistry,GapsUnwitnessWrite) plus the sharedGapsMissingValue, all carrying theircode()/help()lines. Ships thegaps_unwitnesswalkthrough, thegaps` bench stage, and README/lib.rs/main.rs/usage docs. -
**
gaps audit(glyim-ledger gaps audit [ROOT] [--format text|json])**: the trust-loop closure over the gap-lifecycle write faces — resolves every registered gap's witness fixture against the tree, one row per gap sorted by ID. Thegaps witnessface checks the fixture at attach time, but nothing re-verified the registry against the tree afterwards: a fixture that is moved, renamed, or deleted left the registry claiming a witness that no longer exists — exactly the silent debt plan §3.3 forbids, invisible to every existing face (checkvalidates registry consistency, thegapsreport prints the recorded path without probing the tree). The newaudit_gapsverdict pass classifies each gap —witnessed(the fixture resolves to a readable regular file under ROOT),debt(honest unwitnessed debt — displayed, never failed, the gaps-report rule),missing(a registry-claimed witness the tree no longer carries, including the barestatus = “witnessed”block that carries nowitnessline at all — the serde default makes that a silent claim), andunreadable(the witness path resolves to something that is not a readable regular file).run_gaps_auditloads the registry once, reports the same sorted diagnostics thegapsreport face would, andis_ok()fails the gate on anymissing/unreadablerow or error-severity diagnostic — the same finding gateevidence auditruns over the evidence store, applied to the witness paths the write faces record. Theglyim.ledger-gaps-audit/1JSON contract carries the counts and the full row list; the text face prints the summary line, every non-passing row with its detail (the vanished path), the witness-debt reminder, and the diagnostics. Ships thegaps_auditwalkthrough, thegaps` bench stage, and README/lib.rs/main.rs/usage docs. -
**
evidence retract(glyim-ledger evidence retract [ROOT] --fixture <PATH> [--out PATH] [--format text|json])**: the evidence-store curation removal face — removes every committed record whosefixture_sha256matches the recomputed digest of one fixture. The audit face'sDriftverdict is the finding (a record that predates a fixture edit no longer describes the tree); until this face the remedy was hand-editing the canonical JSONL store. The engine reuses two seams —FixtureFingerprint(the digest is recomputed from the real fixture bytes, the same spelling the audit face compares) andEvidenceStore(the rewrite persists the canonical remainder, so the surviving records stay byte-deterministic).run_evidence_retractvalidates the request — a relative,..-free, backslash-free fixture path naming an existing file under ROOT (the fingerprint needs the fixture's bytes; a phantom fixture would silently retract nothing), a store that loads with zero error-severity diagnostics (a corrupt line would be silently destroyed by the rewrite otherwise — the waiver-face load rule), and at least one matching record (a fixture with nothing committed is a rejection naming the digest, not a silent no-op). Nothing is written when validation fails; the persist failure reuses the record face's typedEvidenceWriteseam. The dispatch layer routes every rejection through the typed error seam. 6 new typedLedgerCliErrorvariants (EvidenceRetractMissingField,EvidenceRetractBadFixture,EvidenceRetractMissingFixture,EvidenceRetractFingerprint,EvidenceRetractLoad,EvidenceRetractUnknownFixture), all carrying theircode()/help()lines. Ships theevidence_retractwalkthrough, theevidence` bench stage, and README/lib.rs/main.rs/usage docs. -
**
gaps open(glyim-ledger gaps open [ROOT] --id <GAP-NNNN> --class <a|b|c> --title <TEXT> --affects <ID[,ID...]> --caps <L0..L5> --opened-in <TAG> [--file ledger/gaps/.../FILE.toml] [--format text|json])**: the opening stage of the gap-lifecycle write face — files a NEW gap entry into the registry. Until this face the witness and retire stages had sanctioned commands, but opening a gap meant hand-writing the curated TOML block and remembering the aligned registry style, the explicitstatus = “unwitnessed”line, and the regenerate-KNOWN_GAPS.mdstep. The newGapOpenerseam has two implementations —FileGapOpener(reads, appends, replaces the registry file; a missing file is an empty document, so the default numbered target is minted on first open) andInMemoryGapOpener(tests and in-process consumers, with the appends recorded for the audit). The engine renders the canonical block in the committed registry style (keys padded to theopened_incolumn) and appends it after one blank separator, so the curated header prose and every sibling block survive byte-for-byte; the block always carries the explicitstatus = “unwitnessed”line because the serde default for a missingstatuskey iswitnessed— an omitted line would mint silent debt, which plan §3.3 forbids.run_gaps_openvalidates the request against the loaded registry — the canonicalGAP-NNNNshape (the face mints IDs, so four digits is enforced, not just matched), a usable one-line title andopened_in, every–affectsfeature present in the registry (a gap that limits nothing real is silent debt), the ID free (an open gap is never silently shadowed), and a relative, existing.tomlpath underledger/gaps/when–filenames one; without–filethe next numberedledger/gaps/known/NNNN-gaps-open.tomlis minted (a pure function of the tree). A registry that does not load cleanly is never extended. The dispatch layer refreshes the generatedKNOWN_GAPS.mdin the same run through therender-gapspipeline, so the–checkdrift gate stays green. 11 new typedLedgerCliErrorvariants (GapsOpenMissingField,GapsOpenBadId,GapsOpenBadClass,GapsOpenBadCaps,GapsOpenBadTitle,GapsOpenBadOpenedIn,GapsOpenBadFile,GapsOpenAffectsUnknown,GapsOpenDuplicateId,GapsOpenRegistry,GapsOpenWrite), all carrying theircode()/help()lines. Ships thegaps_openwalkthrough, thegaps` bench stage, and README/lib.rs/main.rs/usage docs. -
gaps witness(glyim-ledger gaps witness [ROOT] --id <GAP-ID> --witness <PATH>): the gap-lifecycle write face — attaches the witness fixture that reproduces one unwitnessed gap, closing the witness debt the plan §3.3 report prints and thenextqueue ranks. The newGapWitnessRewriterseam has two implementations —FileGapWitnessRewriter(edits the registry file exactly where the loaded registry says the block lives) andInMemoryGapWitnessRewriter(tests and in-process consumers, with the edits recorded for the audit). The rewriters are deliberately surgical rather than canonical: only the matched[[gap]]block’sstatusvalue flips and the alignedwitnessline is appended, so the curated header prose of the committed seed files survives byte-for-byte (the opposite tradeoff to the waiver faces, whose machine-written document is canonically re-serialized).run_gaps_witnessvalidates the request against the registry and the tree — a relative,..-free, backslash-free path naming an existing fixture (a phantom witness would trade visible debt for silent debt) — refuses a registry that does not load cleanly, and never silently re-witnesses an already-witnessed gap. The dispatch layer refreshes the generatedKNOWN_GAPS.mdin the same run through therender-gapspipeline, so the--checkdrift gate stays green. 8 new typedLedgerCliErrorvariants (GapsWitnessMissingField,GapsWitnessBadId,GapsWitnessBadWitness,GapsWitnessUnknownId,GapsWitnessRegistry,GapsWitnessAlreadyWitnessed,GapsWitnessMissingFixture,GapsWitnessWrite, plus the sharedGapsBadFormat), all carrying theircode()/help()lines. Ships thegaps_witnesswalkthrough, thegapsbench stage, and README/lib.rs/main.rs/usage docs. -
gaps retire(glyim-ledger gaps retire [ROOT] --id <GAP-ID>): the closure half of the gap lifecycle — removes one gap’s[[gap]]block from its registry file entirely. The renderedKNOWN_GAPS.mdstates that closed entries retire to the git history of the file and of the registry; until this face the removal itself had no sanctioned command. The newGapRetirerseam has two implementations —FileGapRetirer(drops exactly the matched block’s lines, swallowing the block’s trailing separator when another block follows) andInMemoryGapRetirer(tests and in-process consumers, with the removals recorded for the audit).run_gaps_retirevalidates the ID, refuses a registry that does not load cleanly (the revoke-face load rule), and reports the remaining open-gap count through theglyim.ledger-gaps-retire/1JSON contract and the text face. The dispatch layer refreshes the generatedKNOWN_GAPS.mdin the same run. 5 new typedLedgerCliErrorvariants (GapsRetireMissingField/GapsRetireBadId/GapsRetireUnknownId/GapsRetireLoad/GapsRetireWrite), all carrying theircode()/help()lines. Ships thegaps_retirewalkthrough, the retire bench stage, and README/lib.rs/main.rs/usage docs. -
French documentation (i18n): the
glyim-docssite ships a complete French translation of 19 content pages underdocs/src/content/docs/fr/. -
waivers prune(glyim-ledger waivers prune): retires every expired C9 exception in one call — the batch counterpart ofwaivers revoke(one exact ID at a time) for the moment an operator clears the whole expired-inventory debt. The newWaiverPrunerseam (the many-expired counterpart ofWaiverRewriter) has two implementations —FileWaiverPruner(parses the committed document, partitions the entries by expiry, re-serializes the remaining entries canonically, and replaces the file; a non-clean document is refused, never truncated) andInMemoryWaiverPruner(tests and in-process consumers, with the pruned IDs recorded for the audit).run_waivers_prunevalidates the document (zero error-severity load diagnostics), and a document with no expired waiver is never rewritten — the seam is not invoked and the file bytes stay untouched. The outcome rows report ID order regardless of the document’s construction path (theassess_waiverscontract) through theglyim.ledger-waivers-prune/1JSON contract and the text face. 2 new typedLedgerCliErrorvariants (WaiversPruneLoad/WaiversPruneWrite), both carrying theircode()/help()lines. Ships thewaivers_prunewalkthrough, the prune bench stage, and README/lib.rs/main.rs/usage docs. -
release-check(glyim-ledger release-check <VERSION> [ROOT]): the plan §10 final release gate — the master plan names the face in the CLI table (“ledger release-check vX.Y.Z— Final release gate”), defines its contract in the release-criteria section (“passes iff all 24 readiness gates are green on the release commit, evidence is reproducible (RG-04/17), and no waiver is active”), and requires it at M12.7, but no command composed the three shipped verdict axes into the one verdict a release commit needs. The newReleaseCheckSourceseam (the composition counterpart ofHandoffSource) has two implementations —FileReleaseCheckSource(runs the real M1.12 gate report, M1.13 determinism self-check, and C9 waiver health over the registry, through the same executors those faces use, so a release verdict can never disagree with an individual face run) andInMemoryReleaseCheckSource(tests and in-process consumers) — and theReleaseCheckRendererseam (theWaiversRendererpattern) renders the text report and theglyim.ledger-release-check/1JSON contract from oneReleaseCheckOutcome. The gate isis_ok, clause by clause the plan sentence: every declared gate green — afailblocks and anunmeasuredverdict blocks too (plan M1.12: displayed, never silently passed — the blocking list names them in declaration order), the self-check reports no drift, no waiver is active or expired (the C9 health contract keeps the release gate from ever being greener than the faces it composes), and no error-severity diagnostic across the composed faces (warnings display, not fail). The<VERSION>argument is validated at parse time (vMAJOR.MINOR.PATCH,voptional; no pre-release tags or build metadata — a release gate gates a plain triple) and the verdict names it in both faces. 4 new typedLedgerCliErrorvariants (ReleaseCheck*), all carrying theircode()/help()lines. Ships therelease_checkwalkthrough, the release bench stage, and README/lib.rs/main.rs/usage docs. -
waivers extend(glyim-ledger waivers extend): re-pins one C9 exception’s expiry totoday + --days(default 7, horizon 14) — the sanctioned counterpart theWaiversGrantDuplicatehelp line already points to. The newWaiverExtenderseam (the mutation counterpart ofWaiverRewriter) has two implementations —FileWaiverExtenderandInMemoryWaiverExtender— and the identity (ID, feature, reason, issue) is never rewritten; only the expiry moves. 6 new typedLedgerCliErrorvariants (WaiversExtend*), all carrying theircode()/help()lines. Ships thewaivers_extendwalkthrough, the extend bench stage, and README/lib.rs/main.rs/usage docs. -
evidence audit(glyim-ledger evidence audit): audits the committed store against the filesystem — recomputes every record’sfixture_sha256from the fixture bytes and reportsok/missing/drift/unreadableverdicts; any finding fails the exit code (the trust-loop closureevidence checkcannot express). The newFixtureFingerprintseam has two implementations —FileFixtureFingerprint(sha2 over the raw bytes) andInMemoryFixtureFingerprint(precomputed digests). Ships theevidence_auditwalkthrough, the audit bench stage, and README/lib.rs/main.rs/usage docs. -
C9 waiver-retirement face (
glyim-ledger waivers revoke):waivers grantis append-only by design — once a waiver’s regression fix landed (or its horizon expired and the C9 gate started failing CI), the only way to retire the entry was hand-editingledger/waivers.toml, bypassing the canonical-ID and canonical-serialization discipline every other face enforces. The newWaiverRewriterseam (the rewrite counterpart ofWaiverSink) has two implementations —FileWaiverRewriter(parses the committed document, drops the one exact-ID match, re-serializes the remaining entries canonically, and replaces the file; a document that fails to parse is refused, never truncated) andInMemoryWaiverRewriter(tests and in-process consumers, with the removal recorded for the audit).run_waivers_revokevalidates the request (usable ID; the committed document must load with zero error-severity diagnostics — a duplicate-ID file fails here; the ID must be present, and an unknown ID writes nothing and names a few existing candidates), removes exactly one block, and reports the remaining count through theglyim.ledger-waivers-revoke/1JSON contract and the one-line text face. Five new typedLedgerCliErrorvariants (WaiversRevokeMissingField/WaiversRevokeBadIdfor the parser;WaiversRevokeUnknownId/WaiversRevokeLoad/WaiversRevokeWritefor the write face), all carrying theircode()/help()lines. -
§3.7 session-handoff face (
glyim-ledger handoff): the master plan’s CLI table names aledger handoffface (“generates the (short) session handoff from state”) that did not exist — composing the readiness state into one session-opening read meant running four commands (compute,next,waivers,gaps) and merging them by hand. The newHandoffSourceseam (the composition counterpart ofWaiverSource) has two implementations —FileHandoffSource(runs the real compute,next, and waiver-health faces over the registry, through the same loaders those faces use, so a handoff can never disagree with them) andInMemoryHandoffSource(tests and in-process consumers) — and theHandoffRendererseam (theWaiversRendererpattern) renders the marker-delimited Markdown document face and theglyim.ledger-handoff/1JSON contract from oneHandoffOutcome. The document is short by contract: the readiness histogram (features, evidence records, L0–L5 counts, error diagnostics), the top-N work queue (--items N, default 5, max 20 — ranks stay honest so a slice still shows where items stand in the full queue), waiver health with the next expiring waiver, and the witness debt. The gate isHandoffOutcome::is_ok: zero error-severity diagnostics across the three composed faces and no expired waiver (constitution C9) — the debt is rendered, never silent, and the exit code fails exactly as the composed faces would.--out PATHwrites the rendered document (defaultHANDOFF.md/HANDOFF.jsonby face) and--checkbyte-compares the committed document against the composed state (the M1.10 drift-gate contract, mirrored from thestatusface; a committedHANDOFF.mdis not yet wired into CI — wire the job once the face settles). Five new typedLedgerCliErrorvariants (HandoffBadFormat/HandoffMissingValue/HandoffBadItemsfor the parser;HandoffDrift/HandoffWritefor the write/check face), all carrying theircode()/help()lines. The engine sorts the queue by rank before slicing (input order never leaks into the render) and pinstodayon the waivers outcome (no second clock consult). -
C9 waiver-health face (
glyim-ledger waivers) + curated grant write face (glyim-ledger waivers grant):ledger/waivers.tomlwas read only inside thediffregression gate — an expired or horizon-violating waiver stayed invisible until a regression actually needed covering, and there was no way to inspect the live exception inventory at all, so the C9 sentence “expired waivers fail CI” was not directly checkable. The newWaiverSourceseam (the load counterpart ofSnapshotStore/EvidenceSource) has two implementations —FileWaiverSource(reads<ROOT>/ledger/waivers.tomlthrough the sameload_waiversloader and diagnostic codes thediffgate uses, so the two faces can never disagree) andInMemoryWaiverSource(tests and in-process consumers) — and theWaiversRendererseam (theKnownGapsRendererpattern) renders the text report and theglyim.ledger-waivers/1JSON contract from oneWaiversOutcome. The gate isWaiversOutcome::is_ok: no error-severity load diagnostic (schema, duplicate ID, horizon violation) and no row whose verdict isExpired; a waiver inside its horizon is report content (the remaining-days column is the operator’s reminder), never a failure.waivers grantis the write counterpart: it validates the request against the registry (--featuremust name a declared feature,--issuemust be anhttps://link,--reasonmust be usable,--daysmust stay insideWAIVER_MAX_AGE_DAYS, CLI default 7), composes the deterministicWVR-<YYYYMMDD>-<feature slug>ID, and appends the canonical[[waiver]]block through theWaiverSinkseam (FileWaiverSinkappends to the committed document with newline-normalization,InMemoryWaiverSinkrecords the fragment for tests; thetomlcrate escapes, never hand-quoting). A same-day re-grant is a duplicate error, never a silent overwrite, and nothing is written when validation fails. Eight new typedLedgerCliErrorvariants (WaiversBadFormat/WaiversMissingValuefor the health face;WaiversGrantMissingField/WaiversGrantBadDays/WaiversGrantBadIssue/WaiversGrantUnknownFeature/WaiversGrantRegistry/WaiversGrantDuplicate/WaiversGrantWritefor the grant face), each with itshelp:remedy line. Ships thewaiver_healthandwaivers_grantwalkthroughs (the grant walkthrough writes into a throwaway registry, never the live one), thewaiversbench (assess + both faces + the grant validation path over a 500-waiver set), and README/lib.rs/main.rs/usage docs.
Added
- Goto declaration (
textDocument/declaration): the missing member of the goto family — goto-definition answers the definition (the item, wherever it lives), but nothing answered “where is this name declared for this file”. The newgoto_declarationengine resolves the cursor’s identifier through aDeclarationSourceseam: ausestatement binding the name declares it (the import wins over a same-named local item — that is what the user wrote to bring the name into scope), a locally-declared item declares itself, and a name that is neither imported nor declared in the file answersnullhonestly instead of masquerading as a second definition request. The productionParseTreeDeclarationSourcewalks the parse trees the analysis driver already stores (db.syntaxes) — glob (use foo::*) and_aliases bind no single name and are skipped — so no re-analysis happens on the request path and broken files still answer. Ships the policy tests over a mock source, the database-backed request tests, thegoto_declarationbench, and thegoto_declaration_walkthroughexample. - Server log file (
glyim-lsp --log-file X): the flag was parsed and documented (“tee tracing to X”) butrun_serveraccepted it as_log_fileand never used it — every tracing event the engines emit (debug!per request,warn!per dropped edit) went nowhere. The newserver_logmodule closes the seam:FileLogopens the target file and implementstracing_subscriber’sMakeWriter(oneMutexwriter, line-buffered),install_globalwires it as the global default subscriber emitting JSON lines, andrun_serverinstalls it when the flag is present — a file that cannot be opened degrades to a one-line stderr note and a server that still runs, because losing the log must never cost the session. Ships the file-log tests (bytes land, events round-trip as JSON) and theserver_log_walkthroughexample. - Inlay hints (
textDocument/inlayHint): inline: Tyannotations on un-annotatedletbindings, resolved from the Tier 6.4 HIR + typeck state through aBindingTypeSourceseam (HirBindingTypeSourceproduction impl), with an honest skip list (annotated bindings, types with no stable user-facing spelling, bindings outside the requested range). Routed, advertised, conformance-pinned, tested over a mock and over the database, benched (inlay_hint), and walked through ininlay_hint_walkthrough. - Call hierarchy (
textDocument/prepareCallHierarchy+ incoming and outgoing calls) and signature help (textDocument/signatureHelp): the call-hierarchy requests answer the function item under the cursor and walk the reference graph’s call records for callers and callees; signature help resolves the innermost recorded call containing the cursor and renders the callee’s signature with the active parameter counted from the source text. Both read the same reference graph and symbol index the other request engines use (seamsCallGraphSource/CallSiteSource/SignatureSource), are routed, advertised, conformance-pinned, tested over mocks and the database, benched, and walked through in dedicated examples.
Fixed
-
glyipno longer silently swallows a corruptGlyip.lock:resolve_lockfileread the lockfile withLockfile::read_from_dir(...).unwrap_or_default(), which conflated “no lockfile yet” (fine —read_from_diralready answers an empty one) with “a resolution record that cannot be parsed” — the user’s pin record was discarded without a trace and re-resolved as if it had never existed. The read error now propagates, and a regression test pins the contract (crates/glyip/src/tests/lockfile_advanced.rs). -
STATUS.md/STATUS.jsonwere committed stale after the ledger feature registry gained the newer LSP capability declarations — the committed status said 225 features over 9TOOL-LSP-*rows while the registry carried 233 over 17; theledger-checkCI job’sstatus . --checkbyte-compare would fail on every run. Both are regenerated from the registry (and the two new capability entries,TOOL-LSP-DECLARATIONandTOOL-LSP-LOG-FILE, are declared inledger/features/tooling/lsp.tomlin the same pass). -
Two latent rustc-1.100 clippy breaks (found by the
--all-targets --all-featuresgate):tools/glyim-metrics/examples/ baseline_check.rsprinted a{}placeholder with no argument (no committed baseline at {} — skipped) — a runtime panic on the out-of-repository arm that the newerformat_argsdiagnostic rejects at compile time; the committed-baseline path is now the argument. Andtools/glyim-ledgerbuilt twocloned_ref_to_slice_refssites (theevidence_storewalkthrough and amerge_recordstest) —&[run.clone()]slice literals becamestd::slice::from_ref(&x). -
Evidence-store curation face (plan §3.4 store remainder):
tools/glyim-ledger/src/evidence.rscloses the gap between the M1.5 evidence emitter (glyim-testrecords underGLYIM_TEST_EVIDENCE) and the M1.8 consumer (ledger/evidence/*.jsonldiscovered byProjectEvidenceSource): nothing owned the store those records are committed into, so a harness run reached the ledger only by hand-copying JSONL out oftarget/. The newEvidenceStoreseam (the write counterpart of the read-sideEvidenceSourcetrait) has two implementations —FileEvidenceStore(the committedledger/evidence/*.jsonllayout: one canonicalglyim.evidence/1line per record, missing parent directories created, an absent store file an honest fresh store) andInMemoryEvidenceStore(tests and in-process consumers, same canonicalization contract). Wired asglyim-ledger evidence record [--out PATH] [--format text|json] <SRC...>— validate harness-emitted records against the registry (schema tag, M1.5 record invariants, unknown feature IDs; every rejection is an error diagnostic, nothing invalid reaches the store), merge them with whole-record dedupe into canonical order (merge_records, idempotent and order-insensitive so re-recording the same run is byte-identical;glyim.ledger-evidence-record/1JSON face) — andglyim-ledger evidence check [ROOT]— validate the committed store itself and report its coverage (files, records, duplicates, distinct fixtures, features covered, per-outcome histogram;glyim.ledger-evidence-check/1, error diagnostics fail the exit code, the CI gate face). Four new typedLedgerCliErrorvariants (EvidenceMissingSources/EvidenceMissingValue/EvidenceBadFormat/EvidenceSubcommand) plusEvidenceWritefor the store-persist failure, each with itshelp:remedy line. Ships theevidence_storeexample (curate → idempotence → check, over a synthetic registry or a real root) and the dependency-freeevidencebench (2000-record merge into a 2000-record store, 4000-record check, and the idempotent re-record no-op). The committedledger/evidence/test.jsonlis machine-observed: generated by running the corpus suites withGLYIM_TEST_EVIDENCEand curated through the new record face. -
STATUS drift gate (M1.10 remainder: “STATUS is up to date”):
tools/glyim-ledger/src/status.rslands the slice the M1.9 first slice deliberately deferred (its module doc named the gate “a later slice”):run_status_outrenders a status artifact and either writes it (--out PATH, defaultSTATUS.md/STATUS.jsonby face under ROOT —STATUS_MD_TARGET/STATUS_JSON_TARGET) or, with--check, byte-compares the committed document against the pure(registry, evidence, policy)render and fails with the typedglyim-ledger::status_drifterror (the exact drift-gate contractrender-gaps --checkestablished forKNOWN_GAPS.md; write failures go through the newglyim-ledger::status_write). The committedSTATUS.md/STATUS.jsonare generated from the committed evidence store, so the M1.10 CI gate and the M1.8 engine can never disagree with what a contributor sees. Wired throughparse_status(--out,--check), thestatususage/help text, and themain.rsdispatch (write/check verdicts print, drift fails like a CLI error); pinned by write-face, check-OK, drift, missing-document, explicit-target, and CLI-parse tests. -
Generated KNOWN_GAPS.md (M1.9 remainder):
tools/glyim-ledger/src/render.rscloses the drift class the M1.7 migration left behind — the machine-checked status lives inledger/gaps/known/*.tomlwhileKNOWN_GAPS.mdstayed hand-maintained (its own audit note records one stale revision). The document is now a pure function of the gap registry: theKnownGapsRendererseam has a Markdown face (the committedKNOWN_GAPS.md— provenance header, witness-debt table, one section per open gap sorted by ID) and a JSON face (glyim.known-gaps/1, the readiness page’s future input), both consuming the M1.7GapOutcomeverbatim so the file can never disagree withglyim-ledger gaps. Wired asglyim-ledger render-gaps [ROOT] [--format md|json] [--out PATH] [--check]:--outwrites,--checkbyte-compares the committed document and fails with the typedglyim-ledger::render_drifterror (plan M1.9 DoD: “outputs deterministic (golden)” — pinned by a full golden fixture and repeat-render byte-equality tests).KNOWN_GAPS.mdis regenerated from the registry in this change; the closed-entry history retires to git (the registry holds only open gaps, per the RG-10 verdict’s contract). Ships therender_known_gapsexample and the dependency-freerenderbench (both faces over a 500-gap registry). -
Committed corpora directory (M2.3 remainder):
tools/glyim-bench/src/corpus_dir.rslands the slice the master plan’s M2.3 exit gate calls “corpora committed with hashes” on top of the slice-1 substrate: theCorpusSinkwrite seam,DirCorpusSink(conventionalperf/corpus/layout — one<family>-<seed>-<size>.gfile per program plus theglyim.corpus/1corpus.jsonmanifest),CorpusDirPlanflag parsing (families × seeds × size, default all seven families), andcheck_corpus_dir— which loads the manifest, runs the substrate’s template-verify contract, then re-hashes every committed.gfile, reporting missing/hand-edited programs as gate rows (exit non-zero, the same verdict-not-error shape as the diff and budget gates). Wired asglyim-bench corpus write|check [--dir PATH] [--families LIST] [--seeds LIST] [--size N]with four new typedBenchErrorvariants (CorpusDirRead/CorpusDirWrite/CorpusFileMissing/CorpusFileMismatch), thecorpus_commitexample, and thecorpus_dirbench (28-program write + check). -
Release-gate report (M1.12):
tools/glyim-ledger/src/gates.rsimplements the plan §6 M1.12 exit gate — “Readiness gates RG-01…RG-24 declared inledger/gates.toml;unmeasuredallowed but displayed;ledger gatesprints all 24”. The declaration face is a new strict schema beside the policy loader (tools/ledger-schema/src/gates.rs,glyim.ledger-gates-registry/1,deny_unknown_fields): each[[gate]]row carries the plan’sRG-NNid, title, criterion, and the evidence source the verdict engine may consult today — a closed enum (none/levels/gaps) so a declaration can never claim an input the engine does not have; verdicts have no on-disk field (constitution C1: status is computed, never typed). The engine evaluates every declared gate per source — RG-09 over the M1.8 compute outcome (core/std features below L4, then core below the unmeasurable-L5, reported as fail naming the unmeasured hardening axes), RG-10 over the M1.7 gap registry (open class-b gaps, class-a gaps without a pinned diagnostic, witness debt — the registry holds only open gaps, so every counted entry is open by construction),noneas the honestunmeasured(displayed, never silently passed, never failed by itself: the M1.12 exit gate is “prints all 24”, so the command exits non-zero only on load/validation diagnostics; CI blocking stays with the later RG wiring slices). Wired asglyim-ledger gates [ROOT] [--evidence PATH] [--format text|json]over theglyim.ledger-gates/1contract, with therelease_gatesexample and the dependency-freegatesbench (24 gates over a 500-feature registry + gaps).ledger/gates.tomldeclares all 24 plan gates; on today’s tree the report prints 0 pass, 2 fail (RG-09, RG-10), 22 unmeasured — the honest release state. -
Determinism self-check (M1.13 first slice):
tools/glyim-ledger/src/verify.rsimplements the plan §6 M1.13 “runcomputetwice → identical bytes” half as a command:verify_determinismruns every ledger pipeline — compute (text/JSON/snapshot document), status (Markdown), and the M1.12 gates report (text/JSON) — twice, from two independent load passes over the same root, and compares the rendered bytes per check (fixedCHECK_NAMESorder; the order is part of theglyim.ledger-verify/1contract). Unlike thegatesreport,verifyis a gate: a drifted check or an error-severity diagnostic fails the command (exit 1), so CI can wire it directly. The checker reuses the executors verbatim and adds no IO boundary, so future evidence sources participate automatically; the two-machine comparison (committed golden + CI job) is deliberately left to the later M1.13 slices. Wired asglyim-ledger verify [ROOT] [--evidence PATH] [--format text|json], with theverify_determinismexample and the dependency-freeverifybench (6 double-run checks over the 500-feature synthetic registry). -
Matrix gate with the geo-mean aggregate budget (M2.5 remainder):
tools/glyim-bench/src/matrix.rsimplements the plan §325 / §6 M2.5 perf-compare criterion — “fail >2% on a benchmark or >0.5% geo-mean” — the aggregate clause no existing gate could express: a change that slows every benchmark by +1% passes each per-benchmark budget and is caught only by the matrix. TheBaselineSourcetrait (HistoryBaselineSourceselects the latest recorded run of each program from aHistoryStore, lazily cached;InMemoryBaselineSourcebacks tests) keeps the engine IO-free and lets the baseline layout evolve;diff_matrixreuses the unchanged M2.5diff_reportsengine per row (rows in input order, no clock, plan C6), andexecute_diff_matrixwires theReportStore+BaselineSourceseams. The instruction geo-mean is measured only when every row carried instructions (the budget gate’s honesty rule: a geo-mean over a subset is not coverage). Wired asglyim-bench matrix --history PATH [--max-delta-pct] [--max-geo-delta-pct] REPORT...over theglyim.bench-matrix/1outcome, with thematrix_gateexample and the dependency-freematrix_enginebench (8 programs × 256 history records). A missing baseline is now a typedBenchError::BaselineUnavailablewith a remedy-naming help line (previously the misleadingInvalidPlanwhose help talked about--iterations). -
History trend analyzer (M2.5 complement):
tools/glyim-bench/src/trend.rsmeasures the total drift across the last N recorded runs of one program (glyim.bench-trend/1) — the accumulated multi-PR regression the latest-baseline diff can never see, because every individual PR stayed within its own budget while the window ratchets +1% per run.trend_over_historyis the pure engine (append-order window, first-to-last drift, the diff engine’s degenerate zero-first-mean rule),execute_trend_from_historywires theHistoryStoreseam, and the instruction drift is measured only when every window point carried instructions. Wired asglyim-bench history trend --history PATH --program P [--window N] [--max-drift-pct], with thehistory_trendexample and thetrend_enginebench (256 records × 2 programs, window 32). -
Perf-history store (M2.5 first slice):
tools/glyim-bench/src/history.rsimplements the plan’sperf/history/*.jsonlseam — the committed memory the M2.5 diff gate diffs against. TheHistoryStoretrait (JsonlHistoryStoreappends one self-describingglyim.bench-history/1record per line and loads a missing file as an empty history;InMemoryHistoryStorebacks tests) is path-agnostic (program_slugderives the conventional per-benchmark filename),latest_baselineis the pure selection — the last record measuring the program, file order = append order, no clock (plan C6) — andexecute_diff_from_historywires the stores into the unchanged M2.5 diff engine (baseline_pathnames the history file with the#latestselector). Wired asglyim-bench history record|show|diff, with thehistory_baselineexample and the dependency-freehistory_storebench. -
Absolute budget gate (M2.6 first slice):
tools/glyim-bench/src/budget.rsimplements the plan’s budgets seam — constitution C7’s absolute half (“budgets are tests”): a committedglyim.bench-budgets/1TOML document (perf/budgets.toml, one[[budget]]row per program withmax_wall_mean_ns/max_instructions_meanbounds) is enforced against writtenglyim.bench/1reports. Split exactly like the M2.5 diff slice: theBudgetStoretrait (FileBudgetStoreon disk,InMemoryBudgetStorefor tests) abstracts where the budgets come from,check_budgetsis the pure(reports, budgets) → verdictsengine, andexecute_budgetwires both stores. Verdicts extend the M2.2 gate’s inclusive<=boundary with two honesty rules: a bound on a metric the report does not carry isUnmeasured(a wall-only run cannot silently satisfy an instruction budget), and a program with no budget row fails outright — a benchmark that never declared a budget cannot be “within” one. Renderers are the deterministic text table and theglyim.bench-budget/1JSON contract; wired asglyim-bench budget [--budgets perf/budgets.toml] [--json OUT] REPORT..., with thebudget_checkexample and the dependency-freebudget_enginebench. -
Readiness-regression gate (M1.10 first slice):
tools/glyim-ledger/src/diff.rsimplements the plan’sledger diff— a per-feature level diff between twoglyim.ledger-snapshot/1snapshot documents (produced byglyim-ledger compute --snapshot PATH) with the constitution-C9 waiver gate: a computed-level drop (or a feature dropped from the registry) fails the gate unless an unexpiredledger/waivers.tomlwaiver covers it, a waiver expiring beyond the 14-day horizon is inert (error diagnostic), and an expired waiver that would have covered a regression is itself an error so a stalewaivers.tomlcan never mask a real regression. Split exactly likecompute.rs: theSnapshotStoretrait (FileSnapshotStoreon disk,InMemorySnapshotStorefor tests) abstracts where snapshots come from,diff_levelsis the pure engine,execute_diff/run_diffwire it; hand-rolled proleptic-Gregorian date arithmetic (NaiveDate, Hinnant’s day-number algorithms) keeps the dependency-light convention. Renderers are the text report and theglyim.ledger-diff/1JSON contract; wired asglyim-ledger diff <BASE> <CURRENT> [ROOT] [--format text|json], with thereadiness_diffexample and the dependency-freediffbench. -
Scaling analyzer (M2.4 first slice):
tools/glyim-bench/src/scaling.rsimplements the plan’s M2.4 — measure a{size}-parameterized command at every input size and fit the log-log scaling exponent.fit_scalingis a pure ordinary least-squares over(log size, log mean wall time)(exact recovery of power laws, constant series pinned to exponent 0 by convention),substitute_sizeis the argv contract,run_scalingdrives the M2.2 runner per size, andexecute_scalingfits a stored report history through the M2.5ReportStoreseam — a committed report history doubles as a scaling-history input without a new IO boundary. Budget semantics mirror the M2.5 gate (exponent strictly above the budget isSUPERLINEARand fails); wired asglyim-bench scale [--sizes LIST] [--max-exponent E] -- CMD..., with thescaling_fitexample and the dependency-freescaling_enginebench.
Fixed
- Docs drift, verified against the code: the Astro CLI reference
(
glyim-docs/src/content/docs/reference/cli.mdx) listed onlyobj/exec/mir/llvm-ir/asm/cdylibemit kinds —syntax,stats, andrun(documented in the README’s flag table) are added, the flag table gains the M2.1--time-passes/--self-profilemeasurement flags, and--backenddocuments theinterpbackend the driver accepts for--emit run; the glyip reference’sglyip build --release -O2example used a short flag the binary does not have (the parser only takes--opt-level, as the README already showed) and now reads--opt-level 2. CONTRIBUTING.mdcited a hand-maintained “KNOWN_GAPS §3.5.26” section that no longer exists (the document is generated fromledger/gaps/known/*.tomland carries GAP-NNNN entries, not numbered sections); the sentence now points at the registry’s link-failure diagnostics.SECURITY.mdclaimed the gaps file “documents dozens of incomplete features” — the generated registry holds exactly 5 open gaps; the claim is corrected to the machine-checked count.README.md’s tooling summary listed the--emitkinds withoutrun(its own flag table two hundred lines below already documented it); the list now includesrun.glyim-docs/src/content.config.ts.bak.20261112-165003was a tracked editor backup file (committed hygiene slip); removed from the index.tools/glyim-ledger/Cargo.toml: the package description still enumerated the M1.7-era command set (computeonwards missing); it now matches the shipped surface including the evidence faces.tools/glyim-bench/src/runner.rs/tools/glyim-bench/src/trend.rs: the last twoexpectcalls in non-test code (against the CONTRIBUTING no-unwrap/expectrule) are replaced with typed fallbacks —run_iterated’ssummarize(...).expect("iterations >= 1")becomes anok_or_elseintoBenchError::InvalidPlanbehind the existing zero-iteration guard, andexecute_trend_from_history’s two.expect("covered above")endpoint reads become anand_then-destructured pair that degrades to the guard’s no-instruction-drift branch instead of panicking. Same semantics on every reachable path;glyim-benchnow has zeroexpect/unwrapoutside tests.tools/glyim-bench/src/main.rs: thediffarm passedjson.as_ref()(Option<&PathBuf>) intoexecute_diff, which takesOption<&Path>— the binary did not compile (E0308). Fixed withjson.as_deref();cargo check --workspace --all-targetsis green again.crates/glyim-cli/src/lib.rs/crates/glyim-cli/src/linker.rs: the ICE-report writes and the linked-binary chmod silently swallowed theirio::Error(let _ = ...); both now surface throughtracing::warn!with the failing path (the write failures decide whether a bug report links to a real artifact; the chmod failure decides whether the linked binary runs at all).- Status renderers (M1.9 first slice):
tools/glyim-ledger/src/status.rsrenders the M1.8 engine’s outcome as the two plan-M1.9 artifacts that hang directly off it: theglyim.status/1JSON contract (per-level histogram + per-feature summary entries; the compute contract keeps themissing-reason prose) and the marker-delimited Markdown block (<!-- ledger:status:start/end -->) the “generated content” embedding step needs. Both are pure functions of the engine outcome — no clock, entries already sorted — pinned by golden tests, a summary-vs-entries cross-check, and byte-identical repeat renders. Wired asglyim-ledger status [ROOT] [--evidence PATH] [--format md|json], with thestatus_reportexample and the dependency-freestatusbench; the “STATUS is up to date” CI gate and the remaining M1.9 renderers (KNOWN_GAPS.mdgeneration, Astro page) are later slices. - Level-computation engine (M1.8 slice):
tools/glyim-ledger/src/compute.rsimplements the plan’sledger computeas a pure function of (registry, evidence, policy). Per feature it walks the L0–L4 evidence ladder (level N requires every rule of levels L1..N; a level whose rules are all backend-gated away stops the ladder instead of advancing vacuously), applies every open gap’scapsceiling (capped_bynames the cappers), and reports the[hardening]axes (fuzz_cpu_hours,mutation_kill_rate_pct) asunmeasuredfor L5 targets — no evidence kind records them yet, so nothing silently claims hardening. The policy schema (glyim.ledger-policy/1,ledger/policy.toml) lives intools/ledger-schema/src/policy.rsbeside the other strict registry schemas; evidence enters through theEvidenceSourceseam (ProjectEvidenceSourceoverledger/evidence/*.jsonl,JsonlEvidenceSourcefor explicit paths,InMemoryEvidenceSourcefor tests), reading the harness’sglyim.evidence/1wire format strictly (deny_unknown_fields, schema-tag check, hash/mode/backend invariants) without a dependency on the test-harness crate. Determinism and monotonicity are pinned by golden tests and a deterministic-PRNG property test (evidence growth never lowers a computed level); theglyim.ledger-compute/1JSON contract (--format json) and the text report render the same outcome. Wired asglyim-ledger compute [ROOT] [--evidence PATH] [--format text|json], with thecompute_levelsexample, the dependency-freecomputebench, theTOOL-LEDGER-COMPUTEregistry row, and README/CLI docs. - Corpus substrate (M2.3 slice 1):
tools/glyim-bench/src/corpus.rsadds the seven deterministic synthetic generator families the master plan’s M2.3 calls for (wide, deep, generic, trait, match, macro, closure) as pure functions of(family, seed, size)— no clock, no ambient PRNG — each mirroring a shape proven by an existing run-pass fixture, with the reference exit code derived by construction under documentedi32overflow bounds. Theglyim.corpus/1manifest (deny_unknown_fields, byte-deterministic rendering) records family, seed, size, exit, compile flags, and the FNV-1a-64 identity of the source;CorpusManifest::verifyregenerates every row and fails with a typedCorpusIdentityMismatch— the machine-checked “corpora committed with hashes” guarantee. New seams carrytracingspans (corpus_generate,corpus_manifest_build) and miette help text (CorpusPlan,CorpusManifestParse,CorpusIdentityMismatch). Tests pin determinism, exit-code contracts, JSON round-trip/strictness, drift detection, and FNV vectors; benchglyim-bench --bench corpus_genpins build/verify/marginal cost; new consumer exampletools/glyim-bench/examples/corpus_walk.rs; ledger rowTOOL-BENCH-CORPUS-GEN. - Micro-debt cleanup:
glyim-test’sTestMode: FromStrnow carries a typedTestModeError(miettehelp()with the canonical mode list;Displaytext byte-identical to the former string error, so substring assertions keep passing) instead ofErr = String— the same debt class as the ledger/metrics CLI errors — andtools/glyim-pilot’s HTTP control-plane bind degrades to a logged error instead ofunwrap()-panicking the detached task (constitution C4). - Docs drift fixes: the README repository map now lists the
glyim-ledger gapssubcommand (landed with the M1.7 witness-debt report), records the M2.3 slice-1 state, and lists thecorpus_walkexample; the degenerate/// Struct.//// Variant.placeholder rustdocs incrates/glyim-test/src/harness/config.rsare replaced with real field docs (the workspace-wide placeholder sweep — ~2.6k sites — is tracked as a docs follow-up). - Gap registry migration (M1.7 slice): the open
KNOWN_GAPS.md§§1–8 entries are now registry rows underledger/gaps/known/— the seed’s GAP-0001/GAP-0002 join GAP-0003 (§4,panic!does not unwind — intentional, documented), GAP-0004 (§6, a partial move out of aDrop-implementing type suppresses the parent destructor — witnessed) and GAP-0005 (§6, conservativeneeds_dropfordyn Trait/projections). Newglyim-ledger gaps [ROOT]subcommand renders the witness-debt report (GapOutcome/run_gaps/format_gap_report), with a consumer example (tools/glyim-ledger/examples/gap_report.rs), a dependency-free bench (benches/gap_report.rs), theTOOL-LEDGER-GAPSregistry row, andtracingspans on the new seam.KNOWN_GAPS.mdstays the prose audit (verification recipes + closed entries) and points at the registry; the ~6.1k-line raw session log that had accreted after its Verification section moved todocs/archive/session-log-s16-s18.md. - Measurement harness (M2.2 slice): new
tools/glyim-benchcrate turns a command (or an in-process workload) into numbers with a stability guarantee — the M2.2 definition of done is a variance budget, not a speed number: instruction-count CoV < 0.1 % over 10 runs.glyim-bench run [--iterations N] [--source perf|callgrind|wall] [--json OUT] -- CMD...executes the command N times and prints the report;--source perfwraps the child inperf stat -x, -e instructions,cycles,--source callgrindinvalgrind --tool=callgrind, and the default auto-detectsperf, falling back to wall-only sampling (logged atinfo, never silently). Child RSS comes fromgetrusage(RUSAGE_CHILDREN)(Linux; the running maximum over reaped children).glyim-bench gate [--max-cov-pct P] REPORTre-checks a written report against the budget and exits non-zero on failure.- New
glyim_benchlibrary seams:runner::run_iterated(oneBenchSampleper iteration),sourceparsers forperf stat -x,CSV and the callgrindsummary:line,stats(min/mean/median/max + population CoV,DEFAULT_MAX_COV_PCT = 0.1),alloc::CountingAllocator(opt-incounting_allocator!macro; gross allocation events/bytes, the columns the M1.5 evidence schema reserved for M2), andreport(glyim.bench/1JSON withdeny_unknown_fields, no clock/PRNG data, byte-deterministic rendering — same discipline as the M1.5 evidence records). - Errors on the new seams are typed
BenchErrordiagnostics with actionablehelp()text (a missingperfsuggests--source wall; a gate failure suggests raising--iterations); the runner emitsbench_runspans and per-sampledebug!events. - Tests: CoV vectors, gate boundaries, both counter parsers (with
<not counted>/<not supported>handling), report round-trip + unknown-field rejection + determinism, and (unix) runner end-to-end oversh -c. New benchglyim-bench --bench runner_overheadpins the harness’s own cost; new consumer exampletools/glyim-bench/examples/measure_alloc.rswalks the in-process counting-allocator path. - Ledger: the
tooling.bencharea joins the taxonomy andledger/features/tooling/bench.tomldeclares the harness surface (TOOL-BENCH-RUN,TOOL-BENCH-COUNTING-ALLOC,TOOL-BENCH-STABILITY-GATE).
- Micro-debt cleanup:
tools/glyim-ledger‘sparse_args/write_schemareturn a typedLedgerCliErrorandtools/glyim-metrics’ CLI a typedMetricsCliError(bothmiette::Diagnosticwith per-varianthelp()lines) instead of bareResult<_, String>; tests now assert on constructors rather than message substrings, and CLI output still carries the usage text plus ahelp:line. - Docs drift fixes: the README repository map no longer lists the
already-shipped M2.1 slice as a “next plan item” (it now records the
landed M2.1/M2.2 state and points at M1.7/M2.3 as next), the “Tracked
gaps” async bullet no longer claims loop-await state machines are
implemented (
.awaitin a loop body is the diagnosed[T0060]hard error perKNOWN_GAPS.md§1), the member count is 39 (34 + 5 tooling) with atools/glyim-benchrow,docs/TECHSTACK.mdre-anchors at workspace 0.7.1 (ba2a526e) and records themiette/clap/tracingconsumer additions and thelibcper-crate extra. - Per-phase instrumentation (M2.1 slice): every pipeline phase
(load → parse → expand → defmap → hir → typeck → lower → borrowck →
opt → mono → codegen) now opens a
tracingspan and accumulates wall-clock microseconds into aglyim_pipeline::PhaseProfile, exposed onCompileArtifacts/ every emit path.glyimCLI:--time-passesprints the fixed-width per-phase table on stderr;--self-profile[=FILE]writes a Chrome Trace event list (Perfetto /chrome://tracing-openable; value is=-bound so the positional INPUT can never be swallowed, bare form defaults to./trace.json);--emit=statsruns the analysis-only front half and writes a schema-versioned (version: 1) JSON report with the phase table plus mono/warning counters. A compile-cache hit records no phases and says so instead of printing an empty table.- New
glyim_pipeline::Pipeline::compile_statspublic API backs--emit=stats;emit_mir/emit_syntax/emit_llvm_ir/emit_asmnow return the profile so every emit mode can honour--time-passes/--self-profile. - Determinism contract (unit-tested): the phase set/order is pinned, all three renderers are byte-deterministic for a given profile, and an empty profile renders a valid zeroed report (no NaN).
- Errors on the new seams carry miette help text (e.g. an unwritable
--self-profilepath suggests the remedy) and the write path emitstracing::debug!events. - New consumer example
crates/glyim-pipeline/examples/phase_profile.rsdrivescompile_stats+ all three renderers as a library consumer;hello_pipelinenow also prints the phase table. New benchglyim-pipeline --bench phase_profmeasures the renderer cost (sub-µs per render — the instrumentation gate is effectively free).
- Micro-debt cleanup:
glyim-test’s fixture-header parser (harness::config::parse_test_config) returns a typedTestConfigError(mietteDiagnosticwith an actionablehelpline naming the//@grammar and the tag codemod) instead of a bareString; the stale rustdocs inglyim-hir/src/lower/lower_async.rsthat claimed the multi-await v1 desugar was an unwired scaffold (and referenced a nonexistentallow(dead_code)) now describe the live dispatch; the malformedKNOWN_GAPSreference in theglyim-mir-interpcrate docs is fixed. - Docs drift fixes: README’s
glyipquickstart no longer documents a nonexistent-O2flag (glyip buildtakes--opt-level), the CLI flag table gains--with-stdlib,-A/-W/-D,--emit=syntax, and the new M2.1 measurement flags, the stdlib module lists match the actuallib/directories (parse,alloc,int_str), the “Tracked gaps” section no longer claims cross-frame unwinding is missing (it is implemented and hardened — seeKNOWN_GAPS.md), and the repository map describes the real milestone state (M0 landed, M1.1–M1.6 landed) instead of “M0 slice”.docs/TECHSTACK.mdnow recordsasync-lspin the §2 table (previously claimed absent whileglyim-lspdepends on it), fixes theclapconsumer list (glyim-cli/glyip/glyim-pilot— notglyim-ledger), corrects thereqwest/flate2/tarversions, updatesmiette’s consumers, and re-anchors its source-of-truth header at workspace 0.7.0. CONTRIBUTING no longer claimsRUSTC_WRAPPER=kacheis set in the default dev environment (it is maintainer-machine-specific), and the staleglyim-testmanifest note about the (now closed) asyncfn_abi_ofcodegen gap is reconciled with CI. - Evidence JSONL emitter (M1.5 slice):
glyim-testnow emits one readiness-ledger evidence record per executed fixture whenGLYIM_TEST_EVIDENCEnames an output path — the machine-checked inputledger compute(M1.8) will consume, per plan §3.4/§6 M1.5.harness::evidence: typedEvidenceRecord(glyim.evidence/1) with outcome/backend enums from the ledger’s backend set, SHA-256 fixture hashes over the exact source bytes, mode, revision, declared//@ feature:///@ backends:tags, and stable short reason classes (free-form compiler output deliberately dropped so message refactors cannot move ledger statistics).instructions/rss_kbare reserved (alwaysNoneuntil M2’s counting-allocator instrumentation).- Hermetic by construction: no clock or PRNG data —
TestResult::durationnever reaches a record, and two runs against the same fixtures serialise byte-identically (tested). Records deserialise strictly (deny_unknown_fields, same discipline asledger-schema), andwrite_evidencevalidates the whole slice before writing so a schema bug cannot poison the evidence store. tracingspans (evidence_write, record/byte count events) on the emission path, matching the harness’s existing span style; failures render throughmiettewith actionablehelptext (the remedy namesGLYIM_TEST_EVIDENCEor the schema rule that was violated).- Bench:
glyim-test --bench evidencemeasures a full 375-fixture evidence pass (record construction ≈0.6 ms, serialisation ≈0.2 ms, validated write ≈0.6 ms) — the M1.5 gate is effectively free. - New consumer examples:
crates/glyim-test/examples/evidence_report.rsround-trips the JSONL contract (producer + validator + reason-class aggregate) andcrates/glyim-pipeline/examples/hello_pipeline.rsdrives the compiler as a library (write a.gprogram, lower it to MIR in-process).
- Micro-debt cleanup: the harness JSON reporter no longer swallows
failures —
GLYIM_TEST_JSONwrite/serialise errors now print a miette-rendered diagnostic instead of vanishing intolet _ =; the dead workspace dependenciestextwrap,owo-colors, andpetgraph(declared in[workspace.dependencies], referenced by no member, absent fromCargo.lock) are removed; the stale committedCargo.lock(members at 0.5.1 vs workspace 0.6.0) is regenerated. - Docs drift fixes: README’s architecture table gains the missing
glyim-gsxrow and a tooling row fortools/*(the workspace has 38 members: 34 crates + 4 tools); CONTRIBUTING says Rust ≥ 1.95 (was 1.85), replaces the inline-#[allow]guidance with the M0 zero-allow policy (relaxations only in[workspace.lints.clippy]), documents the M1.4//@fixture grammar instead of the legacy// key:headers, and updates the corpus count (~260 → ~410);docs/TECHSTACK.mdis rewritten (v2.0.0) to list only dependencies the manifests actually declare (the previous revision listedsalsa/chumsky/egg/regalloc2/async-lspand nonexistent crates); the master plan’s F1 evidence pointer now reflects that the production-readiness playbook has been retired fromdocs/roadmaps/. The M0 metrics ratchet baseline is refreshed (+1,041 code lines, +10 test functions, +16 documented items, 0 inline allows). - Fixture annotation grammar + codemod (M1.4): every
.gfixture carries a machine-readable//@header, and the harness rejects fixtures that lack one — the “100% of fixtures tagged; fixtures lacking expectations rejected” DoD is a tested fact, not a promise.glyim-test: newannotations::directivesgrammar —//@ mode:,//@ feature:(comma-separated registry IDs, shape-checked),//@ backends:(validated against the ledger’sgam/llvm/cranelift/bytecodeset), theexpect-*outcome family (expect-exit/expect-stdout/expect-stderr/expect-error/expect-warning/forbid-warning), and the harness gates (needs-llvm,ignore,only-target,compile-flags,aux-file,timeout,min-version,revisions,[rev] compile-flags). Unknown keys, malformed IDs, duplicate singular keys, and mixing a legacy// key:header with its canonical//@spelling are hard parse errors, so a typo can never become a silent no-op tag.glyim-test: the collector rejects fixtures with no//@header (MissingAnnotations) and fixtures whose mode lacks the required expectation — run-pass/run-fail must pin an exit code or stdout/stderr pattern (the strategies’ defaults0/1are now spelled out in every fixture), compile-fail must carry an inline//~annotation or//@ expect-error:(MissingExpectation).glyim-test: newglyim-tag-fixturescodemod bin converts every fixture header to the canonical form and derives the ledger tags (410 fixtures: 375 in theglyim-testcorpora plus the 35 in the per-crate corpora ofglyim-lower/glyim-typeck/glyim-pipeline/glyim-lang-{alloc,core,std}that drive the sameTestCollector):featurefrom a curated keyword table (92 distinct IDs, all cross-checked against the M1.2 registry via--verify-ids) plus the fixture-mode feature,backendsfrom the CI reality (gam, llvmfor the run corpora andneeds-llvmfixtures;gam, bytecodefor the--backend=bytecodefixture;gamelsewhere). The rewrite is idempotent; prose comments pass through untouched.- The tagging surfaced two real seams:
runtime/drop_order.g(a bytecode-backend fixture not driven by any corpus — the async-proof gating intests/runtime.rscoversruntime/m5only) and thetypeck/+codegen/fixture dirs (no corpus root points at them). Both are now tagged and recorded for the ledger’s work queue (M1.9ledger next), not silently fixed here. - Bench:
glyim-test --bench annotationsmeasures one full discovery pass (parse: 375 rich headers in ~0.4 ms; codemod rewrite: 375 legacy fixtures in ~1.4 ms) — the M1.4 gate is effectively free. - New tests: 29 unit tests across the grammar contract and the codemod
rewrite rules, plus the workspace-wide
annotations_corpusDoD gate (covering the per-crate corpora as well). The M0 metrics ratchet baseline is refreshed (+129 test functions, 0 inline allows). - Docs drift fixed while landing: README badge/MSRV said Rust 1.94
(workspace
rust-versionis 1.95), the crate-count badge said 20+ (the workspace has 38 members), and the stale committedCargo.lock(members at 0.5.0 vs workspace 0.5.1) is regenerated.
- Inventory extractors, slice 1 (M1.3):
ledger inventoryreads the source, so the registry can no longer drift from the code (plan §3.5).ledger-schema: twosyn-based extractors — MIR IR variants (mir.<Enum>.<Variant>for the five backend-parity enumsStatementKind/Rvalue/Operand/ProjectionElem/TerminatorKindincrates/glyim-mir) and runtime FFI symbols (runtime.ffi.<symbol>for every#[no_mangle]/#[unsafe(no_mangle)]pub extern "C"fn incrates/glyim-runtime, 99 of them). Feature entries gain an optionalinventory = [...]claim list; a newledger/inventory-ignore.tomlregisters deliberate non-features (exact keys only — no globs, so a new variant can never be silently swallowed).inventory_diagnosticsfailsledger checkon unmapped items (LEDGER-INVENTORY-UNMAPPED), stale ignores (LEDGER-INVENTORY-STALE-IGNORE), stale claims (LEDGER-INVENTORY-STALE-CLAIM), duplicate claims/ignores (LEDGER-INVENTORY-DUP-CLAIM,LEDGER-INVENTORY-DUP-IGNORE), claimed-and-ignored conflicts (LEDGER-INVENTORY-CONFLICT), and unparseable sources (LEDGER-INVENTORY-PARSE) — the M1.3 DoD “adding a MIR variant without registration failsledger check(tested)” is a unit + integration tested fact.glyim-ledger: newledger inventory [ROOT]subcommand (items with claim/ignore status, exit 1 on gate errors);ledger checknow runs the inventory gate and reports the extracted item count.- Registry seed: the 15 implemented FFI families claim their 99
symbols; the 29 existing MIR variants are ignored-with-reason (the
per-variant rows are the §3.6 backend-parity matrix, M1.8). The
extractor immediately surfaced registry drift:
RUNTIME-FFI-FSclaimed 16 symbols in its title but implements 14 (title corrected);RUNTIME-FFI-SYNC(mutex/rwlock) has no backing symbols at all and stays unclaimed until they land. - Bench:
extract_inventoryharness measures parse+extract of a synthetic 150-variant/100-symbol corpus (~1.4 ms, parse-dominated). - 31 new tests across the two ledger crates, written test-first.
- Feature registry seed (M1.2): the ledger’s claim surface grows from
6 smoke-test entries to 216 curated features across 32 registry files,
covering the documented inventory end to end: the README feature list
and language tour,
docs/specs/v0.1.0.md, all eightdocs/design/*documents, the 33 stdlib modules ofglyim-lang-core/-alloc/-std, the 16 runtime FFI symbol families, and the tooling surface (CLI,glyip, LSP, test harness, and the ledger/metrics tooling itself).ledger-schema: the feature taxonomy the master plan delegates to an “Appendix C” that was never checked in (docs drift found during the M1.2 deep dive) now lands in-repo asTAXONOMY— 34 areas over six namespaces (lang.*,compiler.*,codegen.*,tooling.*,std.*,runtime.*), each with an enforced ID prefix — plusmin_target_levelencoding release gate RG-09 (core⇒ L5,std⇒ L4) at declaration time.ledger checknow fails on unknown areas (LEDGER-AREA-UNKNOWN), prefix mismatches (LEDGER-ID-AREA-MISMATCH), tier/target violations (LEDGER-TIER-TARGET), and dead spec references (LEDGER-SPEC-MISSING): every entry’sspecmust resolve to a real repo-relative file, so a moved or renamed doc breaks CI instead of silently rotting the registry.ledger-schema: newload_project_registryproduction entry point —glyim-ledger check <ROOT>walksROOT/ledgerand anchors repo-relative references (specpaths, gap witnesses) at the project root, matching the plan’s path examples; the fixture-facingload_registrykeeps its behavior for tests.glyim-ledger: the check gate runs the taxonomy/spec validation and reports abytecodebackend variant for theglyim-codegen/glyim-bytecode-vmexecutor (goes away with ADR-004’s removal, if accepted).- Bench: the
ledger-schemaload+validate harness is scaled to the registry’s real size (300 features / 50 gaps synthetic, was 200/40), switched to the productionload_project_registrypath and fixed to a taxonomy-valid fixture, so CI headroom tracking measures the M1.2 shape: ~2.6 ms per load+validate of 350 entries. - Seed data fixes found by the new gates:
LANG-ASYNC-AWAITnow targets L5 as RG-09 requires forcoretier entries. - 65 tests total in the two ledger crates (14 new taxonomy/spec tests
in
ledger-schema, 2 new check-integration tests inglyim-ledger), written test-first.
- Readiness Ledger v1 foundation (M1.1): new
tools/ledger-schemaandtools/glyim-ledgercrates implementing the registry schema half of the master plan’s Workstream A (§3).ledger-schema: strict TOML entry types ([[feature]],[[gap]]) withdeny_unknown_fields— typos are load errors, never silently ignored keys; the maturity-level/gap-class/backend/lane vocabulary from the plan (§3.2, §3.3, §3.6, §3.8);load_registrywalkingledger/features/**andledger/gaps/**deterministically (sorted walks, sorted diagnostics);Registry::validate— theledger checkengine (unique IDs,affects/requiresreference resolution,requirescycle detection, and the strict-xfail witness contract with//@ known-gap:headers and ratcheted witness debt); and a dependency-free JSON-Schema (draft-07) export for both entry types.glyim-ledger:ledger check [ROOT]registry gate (exit 1 on any error, witness debt reported as warnings) andledger schema [OUT]JSON-Schema export. Hand-rolled argument parsing, matching theglyim-metricsno-clap convention. 49 tests total, written test-first, plus a load+validate throughput bench.- Seed registry
ledger/: 6 real feature entries (control flow, pattern matching, generics, async, GSX views, unwind cleanup) and 2 real gap entries migrated fromKNOWN_GAPS.md(GAP-0001 await-in-loop class a, GAP-0002 SEH cleanup unreachable class b), both declaredunwitnesseduntil the M1.6/M1.7 witness fixtures land. - CI: new
ledger-checkjob runs the gate on every PR (pure Rust, no LLVM dependency).
- GSX view syntax (docs/design/GSX-in-Glyim.md): first-class, typed,
host-agnostic view syntax with a dedicated compiler stage.
- Frontend:
Gsx*CST nodes andparse_gsx_element(elements, fragments, self-closing, directive attrson:/class:/style:/bind:, spread, shorthand, hyphenated names,for … bykeyed iteration, text holes split at parse time; zero lexer changes). - HIR:
Expr::Gsxpreserves element structure (no call-tree desugar). - Typeck:
check_gsxvalidates tags/props/events/children against dialect schemas and checks hole expressions. - New crate
glyim-gsx: View IR (skeleton + slots + regions), flat-u32blueprints, read/write-set analysis with prefix interference, mutation-specialized patch functions (§7.5), SSR emitter, Host trait + headless op-recording host, keyed-list LIS reconcile,Signal<T>(G0201) diagnostics with fix-its. 88 crate tests including the §3.1 Counter example end-to-end.
- Frontend:
- Fuzzing infrastructure:
fuzz_parse(lexer/parser/CST round-trip) andfuzz_compile(full-pipeline ICE detector) cargo-fuzz targets with corpus seeds and a token dictionary. - CI: strict M5 runtime proof (real LLVM codegen), differential suite
(LLVM native vs MIR interpreter), lint job (
fmt+clippy -D warnings), cargo-deny supply-chain job, runner caching, timeouts, concurrency cancellation. - MIT LICENSE file, declared MSRV (
rust-version = "1.85"). - M0.6 metrics ratchet: new
tools/glyim-metricscrate (TDD, 18 unit tests + dependency-free scan bench) measures lexical repo health —.rsfiles, code lines, public items, doc coverage, test functions, and the inline-allowcount the M0 zero-allow policy pins at zero. The binary writesmetrics/baseline.json(906 files / 226.5k lines / 4811 tests / 0 inline allows at M0) and CI’s newmetrics-ratchetjob fails on any regression while allowing improvements (gates never weaken, C9). - Workspace-wide pedantic lint rails (M0 §2 C4, §7.4):
[workspace.lints.clippy] pedanticis wired into all 36 member crates via[lints] workspace = true; every relaxation is a single rationale-annotated entry in the root manifest, and the enforced gate (cargo clippy --workspace --all-targets --all-features -- -D warnings -W clippy::pedanticwith manifest-derived re-asserts) passes with zero inline#[allow]/#[expect]attributes in the tree. rust-toolchain.tomlpins local development to thestabletoolchain (MSRV 1.95.0 stays a separate CI job).
Fixed
glyim-opt’s drop-flag statement inspection re-read the pushed statements throughnew_stmts.last().unwrap()— provably non-empty, but the re-inspection also saw the optional plain-flag statement pushed one line earlier, so the per-element check’s input depended on push order. The per-element flag statement is now computed from the original statement before it is moved (branch is total; emitted order fixed: original stmt, plain flag, per-element flag). Behaviour-preserving; theCOMPILER-OPT-DROP-ELABfixtures pin it.- GSX SSR emitter dropped every element’s closing
>(</h1instead of</h1>) — the crate’s own G7 snapshot tests were left red onmain(the ubuntuTestjob has been failing since); the fix makes all 88glyim-gsxtests pass. glyim-test’sjson-outputfeature did not compile when enabled: the optionalserdedependency lacked itsderivefeature, so the feature’s#[derive(Serialize)]blocks failed (cargo test --all-featurescould not build the crate). Found by the M1.3 gate run.
Changed
- The strict-xfail witness contract covers run modes (M1.7):
//@ known-gap: GAP-NNNNis now accepted onrun-pass/run-failfixtures (a pinned exit code is a valid gap-open behaviour witness) and a failing run witness sharpens intoFailureReason::KnownGapClosedinstead of a generic exit/output mismatch.compile-pass/uiwitnesses stay rejected at discovery — the discovery error is renamedWitnessRequiresCompileFail→WitnessUnsupportedModewith updated guidance. First consumer:tests/run-pass/behavior/partial_move_drop_guard_known_gap.gwitnesses GAP-0004 on the exit-code contract. regalloc2dependency removed from the workspace (unused).- Session documents
HANDOFF.mdandFIXES.mdmoved todocs/archive/to keep the repo root navigation-focused. - Dead code deleted across the workspace: unused fields/methods/helpers
(
DoneDefaultsfields,record_commit/set_provider_cooldown,SourceMap::path,AnalysisDriver::cache_dir, test-only helpers that no test reached, …) — replaced with#[cfg(test)]where the consumers are the test suites themselves. - ~160
missing_docsgaps closed;push_str(&format!(..))idioms converted towrite!/writeln!; format args inlined peruninlined_format_args. - CI installs LLVM 23 consistently (
./llvm.sh 23— previously mixed v22 script with v23 dev packages). - Release profile enables
overflow-checks(compiler-internal arithmetic overflow is an ICE, never a silent wrap).
Fixed
parse_typerecursion depth unbounded → deeply nested types crashed the compiler with an uncatchable stack overflow (SIGSEGV). Now a parse diagnostic (MAX_EXPR_DEPTHguard, same policy as expressions).- MIR interpreter subslice projection: bounds guard checked
towhile subtractingfrom→usizeunderflow (panic in debug, bogus slice length in release). Both operands are now validated. - MIR interpreter
byte_payload: program-controlledrepeat(n)could OOM the host; payload capped at 16 MiB. - const-eval array/tuple index:
u128 → usizetruncation silently aliased indices ≥ 2^64 to in-bounds elements. Oversized indices now error. - Interpreter internal index accesses (
basic_blocks, argument locals) returnInterpErrorwith a “please report” message instead of panicking. glyim-cliICE report now includes the panic message, suppresses the default panic printer duringcatch_unwind, and points to the correct issue tracker.glyip testisolates interpreter panics per fixture instead of aborting the whole test session.- LLVM codegen: recoverable type/ABI failures return diagnostics instead
of panicking (
fn type lowering failed,Codegen error, variant index). - README: correct repo URL, binary name, and LLVM-install guidance.
- Legacy session instrumentation and stale doc-comment artifacts (unbalanced backticks in doc comments, detached docs, duplicated crate-level docs) cleaned up as part of the M0 doc pass.
[0.1.0] — initial public state
Research-grade end-to-end compiler: lexing, parsing, name resolution,
macros, HIR, type inference + trait solving, NLL borrow checking, MIR
optimizations, LLVM 23 backend, bytecode backend + VM, MIR interpreter,
LSP, glyip build tool, and a five-mode test harness.
