79dafa38f0
Make goal 12 great documentation, state how the README meets it, and plan the README's reorganisation for 0.2.0
lilleman2026-10-14 22:50:30 +02:00
5b1169f9a5
File nested-template gaps: a name bound through a name, a repeat range and a JSON-escape transform
lilleman2026-10-14 22:27:54 +02:00
16b5e0767c
File relative date bounds and exact-count choices as plan items
lilleman2026-10-14 22:05:26 +02:00
7739c09163
Check the plan before filing into it, keep filed items in order, name the filer's tests in the gate, and record the merge over a worse ruling
lilleman2026-10-14 13:39:42 +02:00
16afcff09c
Test that the filer keeps its items in order and exits 2 on a plan it cannot read
lilleman2026-10-14 13:37:32 +02:00
5aca8a1fe8
Record the comprehension check: paired ruling against f90b4d6 rules worse
lilleman2026-10-14 13:34:41 +02:00
5a6928750c
Give the vulnerability filer a folder of its own, and leave its item's score to rank_todo.py
lilleman2026-10-14 13:31:21 +02:00
15965e7a77
State the filer's contract with the plan where it is read, name the step an outage fails, and mark an unfixed vulnerability by name
lilleman2026-10-14 13:17:26 +02:00
6a7da08002
Answer architecture round 4: 0 🔴, 0 🟡; an entry with no summary files without a bare colon
lilleman2026-10-14 13:11:08 +02:00
9049f90cc5
Answer architecture round 3: 0 🔴, 2 🟡; a plan-only change runs the test that pins the plan's shape, and a module record carries its own path
lilleman2026-10-14 13:09:08 +02:00
2d86f4f0c0
Answer architecture round 2: 1 🔴, 3 🟡; read the report and edit the plan in two functions, propose only while no pull request is open, and test filing into the repository's own todo.md
lilleman2026-10-14 13:03:56 +02:00
273dd45128
Answer architecture round 1: 0 🔴, 5 🟡; a job of its own that only releases wait for, filing each vulnerability atop the plan by a pull request, a recorded decision, one gate list, and Renovate on the go run tools
lilleman2026-10-14 12:53:20 +02:00
3d0d7ef180
Test filing each known vulnerability as a security item atop the next release
lilleman2026-10-14 12:49:48 +02:00
117f685939
Fail the gate, daily and before each release, on a known vulnerability in the Go release or the module
lilleman2026-10-14 12:09:59 +02:00
d849a87205
Update golang Docker tag to v1.27.2
renovate[bot]
2026-10-14 09:48:41 +00:00
6a4162b902
Score every plan item's C, how hard it is to get right, in a column after S
lilleman2026-10-14 11:44:00 +02:00
f90b4d6498
Record the comprehension check: paired ruling against c3cc251 rules same
lilleman2026-10-14 11:22:16 +02:00
fbadb99634
Answer architecture round 2: 0 🔴, 0 🟡; tie the token choice to the account type, and keep GHCR's reason in the registry decision
lilleman2026-10-14 11:19:30 +02:00
508e93d11a
Answer architecture round 1: 0 🔴, 3 🟡; copy the image to Docker Hub in a job of its own, give the registries their own decision, and name the narrowest token
lilleman2026-10-14 11:18:32 +02:00
f3fbbac0d9
Push the image to Docker Hub beside GHCR, so docker run larvit/fejkdata works
lilleman2026-10-14 10:09:30 +02:00
717f9f2abc
Drop the AUR until it reopens registration, and plan it as item 252
lilleman2026-10-14 09:37:20 +02:00
c3cc251242
Record the comprehension check: paired ruling against 891323d rules same
lilleman2026-10-14 00:09:07 +02:00
2885f7b571
Answer prose round 1: 0 🔴, 4 🟡; name the package-repository checks, list the release secrets, and point each sentence at its actor
lilleman2026-10-13 23:59:23 +02:00
a1f25e4138
Answer stability round 2: 0 🔴, 1 🟡; test that main() passes on a failed publish's exit code
lilleman2026-10-13 23:55:30 +02:00
b9ae602399
Answer stability round 1: 0 🔴, 3 🟡; fail when the latest release can't be read, build every platform's binaries when Go changes, and test main() and the Unreleased heading
lilleman2026-10-13 23:53:53 +02:00
a82279c6a4
Answer product-owner round 1: 0 🔴, 1 🟡; check the apk repository on Alpine 3.24's apk-tools 3, and say how macOS runs a downloaded binary
lilleman2026-10-13 23:53:53 +02:00
895c0e977f
Answer architecture round 4: 0 🔴, 1 🟡; run the repository checks on every file they read, and check each repository installs the release's own version
lilleman2026-10-13 20:39:06 +02:00
e6e06d007b
Answer architecture round 3: 0 🔴, 4 🟡; keep signing keys out of image layers, and build and install from the package repositories in the gate with throwaway keys
lilleman2026-10-13 20:01:37 +02:00
f08182fb94
Answer architecture round 2: 1 🔴, 0 🟡; self-host signed apt, dnf and apk repositories on GitHub Pages in place of Cloudsmith, and keep an older tag's image while leaving latest alone
lilleman2026-10-13 19:56:37 +02:00
cc7d4fb972
Answer architecture round 1: 0 🔴, 7 🟡; build with the gate's Go, guard single-version channels on older tags, record the Cloudsmith tie, and return the tag from publish()
lilleman2026-10-13 17:35:21 +02:00
e67c858d41
Ship prebuilt binaries, deb, rpm and apk packages on Cloudsmith, a GHCR image, and Homebrew, Scoop and AUR packages with each release
lilleman2026-10-13 16:56:58 +02:00
478a962f34
Test that a published release names its tag to CI, and that the gate checks the packaging config
lilleman2026-10-13 16:51:58 +02:00
f3e2c6b1bb
Release 0.1.0, and add Larvit's copyright line beside Timewave's
lilleman2026-10-13 00:34:59 +02:00
b8b4188af7
Answer prose round 1: the id bullet sets apart the test series and the real-looking SSNs, the own-data bullet names a path rather than a category, the stdin heading names all it covers, and doc.go's namespace sentence has its subject
lilleman2026-10-13 00:39:13 +02:00
5f8d55e2bb
Answer product-owner round 2: the reproducible bullet states its goroutine condition, and the table of contents names the Data format heading it links
lilleman2026-10-13 00:37:00 +02:00
df46340af2
Answer product-owner round 1: the front page's data and id bullets say what ships and what may be real, the Library section links the terms Data defines, and doc.go's synopsis matches the tagline
lilleman2026-10-13 00:34:28 +02:00
82fb611c74
Open the README with badges, what ships and a table of contents, put the stdin byte rules under a heading of their own, and move the Library section before Data
lilleman2026-10-12 21:42:27 +02:00
891323d041
Record the paired ruling at 52e0304, better, and 0.1.0's scoring run, shipped under the floor by the 0.1.0 decision, and file isPath as item 251
lilleman2026-10-12 18:30:41 +02:00
bf61527363
Answer prose round 1: the seed advice says to log a new seed in the error, the doc and the README alike, the changelog says each run takes a new seed, New's failures read in one pass, and the concurrency lines say who draws
lilleman2026-10-12 18:24:47 +02:00
e0f5493daa
Answer product-owner round 1: the seed docs say a new seed each run, not draws afresh, the README says to log a drawn seed to replay a run, and the changelog names WithSeed and the data options apart
lilleman2026-10-12 18:21:44 +02:00
5971037362
Test that the fejkdata binary without --seed draws a new seed each run
lilleman2026-10-12 18:21:28 +02:00
cde9e354c5
Answer architecture round 2: New's doc comment wraps whole, the README's stream needs no seeded, and the system-seed test reports each run's exit code and stderr
lilleman2026-10-12 18:18:46 +02:00
8e8fa92e77
Answer architecture round 1: Main draws the CLI's default seed and passes it to run, New names every option mistake at once, dataGiven says what it is, and the docs drop seeded where every sequence is
lilleman2026-10-12 18:17:45 +02:00
7c0fa4075f
Test that New names a nil module beside the missing seed, and that the CLI without --seed draws from the seed Main gives run
lilleman2026-10-12 18:17:45 +02:00
9c8a0449ca
Record the last chunk's reading cost
lilleman2026-10-12 18:13:34 +02:00
90c804f6e6
Fail New without WithSeed, naming it, and seed the CLI from the system without --seed
lilleman2026-10-12 18:13:14 +02:00
3ae8b9f1b1
Test that New without WithSeed fails naming it, that the CLI without --seed draws afresh each run, and seed every test's New
lilleman2026-10-12 18:10:57 +02:00
1a5b632b90
Answer prose round 1: List gives direct descents only, the library and CLI lines name their verbs, the template line explains its values, the geo line says which places ship, and the README's pointer rule reads in one pass
lilleman2026-10-12 18:03:05 +02:00
143311270c
Answer product-owner round 1: the release notes link the tagged README, say how to install and pin, name 64-bit targets, List and IsTemplate, the README says a nullable column needs a pointer, and item 89 names the changelog lines it changes
lilleman2026-10-12 17:58:16 +02:00
03597c43c7
Record the last chunk's reading cost
lilleman2026-10-12 17:54:16 +02:00
6220564e33
Rewrite the changelog's Unreleased as what v0.1.0 holds
lilleman2026-10-12 17:54:12 +02:00
70fdfbd591
Answer prose round 1: the README lists the release tooling's tests in the gate, and the decision says the size test checks the premise
lilleman2026-10-12 17:45:46 +02:00
5bd978d2a1
Answer stability round 1: items 191 and 192 leave the plan, the decision and item 193 name the size test, and the test's temp dir is tmp
lilleman2026-10-12 17:44:32 +02:00
ca20aff43d
Record the last chunk's reading cost
lilleman2026-10-12 17:39:16 +02:00
870082c12f
Read an existing tag through git/ref/tags in publish_release.py, following an annotated tag to its commit
lilleman2026-10-12 17:39:12 +02:00
2c9ff3b014
Test that the shipped data stays under 100 MiB and that publish_release.py stops on a tag at another commit, both in the gate
lilleman2026-10-12 17:35:58 +02:00
95af089778
Answer prose round 1: item 89 says New breaks once before release, item 26 says its break is the first after 0.1.0, and the randomBytes sentence reads in one pass
lilleman2026-10-12 17:31:58 +02:00
92309041de
Plan item 89 in 0.1.0, so New breaks once before anyone depends on it
lilleman2026-10-12 17:30:58 +02:00
13d622d57c
Answer prose round 1: the shipped-data decision says its items ship in 0.2.0, the size gate says why it comes first, and item 89 says when New breaks again
lilleman2026-10-12 17:19:09 +02:00
71676cd715
Plan 0.1.0 as the release tooling defect and the release preparation, and move every other item to 0.2.0
lilleman2026-10-12 17:17:26 +02:00
9c03958791
Answer prose round 1: bankgiro and plusgiro carry no clearing number, the phone form is called international, the NANPA, Nacha and holiday claims say no research covers them, the plate patterns are written by hand, and the taglines read in one pass
lilleman2026-10-11 23:45:00 +02:00
77e035bff0
Split item 16 into a plan item per locale category not yet shipped
lilleman2026-10-11 23:41:51 +02:00
71b0754679
Answer prose round 1: the custom-CLI test advice says why an indexed module needs each path rendered, the help ruling says the help points to --list and who ruled, ErrNoColumns's doc says what it matches, and the filed items read in one pass
lilleman2026-10-11 23:34:37 +02:00
5e6330c75b
Answer product-owner round 1: the hint for an empty stdin points to --list, the help's examples are templates only, the README's record id is an integer, and a test over an indexed module renders each path
lilleman2026-10-11 23:29:23 +02:00
00257e2851
Test that the hint for an empty stdin points to --list
lilleman2026-10-11 23:28:21 +02:00
90d1948a2b
Answer stability round 1: the tests precede the code they pin, ErrNoColumns's doc speaks of itself alone, the edited docs are reflowed, and the binding hint and a JSON-shaped template's parse position are filed as items 228 and 229
lilleman2026-10-11 23:27:59 +02:00
bcd03b729a
File what the audience bench names outside this chunk, and close item 185
lilleman2026-10-11 23:27:33 +02:00
1edc3b57dd
Show a struct filling an address from one pick, a record template compiled once, a counter per table and how a custom CLI's embed maps to paths, and record the custom-CLI builder's ruling on the help
lilleman2026-10-11 23:27:33 +02:00
9671600fff
Give the help examples that read no data and the exit codes, say a data path is no directory in one shape, suggest a record of one for a choice, name a JSON syntax error's line and column, and say no data is loaded from FakeStruct
lilleman2026-10-11 23:27:33 +02:00
1a7656d076
Test that the help's examples read no data and list the exit codes, a data path that is no directory says so in one shape, a choice suggests a record of one, a JSON syntax error names its line and column, and FakeStruct says no data is loaded
lilleman2026-10-11 23:27:33 +02:00
780586ad68
Record that no API or flag exists only for custom CLIs, and Main tells one apart by its build info and file name
lilleman2026-10-11 21:16:15 +02:00
90ffcffcd7
Rescore: the paired ruling at 69af4c1 reads better
lilleman2026-10-11 21:02:27 +02:00
adba2510db
Answer prose round 1: the CLI decision says what keeping cli off internal/ buys, the changelog and Library sentences hold one idea each, and item 185 names the three wordings its builder rules on
lilleman2026-10-11 21:00:44 +02:00
81c7ff6737
Name each line of a joined error under the command, test the command name as a pure function, and pin the version line's fallback
lilleman2026-10-11 20:58:23 +02:00
5b2bb7e681
Answer architecture round 2: every error a custom CLI prints names it, the help marks where the name goes, the version line checks the main module first, and the README embed compiles for data without a table
lilleman2026-10-11 20:56:17 +02:00
9528ecd8b0
Answer architecture round 1: a custom CLI names itself by its file, --version names its module beside fejkdata's and follows a replace, the module path comes from the library's type, the end-to-end test runs main in a subprocess, the CLI tests find the shipped modules by their manifests, and Your own CLI sits under Library
lilleman2026-10-11 20:53:00 +02:00
deb42df0e2
Record the paired ruling at fbe2fde
lilleman2026-10-11 20:53:00 +02:00
35f1eeffb2
Make the CLI the library call cli.Main, with fejkdata's own main one line over data.Modules()
lilleman2026-10-11 20:45:52 +02:00
35487cd36d
Test the CLI as package cli's Main over the modules it is given, and fejkdata's main over the shipped packages
lilleman2026-10-11 20:45:52 +02:00
9b7c3f0dc2
Answer prose round 1: goal 2.1 is dropped for goal 2, the no-street decision rests on goal 2.2 and names the item ending it, and en_US stays out of the move
lilleman2026-10-11 20:34:14 +02:00
ab3359be41
Plan 0.1.0's locales as the Nordic countries, France and Germany, and ship a country with no open address register without streets
lilleman2026-10-11 20:28:20 +02:00
87bec6f73f
Answer prose round 1: the locale rule lives once in the decision, a locale ships where the most speak it, and each source says what it holds
lilleman2026-10-11 19:19:12 +02:00
27180c661f
Split item 61 into a plan item per locale, and record the locales Ethnologue's ranking names
lilleman2026-10-11 19:16:59 +02:00
66cd1e0605
Answer prose round 1: the sources name Wikidata, the decision title reads in one pass, and the street rule's threshold says why it is five
lilleman2026-10-11 19:08:49 +02:00
1f9b201633
Answer product-owner round 2: a street joining names with a bare comma is dropped, and the US places read as a drawn tenth plus the capitals and big places
lilleman2026-10-11 19:06:28 +02:00
7eb3a334d7
Answer stability round 2: an unmatched capital's log line names both ways it can match
lilleman2026-10-11 19:06:28 +02:00
1c24ab8da3
Test that a Swedish street joining names with a bare comma does not ship
lilleman2026-10-11 19:04:38 +02:00
5cfa89c8ab
Answer product-owner round 1: a Swedish street is a street's name, Lexington, Ventura and Lynchburg ship by their postal names, and the README names Honolulu
lilleman2026-10-11 19:02:37 +02:00
d3d9547876
Answer stability round 1: the docs say the US tenth is drawn from every place, a capital matches by a name only one place in its state carries, and the test comment says what it checks
lilleman2026-10-11 19:02:37 +02:00
64e99927f5
Test that a Swedish street is a street's name, and that Lexington and Ventura ship by their postal names
lilleman2026-10-11 18:58:05 +02:00
7eb95a0de1
Record the reading cost and refresh item 167
lilleman2026-10-11 18:53:41 +02:00
2132bde2ba
Record the shares, the capitals' source and the measured cost, and close items 199 and 200
lilleman2026-10-11 18:51:54 +02:00
af49b83fa9
Re-pin the seeded sv_SE.address example
lilleman2026-10-11 18:51:07 +02:00
c42c5812fc
Ship every Swedish street, a quarter of the US streets, and every US capital and place of 100,000 beside the drawn tenth
lilleman2026-10-11 18:50:07 +02:00
52a28c390c
Test every Swedish street, a quarter of the US streets, and the capitals and places of 100,000 a draw leaves out
lilleman2026-10-11 18:48:58 +02:00
b962b71f06
Plan every Swedish street and a quarter of the US streets, Swedish streets placed by area, every US capital and city of 100,000, and the multi-county fetch in 0.1.0
lilleman2026-10-11 18:29:50 +02:00
lilleman
renovate[bot]