[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ER2CWVT0QMXEW3Q17S272W":3,"skill-same:01M7ER2CWVT0QMXEW3Q17S272W":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7ER2CWVT0QMXEW3Q17S272W","verify-main-red",null,"JoshuaHayesWasHere\u002Fjstack","JoshuaHayesWasHere","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78288453?v=4","01M7EQPZP0GDYN3SYY9SZZHFJE","Joshua Hayes","01M7EQPZPQKJDZR99NG512A8X2",1,"MIT","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fjbus\u002Fproject-skill\u002Fverify-main-red\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: verify-main-red\ndescription: Check main's red: the walk of main.json's contract and MainRed.tla; use when changing mainmoved, mainjson, jbus.reverts, culprits, watch's red steps or Repo.again.\npaths: \"features\u002Fjbus\u002Fspec\u002FMainRed.tla, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py, features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fmainjson.py, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwatch.py, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fculprits.py, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Freverts.py, features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Freverts.py, features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fcli.py, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fpoll.py, features\u002Fjsettings\u002Fsrc\u002Fjsettings\u002Fstore.py, features\u002Fjmerge\u002Fdocs\u002Fjmerge\u002Fwhat-ready-means.md\"\n---\n\n# verify-main-red\n\n`main.json` in a jbus project's state is the one record of main's red tip.\n`mainmoved.tell` (`features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py`) is its only writer, once a pass, and builds each record with `jmerge.mainjson.record`; `mainjson.of` (`features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fmainjson.py`) reads it.\nA red main holds no pull request, so the record stops no merge.\n`jmerge.cli.Repo.again` reads it to ask GitHub for no merge of a red main into a red pull request, and `jbus.culprits` reads its `failed` to tell a flake from a culprit's own red (`jbus.reverts`).\nA test runs the orders someone wrote down.\nThis check runs every order of merges, check answers, reruns and passes within its bounds, through the real `tell` and the real `mainjson.read`, and checks four properties after every pass:\n\n- **S1, a known red is read as red.**\n  When the newest tip whose check has settled (`green` or `failed`, `mainjson.SETTLED`) failed, `read` names a red tip.\n  Broken, jmerge merges a red main into each red pull request, and each one goes red again.\n- **S2, no stuck red.**\n  When `read` names a tip, no tip that landed after it has a `green` check.\n  Broken, a pull request red over the old red is never judged again after main was fixed.\n- **S3, the red tip's own tests.**\n  When the record keeps `failed` beside `broken`, those are the tests that failed at that tip.\n  Broken, `jbus.reverts` judges a red tip by another tip's tests, so a revert is a wrong one or a culprit escapes.\n- **S4, each red judged once.**\n  `main-reds.jsonl` (`mainmoved.REDS`), the ledger of reds `tell` writes, has a line for the red tip the record names, with that tip's own tests, and no tip has two lines.\n  Broken, a spell of main's red reads `unjudged` and counts as a change failure whatever caused it, or two lines give one red two causes.\n\nThe model is `features\u002Fjbus\u002Ftests\u002Fmain_red_model.py`, standard library only (a `collections.deque` walk, states kept by a `json` key).\nIts docstring says what each step is, the code line that backs it, what is stubbed and what is not covered.\n`tell` reads no pull request and sends no message, so the model has neither.\n\n## The record\n\nTwo checks share this record, and one sha confirms both: `main_red_model.py` walks the real `tell` and `mainjson.read`, and `features\u002Fjbus\u002Fspec\u002FMainRed.tla` models the wider red, from the rerun through the revert or the fix row to the close.\n\nModel: `features\u002Fjbus\u002Fspec\u002FMainRed.tla`\nSync: `2fb4e2587489ad3fbebf71561ac648801edb710f`\nCovers:\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py`: `tell`, `main_check`, `failed_at`, `failed_steps`, `red_line`, `REDS`, `landed`, `close`, `closing_line`, `spell`\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fmainjson.py`: `record`, `read`, `fix_of`, `FIX`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwatch.py`: `_check`, `_rerun_failed`, `RERUN_WAIT`, `mac_check`, `retro`, `RedTip`, `_withdraw`, `_file`, `_same_red`, `_open_reds`, `FIX_GOES`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fculprits.py`: `judge`, `kept_why`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Freverts.py`: `culprit`, `Keep`, `tested`, `covered`, `revert`, `lean`, `holders`, `_keep`, `stuck`, `close`, `cleared`, `over`, `macos`, `_mac_red`, `MAC_WALK`, `READ_WAIT`\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Freverts.py`: `read`\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fcli.py`: `Repo.again`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fpoll.py`: `steps`, `first_half`, `second_half`\n- `features\u002Fjsettings\u002Fsrc\u002Fjsettings\u002Fstore.py`: `write_json`\n- `features\u002Fjmerge\u002Fdocs\u002Fjmerge\u002Fwhat-ready-means.md`: `Main is not red`\n\nAt the sync commit `MainRed.tla` was read against these: `culprit`'s order of checks, then `tested` and `covered`; `OPENED` taking the newest revert and `stuck`; `lean` adding to the newest revert only; `close` skipping a revert not yet open, closing once all holders passed even while main is red, and dropping the record only with main green and every check in `greens`; the pass order 9, 10, 11, 12, 13; `retro` handing over the tip only at `main.red`; `_rerun_failed` asking for a rerun only at the tip; `_withdraw` and `_file`.\nThe two things the walk rests on outside the code were read there too: `write_json` writes a whole record through `os.replace`, and the rule the walk checks is the \"Main is not red\" line of `what-ready-means.md`.\nThe walk of `main_red_model.py` was rerun there and passes as below.\n`features\u002Frepo-guards\u002Ftests\u002Ftest_model_sync.py` fails when a file or name above is gone.\nMove `Sync:` forward only after you read every change to these files since it against both models, as `\u002Fmaintain-formal-verification-skill` says, and never because a check passes.\n\n### MainRed.tla\n\nThe rules beyond S1 to S4, each with its harm:\n\n- **`NeverRevertedTwice`:** jbus never opens a second revert of a commit.\n  Broken, as on 2026-11-09 (#1426 closed, then #1427 opened by the Mac at the same commit), one culprit is reverted twice.\n- **`OneRevertOpen`:** main's check waits on at most one of jbus's open reverts.\n- **`RedEndsOnlyByAMerge`:** a red whose code is broken ends only at a green commit a later merge made.\n- `KnownRedReadAsRed`, `NoStuckRed`, `RedTipsOwnTests` and `EachRedJudgedOnce` are S1 to S4 below, as the state a pass leaves; `test_main_red_spec.py` checks the spec states each one the walk checks.\n\n```sh\nuv run pytest features\u002Fjbus\u002Ftests\u002Ftest_main_red_spec.py -q\n```\n\nIt prints `6 passed` in seconds, and skips where no Java runs TLC; TLC's verdict may come from the statechart tools' cache (`tools.kept`), so to see TLC run, use the bare command in `features\u002Fjbus\u002Fspec\u002FMainRed.md`, \"Check the rules of main's red\", in a copy of the folder.\n\n- **Bounds:** `MainRed.cfg` is `MaxTips = 4` with no Mac (`Mac = FALSE`), 147,834 distinct states; `MainRed.chart.cfg` is `MaxTips = 3` with the Mac, 116,957 states.\n- **The canary:** `Fault = \"opener-only\"` on `MainRed.chart.cfg` is a revert held by the check that opened it alone, and `NeverRevertedTwice` breaks.\n  `BREAKS`, the rules today's code breaks, is empty.\n- **Assumptions:** two rows and an outside push; no cancelled, batched or job-less run; logs always readable; skew or no answer files the row at once; whether a culprit's slug is `over` is folded; `main-reds.jsonl` keeps only each pass's red tip; no browser run; the Mac's rerun is folded into its run, and its `tested`, `covered` and `flaky` checks are left out.\n  The rest is in the README's \"What the main-red model leaves out\".\n- **A trace:** each condition of a step quotes its code; open each quote, and a step the code cannot take is a modeling error.\n  When every step is backed, tell it as the merges, runs, reruns and passes in the code's words.\n\n### The last upkeep\n\n`\u002Fmaintain-formal-verification-skill` ran at `228c1436c` (st-model-upkeep-run) and fixed three drifts in `MainRed.tla`; the walk of `main_red_model.py` was rerun there and holds (`9 passed`):\n\n- **The closing lines:** `reds` holds the verdict lines, each with the green it came after, and `closing` the closing lines `mainmoved.close` appends when a green past the last one ends a spell, once a spell.\n  `tell`'s `judged` reads every line's sha, a closing line's too.\n  `EachRedJudgedOnce` now matches the walk's S4: verdict lines name no tip twice and name the red tip, and closing lines close no spell twice, each of a tip a verdict line names.\n  The old `EachRedJudgedOnce` passed on a description that had no closing lines.\n  The break: closing on every pass with a spell fails S4.\n  Dropping only the once guard passes, since the model's pass is one step and the guard is for a pass that dies between `close` and `main.json`; the README says so.\n- **The Mac's pending commit:** a commit of the Mac's range whose run has not ended is quiet (`UNREAD`), and the model has no clock and no Mac row for its later `OVERLAP`.\n- **Stale prose:** the spec and README no longer name main 21112eba8.\n\nThe row was then rebased onto st-model-sync, whose merge of main brought main to `8f4c21b6f`, and the upkeep diffed the covered code again from `228c1436c` to it: `watch.py` changed in #1724, in `left`, and `jmerge.md` in #1715 and #1721, in the desk check's words and a conflict's line, none of them in what this model covers, so the sync commit moved there.\n\nst-model-sync then merged main again, to `2fb4e2587`, and the row was rebased onto it; the upkeep diffed the covered code from `8f4c21b6f`: no covered file changed, so the sync commit moved there.\n\n## Does a change touch it\n\nRerun it when the diff touches any of these:\n\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py` (`tell`, `main_check`, `failed_at`, `failed_steps`, `red_line`, `REDS`, `landed`, the `STEPS` slot);\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fmainjson.py` (`Record`, `record`, `SETTLED`, `of`, `read`, `typed`, `FIX`, `failures`);\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fcli.py` (`Repo.again`, which reads `main_state`) and `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Frows.py` (`main`);\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fculprits.py` (`kept_why`) where it reads `failed` for `jbus.reverts`;\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fpoll.py` where a pass runs `tell` in the `after-expedite` slot, or the pass lock (`store.locked`, whose `fcntl.flock` is in `features\u002Fjsettings\u002Fsrc\u002Fjsettings\u002Fstore.py`), and `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmerge.py`, where `merge.start` starts a pass's run of `jmerge` off the pass and `merge.keep` runs it, so a merge it makes lands at any point between and within passes;\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwatch.py` `_check` and `_judged`, the answers a tip's check can have;\n- `write_json` in `features\u002Fjsettings\u002Fsrc\u002Fjsettings\u002Fstore.py`: the model takes a read to see a whole record, which `os.replace` gives;\n- the \"Main is not red\" rule in `features\u002Fjmerge\u002Fdocs\u002Fjmerge\u002Fwhat-ready-means.md`;\n- for `MainRed.tla`, every file of the record above: `jbus.reverts` (a culprit, its revert, its holders, `lean`, `close`, `macos`), `culprits.judge`, `watch._check`, `retro`, `_file` and `_withdraw`, and `jmerge.reverts.read`; a change to how a revert or a fix row is filed write by write is `verify-main-fix`'s too;\n- a move of any of these modules: the model imports them and stubs by module attribute, so a move changes its imports and its stubs, and the check is rerun on the moved code (unit 6 moved `jbus.mainstate` to `jmerge.mainjson` with the same counts).\n\n`scripts\u002Fselect_tests.py` selects `features\u002Fjbus\u002Ftests\u002Ftest_main_red_model.py` for a change to `mainmoved.py`, `mainjson.py` or `features\u002Fjmerge\u002Fdocs\u002Fjmerge\u002Fwhat-ready-means.md`, through what the model imports and the path it names, so `make check-fast` runs it.\nRun it by hand anyway when you change the contract on purpose: what it prints is the point.\n\n## Run it\n\n```sh\nuv run pytest features\u002Fjbus\u002Ftests\u002Ftest_main_red_model.py -q\n```\n\nIt takes a few seconds (6,818 states in the widest world).\nOn the code as it is today it prints `10 passed`.\nTo print every world:\n\n```sh\nuv run python features\u002Fjbus\u002Ftests\u002Fmain_red_model.py\n```\n\nIt prints both worlds, how many states each walks, and for each property `holds` or the number of states that break it with a trace.\nOn the code as it is today, every order walks 6,818 states and one tip at a time walks 1,210, and S1 to S4 hold in both.\n\nThe model has two worlds:\n\n- **every order** (`Options()`): any merge, check answer, rerun or pass may come at any point, so a tip may land before a pass looked at the one under it.\n- **one tip at a time** (`Options(one_at_a_time=True)`): a tip lands only once the newest tip's check has settled and a pass has run since.\n\nThe tests and the world each walks:\n\n| Test | World | Today |\n|---|---|---|\n| `test_the_walk_reaches_every_event_the_model_has` | every order | passes: each event kind was reached |\n| `test_s1_a_failed_tip_seen_by_a_pass_is_read_as_red` | one tip at a time | passes |\n| `test_s1_a_failed_tip_is_read_as_red_whatever_lands_after_it` | every order | passes |\n| `test_s2_a_green_tip_seen_by_a_pass_ends_the_red` | one tip at a time | passes |\n| `test_s2_a_green_tip_ends_the_red_in_every_order` | every order | passes |\n| `test_s3_the_tests_kept_are_the_red_tip_s_own_one_at_a_time` | one tip at a time | passes |\n| `test_s3_the_tests_kept_are_the_red_tip_s_own_in_every_order` | every order | passes |\n| `test_s4_each_red_tip_has_one_line_in_the_ledger_one_at_a_time` | one tip at a time | passes |\n| `test_s4_each_red_tip_has_one_line_in_the_ledger_in_every_order` | every order | passes |\n| `test_the_skill_states_the_counts_the_walk_walks` | both | passes: the counts stated equal the counts walked |\n\nEach finding's world is cut from a world that passes, so a break there points at that finding's cause.\nS1 holds one tip at a time, so S1 breaking over every order needs a tip no pass saw (F2).\nS2 holds one tip at a time, so S2 breaking over every order needs a tip no pass saw (F3).\n`tell` sends no message since it stopped telling crews, so the model has no T3 Code and no lost send, and F1 has no path left.\nA failure in any test is a new break.\n\n## The findings\n\nAll three are fixed: `tell` looks at every tip since its last pass (`landed`), and a pass takes a `fixed` it finds in the record as the end of the red.\nF1's cause, a send T3 Code lost, is gone with the message: `tell` writes no `fixed` now, and reads one only in a record written before.\nThe line numbers below are of the code before the fix (`fa810ec`).\n\n- **F1 (S2), retired.**\n  A green tip whose message T3 Code lost wrote only `fixed`, and the next pass, at a pending tip, wrote the old `broken` back.\n- **F2 (S1).**\n  A tip that fails and is followed by another before a pass looks at it was never kept as `broken`: `broken` came from the newest tip's own check.\n  With the newest pending, `read` named no red tip.\n- **F3 (S2).**\n  The mirror of F2: a green tip followed by another before a pass looks at it was never seen, so `broken` stayed while the newest tip was pending.\n  F2 and F3 had one cause, `tell` reading the newest tip only.\n\n## Read a trace\n\nA trace is the shortest order of events to the first state that breaks the property, numbered from `start`.\nTips are `M0` (green, there from the start) to `M3`; a record is printed with its commits as those names and without `at`.\nFor example, with the scratch break `green, waiting, unrun, under = tip, [], \"\", tip` for `green, broken, waiting, unrun, under = tip, \"\", [], \"\", tip` in `tell`'s `check == \"green\"` branch, every order prints:\n\n```\nS2 breaks in 172 of 7247 states (Options(one_at_a_time=False)), against \"Main is not red\" in features\u002Fjmerge\u002Fdocs\u002Fjmerge\u002Fwhat-ready-means.md\n  1. start: M0 is green, no main.json\n  2. M1 lands: a merge\n  3. M1's check settles: failed\n  4. pass: tell writes main.json {\"broken\": \"M1\", \"check\": \"failed\", \"failed\": [\"features\u002Fm\u002Ftests\u002Ftest_m.py::test_M1\"], \"main\": \"M1\"}; mainjson reads red=M1 green=-\n  5. M1's check is rerun and passes\n  6. M2 lands: a merge\n  7. pass: tell writes main.json {\"broken\": \"M1\", \"check\": \"pending\", \"failed\": [\"features\u002Fm\u002Ftests\u002Ftest_m.py::test_M1\"], \"green\": \"M1\", \"main\": \"M2\", \"pending\": [\"M2\"]}; mainjson reads red=M1 green=M1\n```\n\nThe record after a `pass` is what the real `tell` wrote; `red` and `green` are what the real `mainjson.read` gives.\nOne tip at a time, the same break holds, since a pass at a green newest tip clears `broken` before the loop.\n\n## A real bug or a modeling error\n\nEach step of a trace must be backed by code.\nCheck every step against this table; a step no line backs is a modeling error, and the model is what gets fixed:\n\n| Step | Backed by |\n|---|---|\n| `pass` | one `tell` under the pass lock, `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fpoll.py`, in the `after-expedite` slot, `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py` |\n| `Mn lands: a merge` | a merge by `jmerge`: by hand, by `--accept`, by the merge tick, or by a pass's run, which `merge.start` starts off the pass and `merge.keep` runs. No read of the record stops one, and none waits for a pass, so a merge lands at any point between and within passes, `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmerge.py` |\n| `Mn's check settles: \u003Canswer>` | an answer `watch._check` gives, `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwatch.py`; `pending` is a check not ended |\n| `Mn's check is rerun and passes` | a rerun of a failed check on the same tip, which `main_check` asks again about (`again=tip in (main, stands)`), `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py` |\n\nThe stubs are the other place a model can lie: `mainmoved.main_check`, `mainmoved.failed_at`, `mainmoved.failed_steps` and `mainmoved.account` (`stubbed()` in the model), and `FakePass.run`'s answer to GitHub's list of main's commits, which `landed` asks for.\nIf one of them is no longer what `tell` calls, the step it stands for is not the code's.\n`mock.patch.object` fails on an attribute that is gone, but a name `tell` imports with `from ... import` is not patched by a module attribute: then the real function runs and asks GitHub.\n\nWhen every step is backed, the trace is a real bug: report it with the trace, in the code's words, and leave the property as it is (\"Findings stay findings\").\n\n## Change the model when the contract changes on purpose\n\n- **A fix lands for a finding.**\n  A finding the walk finds is a strict `xfail` until it is fixed, and its test fails as `XPASS(strict)` once the fix lands: remove that `xfail` mark, and run again to see it pass.\n- **`main.json` gets a new key, or `mainjson.of` reads it differently.**\n  The model writes and reads the real files and keys its states on the whole record, so nothing in it changes unless a new input reaches `tell`: model that input as a new event in `steps`, with its code line in the docstring.\n- **A new input reaches `tell`**: add it to `State`, give it events in `steps`, add its kind to `test_the_walk_reaches_every_event_the_model_has`, and say it in the docstring's scope.\n  Raise `TIPS` or `EVENTS` only with the run time measured again.\n- **A module moves** (as unit 6 moved `jbus.mainstate` to `jmerge.mainjson`): change the model's imports and the stub targets to the new module, rerun, and expect the same counts.\n  Different counts after a pure move mean the move changed behavior.\n- **The property changes.**\n  Change `s1`, `s2`, `s3` or `s4` and the sentence in the docstring and here, and show the new property failing on a scratch break before trusting a pass: break the line it guards in your own worktree, uncommitted, run the check, see the trace, `git restore` the file, and see the check back at `10 passed` (or the new count).\n\nTwo breaks it was shown to catch on the code before the fix, on 2026-10-20: `if False:` for `if check == \"failed\":` in `mainmoved.py` breaks S1 in the one-tip-at-a-time world (a failed M1 seen by a pass, then M2 lands pending and the pass drops the red), and `if broken:` in `mainmoved.py` breaks S2 (the pass at green M2 keeps `broken: M1`, and the pass at pending M3 reads red again).\nOn the fixed code, dropping `broken, waiting, unrun = tip, [], \"\"` for `waiting, unrun = [], \"\"` in `mainmoved.py` breaks S1 one tip at a time and over every order.\nDropping `was.get(\"fixed\") or` in `mainmoved.py` passes the walk, since the model writes no `fixed`, and fails `test_a_record_left_owing_a_message_ends_the_red_at_its_fixed_tip` in `features\u002Fjbus\u002Ftests\u002Ftest_jbus_main_moved.py`, an older record with `fixed` where GitHub lists no tips.\nA break it was shown to catch on the code as it is today, on 2026-11-03: dropping `broken` from `green, broken, waiting, unrun = tip, \"\", [], \"\"` in `mainmoved.py` breaks S2 over every order (the trace above).\nA break S4 was shown to catch, on 2026-11-10: dropping `tip not in judged and` from `if tip not in judged and (read := failed_at(run, tip)) is not None:` in `mainmoved.tell` breaks S4 one tip at a time and over every order, since a second pass at a failed M1 writes M1's line to `main-reds.jsonl` again.\n","# verify-main-red\n\n`main.json` in a jbus project's state is the one record of main's red tip.\n`mainmoved.tell` (`features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py`) is its only writer, once a pass, and builds each record with `jmerge.mainjson.record`; `mainjson.of` (`features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fmainjson.py`) reads it.\nA red main holds no pull request, so the record stops no merge.\n`jmerge.cli.Repo.again` reads it to ask GitHub for no merge of a red main into a red pull request, and `jbus.culprits` reads its `failed` to tell a flake from a culprit's own red (`jbus.reverts`).\nA test runs the orders someone wrote down.\nThis check runs every order of merges, check answers, reruns and passes within its bounds, through the real `tell` and the real `mainjson.read`, and checks four properties after every pass:\n\n- **S1, a known red is read as red.**\n  When the newest tip whose check has settled (`green` or `failed`, `mainjson.SETTLED`) failed, `read` names a red tip.\n  Broken, jmerge merges a red main into each red pull request, and each one goes red again.\n- **S2, no stuck red.**\n  When `read` names a tip, no tip that landed after it has a `green` check.\n  Broken, a pull request red over the old red is never judged again after main was fixed.\n- **S3, the red tip's own tests.**\n  When the record keeps `failed` beside `broken`, those are the tests that failed at that tip.\n  Broken, `jbus.reverts` judges a red tip by another tip's tests, so a revert is a wrong one or a culprit escapes.\n- **S4, each red judged once.**\n  `main-reds.jsonl` (`mainmoved.REDS`), the ledger of reds `tell` writes, has a line for the red tip the record names, with that tip's own tests, and no tip has two lines.\n  Broken, a spell of main's red reads `unjudged` and counts as a change failure whatever caused it, or two lines give one red two causes.\n\nThe model is `features\u002Fjbus\u002Ftests\u002Fmain_red_model.py`, standard library only (a `collections.deque` walk, states kept by a `json` key).\nIts docstring says what each step is, the code line that backs it, what is stubbed and what is not covered.\n`tell` reads no pull request and sends no message, so the model has neither.\n\n## The record\n\nTwo checks share this record, and one sha confirms both: `main_red_model.py` walks the real `tell` and `mainjson.read`, and `features\u002Fjbus\u002Fspec\u002FMainRed.tla` models the wider red, from the rerun through the revert or the fix row to the close.\n\nModel: `features\u002Fjbus\u002Fspec\u002FMainRed.tla`\nSync: `2fb4e2587489ad3fbebf71561ac648801edb710f`\nCovers:\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py`: `tell`, `main_check`, `failed_at`, `failed_steps`, `red_line`, `REDS`, `landed`, `close`, `closing_line`, `spell`\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fmainjson.py`: `record`, `read`, `fix_of`, `FIX`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwatch.py`: `_check`, `_rerun_failed`, `RERUN_WAIT`, `mac_check`, `retro`, `RedTip`, `_withdraw`, `_file`, `_same_red`, `_open_reds`, `FIX_GOES`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fculprits.py`: `judge`, `kept_why`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Freverts.py`: `culprit`, `Keep`, `tested`, `covered`, `revert`, `lean`, `holders`, `_keep`, `stuck`, `close`, `cleared`, `over`, `macos`, `_mac_red`, `MAC_WALK`, `READ_WAIT`\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Freverts.py`: `read`\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fcli.py`: `Repo.again`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fpoll.py`: `steps`, `first_half`, `second_half`\n- `features\u002Fjsettings\u002Fsrc\u002Fjsettings\u002Fstore.py`: `write_json`\n- `features\u002Fjmerge\u002Fdocs\u002Fjmerge\u002Fwhat-ready-means.md`: `Main is not red`\n\nAt the sync commit `MainRed.tla` was read against these: `culprit`'s order of checks, then `tested` and `covered`; `OPENED` taking the newest revert and `stuck`; `lean` adding to the newest revert only; `close` skipping a revert not yet open, closing once all holders passed even while main is red, and dropping the record only with main green and every check in `greens`; the pass order 9, 10, 11, 12, 13; `retro` handing over the tip only at `main.red`; `_rerun_failed` asking for a rerun only at the tip; `_withdraw` and `_file`.\nThe two things the walk rests on outside the code were read there too: `write_json` writes a whole record through `os.replace`, and the rule the walk checks is the \"Main is not red\" line of `what-ready-means.md`.\nThe walk of `main_red_model.py` was rerun there and passes as below.\n`features\u002Frepo-guards\u002Ftests\u002Ftest_model_sync.py` fails when a file or name above is gone.\nMove `Sync:` forward only after you read every change to these files since it against both models, as `\u002Fmaintain-formal-verification-skill` says, and never because a check passes.\n\n### MainRed.tla\n\nThe rules beyond S1 to S4, each with its harm:\n\n- **`NeverRevertedTwice`:** jbus never opens a second revert of a commit.\n  Broken, as on 2026-11-09 (#1426 closed, then #1427 opened by the Mac at the same commit), one culprit is reverted twice.\n- **`OneRevertOpen`:** main's check waits on at most one of jbus's open reverts.\n- **`RedEndsOnlyByAMerge`:** a red whose code is broken ends only at a green commit a later merge made.\n- `KnownRedReadAsRed`, `NoStuckRed`, `RedTipsOwnTests` and `EachRedJudgedOnce` are S1 to S4 below, as the state a pass leaves; `test_main_red_spec.py` checks the spec states each one the walk checks.\n\n```sh\nuv run pytest features\u002Fjbus\u002Ftests\u002Ftest_main_red_spec.py -q\n```\n\nIt prints `6 passed` in seconds, and skips where no Java runs TLC; TLC's verdict may come from the statechart tools' cache (`tools.kept`), so to see TLC run, use the bare command in `features\u002Fjbus\u002Fspec\u002FMainRed.md`, \"Check the rules of main's red\", in a copy of the folder.\n\n- **Bounds:** `MainRed.cfg` is `MaxTips = 4` with no Mac (`Mac = FALSE`), 147,834 distinct states; `MainRed.chart.cfg` is `MaxTips = 3` with the Mac, 116,957 states.\n- **The canary:** `Fault = \"opener-only\"` on `MainRed.chart.cfg` is a revert held by the check that opened it alone, and `NeverRevertedTwice` breaks.\n  `BREAKS`, the rules today's code breaks, is empty.\n- **Assumptions:** two rows and an outside push; no cancelled, batched or job-less run; logs always readable; skew or no answer files the row at once; whether a culprit's slug is `over` is folded; `main-reds.jsonl` keeps only each pass's red tip; no browser run; the Mac's rerun is folded into its run, and its `tested`, `covered` and `flaky` checks are left out.\n  The rest is in the README's \"What the main-red model leaves out\".\n- **A trace:** each condition of a step quotes its code; open each quote, and a step the code cannot take is a modeling error.\n  When every step is backed, tell it as the merges, runs, reruns and passes in the code's words.\n\n### The last upkeep\n\n`\u002Fmaintain-formal-verification-skill` ran at `228c1436c` (st-model-upkeep-run) and fixed three drifts in `MainRed.tla`; the walk of `main_red_model.py` was rerun there and holds (`9 passed`):\n\n- **The closing lines:** `reds` holds the verdict lines, each with the green it came after, and `closing` the closing lines `mainmoved.close` appends when a green past the last one ends a spell, once a spell.\n  `tell`'s `judged` reads every line's sha, a closing line's too.\n  `EachRedJudgedOnce` now matches the walk's S4: verdict lines name no tip twice and name the red tip, and closing lines close no spell twice, each of a tip a verdict line names.\n  The old `EachRedJudgedOnce` passed on a description that had no closing lines.\n  The break: closing on every pass with a spell fails S4.\n  Dropping only the once guard passes, since the model's pass is one step and the guard is for a pass that dies between `close` and `main.json`; the README says so.\n- **The Mac's pending commit:** a commit of the Mac's range whose run has not ended is quiet (`UNREAD`), and the model has no clock and no Mac row for its later `OVERLAP`.\n- **Stale prose:** the spec and README no longer name main 21112eba8.\n\nThe row was then rebased onto st-model-sync, whose merge of main brought main to `8f4c21b6f`, and the upkeep diffed the covered code again from `228c1436c` to it: `watch.py` changed in #1724, in `left`, and `jmerge.md` in #1715 and #1721, in the desk check's words and a conflict's line, none of them in what this model covers, so the sync commit moved there.\n\nst-model-sync then merged main again, to `2fb4e2587`, and the row was rebased onto it; the upkeep diffed the covered code from `8f4c21b6f`: no covered file changed, so the sync commit moved there.\n\n## Does a change touch it\n\nRerun it when the diff touches any of these:\n\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py` (`tell`, `main_check`, `failed_at`, `failed_steps`, `red_line`, `REDS`, `landed`, the `STEPS` slot);\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fmainjson.py` (`Record`, `record`, `SETTLED`, `of`, `read`, `typed`, `FIX`, `failures`);\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fcli.py` (`Repo.again`, which reads `main_state`) and `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Frows.py` (`main`);\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fculprits.py` (`kept_why`) where it reads `failed` for `jbus.reverts`;\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fpoll.py` where a pass runs `tell` in the `after-expedite` slot, or the pass lock (`store.locked`, whose `fcntl.flock` is in `features\u002Fjsettings\u002Fsrc\u002Fjsettings\u002Fstore.py`), and `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmerge.py`, where `merge.start` starts a pass's run of `jmerge` off the pass and `merge.keep` runs it, so a merge it makes lands at any point between and within passes;\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwatch.py` `_check` and `_judged`, the answers a tip's check can have;\n- `write_json` in `features\u002Fjsettings\u002Fsrc\u002Fjsettings\u002Fstore.py`: the model takes a read to see a whole record, which `os.replace` gives;\n- the \"Main is not red\" rule in `features\u002Fjmerge\u002Fdocs\u002Fjmerge\u002Fwhat-ready-means.md`;\n- for `MainRed.tla`, every file of the record above: `jbus.reverts` (a culprit, its revert, its holders, `lean`, `close`, `macos`), `culprits.judge`, `watch._check`, `retro`, `_file` and `_withdraw`, and `jmerge.reverts.read`; a change to how a revert or a fix row is filed write by write is `verify-main-fix`'s too;\n- a move of any of these modules: the model imports them and stubs by module attribute, so a move changes its imports and its stubs, and the check is rerun on the moved code (unit 6 moved `jbus.mainstate` to `jmerge.mainjson` with the same counts).\n\n`scripts\u002Fselect_tests.py` selects `features\u002Fjbus\u002Ftests\u002Ftest_main_red_model.py` for a change to `mainmoved.py`, `mainjson.py` or `features\u002Fjmerge\u002Fdocs\u002Fjmerge\u002Fwhat-ready-means.md`, through what the model imports and the path it names, so `make check-fast` runs it.\nRun it by hand anyway when you change the contract on purpose: what it prints is the point.\n\n## Run it\n\n```sh\nuv run pytest features\u002Fjbus\u002Ftests\u002Ftest_main_red_model.py -q\n```\n\nIt takes a few seconds (6,818 states in the widest world).\nOn the code as it is today it prints `10 passed`.\nTo print every world:\n\n```sh\nuv run python features\u002Fjbus\u002Ftests\u002Fmain_red_model.py\n```\n\nIt prints both worlds, how many states each walks, and for each property `holds` or the number of states that break it with a trace.\nOn the code as it is today, every order walks 6,818 states and one tip at a time walks 1,210, and S1 to S4 hold in both.\n\nThe model has two worlds:\n\n- **every order** (`Options()`): any merge, check answer, rerun or pass may come at any point, so a tip may land before a pass looked at the one under it.\n- **one tip at a time** (`Options(one_at_a_time=True)`): a tip lands only once the newest tip's check has settled and a pass has run since.\n\nThe tests and the world each walks:\n\n| Test | World | Today |\n|---|---|---|\n| `test_the_walk_reaches_every_event_the_model_has` | every order | passes: each event kind was reached |\n| `test_s1_a_failed_tip_seen_by_a_pass_is_read_as_red` | one tip at a time | passes |\n| `test_s1_a_failed_tip_is_read_as_red_whatever_lands_after_it` | every order | passes |\n| `test_s2_a_green_tip_seen_by_a_pass_ends_the_red` | one tip at a time | passes |\n| `test_s2_a_green_tip_ends_the_red_in_every_order` | every order | passes |\n| `test_s3_the_tests_kept_are_the_red_tip_s_own_one_at_a_time` | one tip at a time | passes |\n| `test_s3_the_tests_kept_are_the_red_tip_s_own_in_every_order` | every order | passes |\n| `test_s4_each_red_tip_has_one_line_in_the_ledger_one_at_a_time` | one tip at a time | passes |\n| `test_s4_each_red_tip_has_one_line_in_the_ledger_in_every_order` | every order | passes |\n| `test_the_skill_states_the_counts_the_walk_walks` | both | passes: the counts stated equal the counts walked |\n\nEach finding's world is cut from a world that passes, so a break there points at that finding's cause.\nS1 holds one tip at a time, so S1 breaking over every order needs a tip no pass saw (F2).\nS2 holds one tip at a time, so S2 breaking over every order needs a tip no pass saw (F3).\n`tell` sends no message since it stopped telling crews, so the model has no T3 Code and no lost send, and F1 has no path left.\nA failure in any test is a new break.\n\n## The findings\n\nAll three are fixed: `tell` looks at every tip since its last pass (`landed`), and a pass takes a `fixed` it finds in the record as the end of the red.\nF1's cause, a send T3 Code lost, is gone with the message: `tell` writes no `fixed` now, and reads one only in a record written before.\nThe line numbers below are of the code before the fix (`fa810ec`).\n\n- **F1 (S2), retired.**\n  A green tip whose message T3 Code lost wrote only `fixed`, and the next pass, at a pending tip, wrote the old `broken` back.\n- **F2 (S1).**\n  A tip that fails and is followed by another before a pass looks at it was never kept as `broken`: `broken` came from the newest tip's own check.\n  With the newest pending, `read` named no red tip.\n- **F3 (S2).**\n  The mirror of F2: a green tip followed by another before a pass looks at it was never seen, so `broken` stayed while the newest tip was pending.\n  F2 and F3 had one cause, `tell` reading the newest tip only.\n\n## Read a trace\n\nA trace is the shortest order of events to the first state that breaks the property, numbered from `start`.\nTips are `M0` (green, there from the start) to `M3`; a record is printed with its commits as those names and without `at`.\nFor example, with the scratch break `green, waiting, unrun, under = tip, [], \"\", tip` for `green, broken, waiting, unrun, under = tip, \"\", [], \"\", tip` in `tell`'s `check == \"green\"` branch, every order prints:\n\n```\nS2 breaks in 172 of 7247 states (Options(one_at_a_time=False)), against \"Main is not red\" in features\u002Fjmerge\u002Fdocs\u002Fjmerge\u002Fwhat-ready-means.md\n  1. start: M0 is green, no main.json\n  2. M1 lands: a merge\n  3. M1's check settles: failed\n  4. pass: tell writes main.json {\"broken\": \"M1\", \"check\": \"failed\", \"failed\": [\"features\u002Fm\u002Ftests\u002Ftest_m.py::test_M1\"], \"main\": \"M1\"}; mainjson reads red=M1 green=-\n  5. M1's check is rerun and passes\n  6. M2 lands: a merge\n  7. pass: tell writes main.json {\"broken\": \"M1\", \"check\": \"pending\", \"failed\": [\"features\u002Fm\u002Ftests\u002Ftest_m.py::test_M1\"], \"green\": \"M1\", \"main\": \"M2\", \"pending\": [\"M2\"]}; mainjson reads red=M1 green=M1\n```\n\nThe record after a `pass` is what the real `tell` wrote; `red` and `green` are what the real `mainjson.read` gives.\nOne tip at a time, the same break holds, since a pass at a green newest tip clears `broken` before the loop.\n\n## A real bug or a modeling error\n\nEach step of a trace must be backed by code.\nCheck every step against this table; a step no line backs is a modeling error, and the model is what gets fixed:\n\n| Step | Backed by |\n|---|---|\n| `pass` | one `tell` under the pass lock, `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fpoll.py`, in the `after-expedite` slot, `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py` |\n| `Mn lands: a merge` | a merge by `jmerge`: by hand, by `--accept`, by the merge tick, or by a pass's run, which `merge.start` starts off the pass and `merge.keep` runs. No read of the record stops one, and none waits for a pass, so a merge lands at any point between and within passes, `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmerge.py` |\n| `Mn's check settles: \u003Canswer>` | an answer `watch._check` gives, `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwatch.py`; `pending` is a check not ended |\n| `Mn's check is rerun and passes` | a rerun of a failed check on the same tip, which `main_check` asks again about (`again=tip in (main, stands)`), `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmainmoved.py` |\n\nThe stubs are the other place a model can lie: `mainmoved.main_check`, `mainmoved.failed_at`, `mainmoved.failed_steps` and `mainmoved.account` (`stubbed()` in the model), and `FakePass.run`'s answer to GitHub's list of main's commits, which `landed` asks for.\nIf one of them is no longer what `tell` calls, the step it stands for is not the code's.\n`mock.patch.object` fails on an attribute that is gone, but a name `tell` imports with `from ... import` is not patched by a module attribute: then the real function runs and asks GitHub.\n\nWhen every step is backed, the trace is a real bug: report it with the trace, in the code's words, and leave the property as it is (\"Findings stay findings\").\n\n## Change the model when the contract changes on purpose\n\n- **A fix lands for a finding.**\n  A finding the walk finds is a strict `xfail` until it is fixed, and its test fails as `XPASS(strict)` once the fix lands: remove that `xfail` mark, and run again to see it pass.\n- **`main.json` gets a new key, or `mainjson.of` reads it differently.**\n  The model writes and reads the real files and keys its states on the whole record, so nothing in it changes unless a new input reaches `tell`: model that input as a new event in `steps`, with its code line in the docstring.\n- **A new input reaches `tell`**: add it to `State`, give it events in `steps`, add its kind to `test_the_walk_reaches_every_event_the_model_has`, and say it in the docstring's scope.\n  Raise `TIPS` or `EVENTS` only with the run time measured again.\n- **A module moves** (as unit 6 moved `jbus.mainstate` to `jmerge.mainjson`): change the model's imports and the stub targets to the new module, rerun, and expect the same counts.\n  Different counts after a pure move mean the move changed behavior.\n- **The property changes.**\n  Change `s1`, `s2`, `s3` or `s4` and the sentence in the docstring and here, and show the new property failing on a scratch break before trusting a pass: break the line it guards in your own worktree, uncommitted, run the check, see the trace, `git restore` the file, and see the check back at `10 passed` (or the new count).\n\nTwo breaks it was shown to catch on the code before the fix, on 2026-10-20: `if False:` for `if check == \"failed\":` in `mainmoved.py` breaks S1 in the one-tip-at-a-time world (a failed M1 seen by a pass, then M2 lands pending and the pass drops the red), and `if broken:` in `mainmoved.py` breaks S2 (the pass at green M2 keeps `broken: M1`, and the pass at pending M3 reads red again).\nOn the fixed code, dropping `broken, waiting, unrun = tip, [], \"\"` for `waiting, unrun = [], \"\"` in `mainmoved.py` breaks S1 one tip at a time and over every order.\nDropping `was.get(\"fixed\") or` in `mainmoved.py` passes the walk, since the model writes no `fixed`, and fails `test_a_record_left_owing_a_message_ends_the_red_at_its_fixed_tip` in `features\u002Fjbus\u002Ftests\u002Ftest_jbus_main_moved.py`, an older record with `fixed` where GitHub lists no tips.\nA break it was shown to catch on the code as it is today, on 2026-11-03: dropping `broken` from `green, broken, waiting, unrun = tip, \"\", [], \"\"` in `mainmoved.py` breaks S2 over every order (the trace above).\nA break S4 was shown to catch, on 2026-11-10: dropping `tip not in judged and` from `if tip not in judged and (read := failed_at(run, tip)) is not None:` in `mainmoved.tell` breaks S4 one tip at a time and over every order, since a second pass at a failed M1 writes M1's line to `main-reds.jsonl` again.\n",{},"main","daff051d2674b46e2eb8a333bbd3f3e40f8d1cea","features\u002Fjbus\u002Fproject-skill\u002Fverify-main-red",0,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere","Software Engineer @ Markel\r\n","2026-11-15 11:25:06",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add JoshuaHayesWasHere\u002Fjstack --skill verify-main-red",{"tool":37,"command":38},"bunx","bunx skills add JoshuaHayesWasHere\u002Fjstack --skill verify-main-red",{"tool":40,"command":41},"pnpm","pnpm dlx skills add JoshuaHayesWasHere\u002Fjstack --skill verify-main-red","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fjbus\u002Fproject-skill\u002Fverify-main-red\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7ERF9GXMY62V7QTVAR6G8DG","no-key","A skill its skills.json lists as hidden that a model may still call by itself, kept broken so the lint is seen to catch it.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ftesting\u002Ftests\u002Ffixtures\u002Fskills\u002Fno-key\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7ERF83ZG3XKJ2SB8MJHCZ8H","fake-skill","A FAKE skill in a FAKE tree, named for its folder until the test renames the folder.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ftesting\u002Ftests\u002Ffixtures\u002Fskills\u002Fnamed-tree\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7ERF698RV4VF8QCDF8H8DA4","extra-key","A skill its skills.json does not list as hidden that a model still cannot call, kept broken so the lint is seen to catch it.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ftesting\u002Ftests\u002Ffixtures\u002Fskills\u002Fextra-key\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7ERF2V8N73X9T0Y9PJ4SFV6","unslop","Cut AI tells from writing. Use when the user says text reads like AI, asks to unslop it, or before prose ships to people.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwriting\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7EREWM67WX934XKABM4XCSZ","technical-writing","Write or review docs, READMEs, RFCs, PR descriptions and commit messages to a layered standard: Diataxis structure, Google developer style, STE rules and Global English.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwriting\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7EREMHJS9JY10AM5EKVX3GP","why","Find why code is the way it is, from its history and every evidence source this session can query, with citations. Use for 'why does X work this way', 'why did we pick Y', regressions and postmortems. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002FSKILL.md",[],[]]