specverb.lock: store goMod as line array, symmetric with goSum #135

New issue

Closed

opened 2026-06-11 01:08:01 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-11 01:08:01 +00:00

Owner

specverb.lock's goMod field stored the whole go.mod as one escaped newline-string, while the sibling goSum field was already a []string of lines. Same kind of data (a verbatim replay blob), two different shapes - and the blob form is unreviewable in a diff (one giant line).

Make goMod a []string too, symmetric with goSum, order preserved (go.mod block structure is significant). Replay joins with newlines. Schema bumps v1 -> v2, forcing a re-lock; ward is the only consumer.

Not parsing go.mod into structured require/replace JSON: nothing reads the structure (the driver only replays it and reads cliGuard separately), and re-serializing exact go.mod syntax would be fragile. Lines are the right altitude.

Raised by Kai.

`specverb.lock`'s `goMod` field stored the whole go.mod as one escaped newline-string, while the sibling `goSum` field was already a `[]string` of lines. Same kind of data (a verbatim replay blob), two different shapes - and the blob form is unreviewable in a diff (one giant line). Make `goMod` a `[]string` too, symmetric with `goSum`, order preserved (go.mod block structure is significant). Replay joins with newlines. Schema bumps v1 -> v2, forcing a re-lock; ward is the only consumer. Not parsing go.mod into structured require/replace JSON: nothing reads the structure (the driver only replays it and reads `cliGuard` separately), and re-serializing exact go.mod syntax would be fragile. Lines are the right altitude. Raised by Kai.

coilysiren referenced this issue from a commit

2026-06-11 01:08:24 +00:00

refactor(specverb): store specverb.lock goMod as a line array

coilysiren closed this issue

2026-06-11 01:08:24 +00:00

coilysiren referenced this issue from coilyco-flight-deck/ward

2026-06-11 01:09:34 +00:00

Re-lock ward-kdl: pruned spec lock + v2 dep lock #84