[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EQWDD8Z6GDSF0B7JR5SWD8":3,"skill-same:01M7EQWDD8Z6GDSF0B7JR5SWD8":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7EQWDD8Z6GDSF0B7JR5SWD8","verify-home-tree-today",null,"Check HomeTreeToday.tla, today's code for the root and child homes; use when changing jbus\u002Fchildren.py, wakes, the merge run or lock, or the handoff block.","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\u002Fhome\u002Fproject-skill\u002Fverify-home-tree-today\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: verify-home-tree-today\ndescription: Check HomeTreeToday.tla, today's code for the root and child homes; use when changing jbus\u002Fchildren.py, wakes, the merge run or lock, or the handoff block.\npaths: \"features\u002Fhome\u002Fspec\u002FHomeTreeToday.tla, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fchildren.py, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwakes.py, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmerge.py, features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fcli.py, features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Flock.py, features\u002Fjbriefs\u002Fsrc\u002Fjbriefs\u002Fhome.py, features\u002Fhome\u002Fskills\u002Fhandoff\u002FSKILL.md\"\n---\n\n# verify-home-tree-today\n\n`features\u002Fhome\u002Fspec\u002FHomeTreeToday.tla` models today's code for a root home and two sibling child homes: child a does one feature and is archived, child b is a routine with a rhythm, each with a pull request, a crew thread and two calls to you, and a call reaches you through the root's home thread, which can fail.\nIt extends `HomeTree.tla`, which holds the variables, the start and the rules (`verify-home-tree`).\nEach condition names the file that checks it and quotes the code, and its constant `Drop` takes one guard out.\n\nThe rules are `HomeTree.tla`'s; their harms are in `verify-home-tree`.\nThis skill is for what the code does: when a step here stops being the code's, the rules are checked on code that no longer exists.\n\n## The record\n\nModel: `features\u002Fhome\u002Fspec\u002FHomeTreeToday.tla`\nSync: `2fb4e2587489ad3fbebf71561ac648801edb710f`\nCovers:\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fchildren.py`: `watch`, `_act`, `_stall`, `keep_alive`, `launch`, `_going`, `_failed`, `_waits`, `_stage`, `started`, `live`, `whose`, `watched`, `_rhythm`, `STAGES`, `FAILURE`, `PATIENCE`, `USERS`, `LAUNCHES`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwakes.py`: `need_items`, `pick`, `kept`, `_send`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmerge.py`: `start`, `keep`\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fcli.py`: `Repo.merge`, `Repo.merge_holding`\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Flock.py`: `MergeLock.take`, `MergeLock.give`\n- `features\u002Fjbriefs\u002Fsrc\u002Fjbriefs\u002Fhome.py`: `stands_in`\n- `features\u002Fhome\u002Fskills\u002Fhandoff\u002FSKILL.md`: `home-id`, `plan-archived.md`\n\nAt the sync commit every action's guards and quotes were read against these: `Acts`' timing against `children.watch`'s start (`last or since + patience*rank`), `keep_alive`, `_going`, `_failed` and `_waits` against `KeepAlive`, `StartEnds`, `StartWrites` and `CauseClears`, the merge lock against `merge_holding`, and the order of the handoff block.\nThe upkeep below fixed one of the three older mismatches and kept two as stated assumptions.\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 the model, as `\u002Fmaintain-formal-verification-skill` says, and never because the check passes.\n\n## Does a change touch it\n\nRerun it when the diff touches a file of the record, how a call or a gate reaches you, when a quiet home is nudged or launched again, or who may merge.\n`features\u002Fhome\u002Ftests\u002Ftest_home_tree_spec.py` fails when a quote of either spec no longer stands once in its file.\n\n## Run it\n\n```sh\nuv run pytest features\u002Fhome\u002Ftests\u002Ftest_home_tree_spec.py -q\n```\n\nIt runs the 30 runs of `canaries.py` (each rule in each scene, and each canary), the quote checks, and four tests that drive the real code along the stories the code once broke; it takes seconds when TLC's verdicts come from the statechart tools' cache (`tools.kept`), and skips where no Java runs TLC.\nBy hand, from the repo root:\n\n```sh\nuv run python features\u002Fhome\u002Fspec\u002Fcanaries.py\n```\n\nIt prints one line a run and ends 0 when every run says what it should.\n\n- **Bounds:** `K = 2`, `Rhythm = 1`; the scenes are `a` (child a alone with both calls and a home thread that can fail, 398,880 states), `b` (the same for child b, 237,780) and `siblings` (both children, no calls, a home thread that never fails, 280,108).\n  `HomeTreeToday.cfg`, the chart's scene, is child a with one call, `K = 1` and a home thread that never fails.\n- **The canaries** (`Drop`): `hand-over`, `keep-on-fail`, `flag`, `beat`, `needs`, `nudge-cap`, `relaunch-once`, `ask`, `one-merger`, `lock`, `all-homes`, `drop-release`, `keep-alive`, `going`, `waits`, each breaking the rule that rests on it; `canaries.py` names each one's rule and scene.\n- **Assumptions:** two children; a pull request drops at most once; the home thread fails at most once; a nudge and a launch are always sent; weak fairness on the steps that happen by themselves.\n  The rest is in `features\u002Fhome\u002Fspec\u002FHomeTreeToday.md`, \"What the model leaves out\".\n\n## A real bug or a modeling error\n\nEach condition quotes its code.\nOpen each quote of a trace at its file and check the code still guards the step as quoted; a step the code cannot take is a modeling error, and the model is what gets fixed.\nWhen every step is backed, it is a bug: tell it as the homes' story (a call, a nudge, a launch, a merge) in the code's words, and add a test that drives the real code along it, as `test_home_tree_spec.py` has for the four rules the code once broke.\n\n## Change the model when the code changes on purpose\n\n- A new guard: add it with a `Drop` value and a canary in `canaries.py` that breaks the rule it holds.\n- A change to how a call reaches you: model each route the code takes (see the last upkeep below), not one `up` flag.\n- Show a changed rule failing on a scratch break first (take the guard out in your own worktree, uncommitted, see the trace, `git restore` the file).\n\n## The last upkeep\n\n`\u002Fmaintain-formal-verification-skill` ran at `228c1436c` (st-model-upkeep-run): the covered code is unchanged from it to the row's first base, and the three older mismatches were settled from the code.\n\n- **Fixed, `RaiseCall`:** a call no longer calms the spell.\n  `children.watch` leaves calls out of the spell's signature (`USERS`), so a call is only a write of the child's home thread, which ends the spell only while it is `calm`.\n  Every rule still holds in every scene with the same states (398,880, 237,780, 280,108), and every canary still breaks its rule: `uv run pytest features\u002Fhome\u002Ftests\u002Ftest_home_tree_spec.py -q` printed `46 passed`.\n- **Kept as an assumption, a failed nudge or launch:** modeled, a send that fails while T3 Code is down leaves a quiet child `calm` past its patience, which `StallFlagged` forbids as worded, and a rule's words change only on the user's word.\n  The code tries again each pass, so the step is late, not lost.\n  The README's \"leaves out\" says so.\n- **Kept as an abstraction, one route to you:** `wakes.need_items` sends a child's gate to its own home thread, and approve, stalled, install and self-asked gates to no thread; the model's single `up` flag is every route, and the README's \"leaves out\" says so.\n- The spec's header no longer names main 21112eba8, and the README and `canaries.py` give `uv run python`.\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: no covered file changed, so the sync commit moved there; the chart's record was made to match its drawing again after the rebase.\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","# verify-home-tree-today\n\n`features\u002Fhome\u002Fspec\u002FHomeTreeToday.tla` models today's code for a root home and two sibling child homes: child a does one feature and is archived, child b is a routine with a rhythm, each with a pull request, a crew thread and two calls to you, and a call reaches you through the root's home thread, which can fail.\nIt extends `HomeTree.tla`, which holds the variables, the start and the rules (`verify-home-tree`).\nEach condition names the file that checks it and quotes the code, and its constant `Drop` takes one guard out.\n\nThe rules are `HomeTree.tla`'s; their harms are in `verify-home-tree`.\nThis skill is for what the code does: when a step here stops being the code's, the rules are checked on code that no longer exists.\n\n## The record\n\nModel: `features\u002Fhome\u002Fspec\u002FHomeTreeToday.tla`\nSync: `2fb4e2587489ad3fbebf71561ac648801edb710f`\nCovers:\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fchildren.py`: `watch`, `_act`, `_stall`, `keep_alive`, `launch`, `_going`, `_failed`, `_waits`, `_stage`, `started`, `live`, `whose`, `watched`, `_rhythm`, `STAGES`, `FAILURE`, `PATIENCE`, `USERS`, `LAUNCHES`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwakes.py`: `need_items`, `pick`, `kept`, `_send`\n- `features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmerge.py`: `start`, `keep`\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fcli.py`: `Repo.merge`, `Repo.merge_holding`\n- `features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Flock.py`: `MergeLock.take`, `MergeLock.give`\n- `features\u002Fjbriefs\u002Fsrc\u002Fjbriefs\u002Fhome.py`: `stands_in`\n- `features\u002Fhome\u002Fskills\u002Fhandoff\u002FSKILL.md`: `home-id`, `plan-archived.md`\n\nAt the sync commit every action's guards and quotes were read against these: `Acts`' timing against `children.watch`'s start (`last or since + patience*rank`), `keep_alive`, `_going`, `_failed` and `_waits` against `KeepAlive`, `StartEnds`, `StartWrites` and `CauseClears`, the merge lock against `merge_holding`, and the order of the handoff block.\nThe upkeep below fixed one of the three older mismatches and kept two as stated assumptions.\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 the model, as `\u002Fmaintain-formal-verification-skill` says, and never because the check passes.\n\n## Does a change touch it\n\nRerun it when the diff touches a file of the record, how a call or a gate reaches you, when a quiet home is nudged or launched again, or who may merge.\n`features\u002Fhome\u002Ftests\u002Ftest_home_tree_spec.py` fails when a quote of either spec no longer stands once in its file.\n\n## Run it\n\n```sh\nuv run pytest features\u002Fhome\u002Ftests\u002Ftest_home_tree_spec.py -q\n```\n\nIt runs the 30 runs of `canaries.py` (each rule in each scene, and each canary), the quote checks, and four tests that drive the real code along the stories the code once broke; it takes seconds when TLC's verdicts come from the statechart tools' cache (`tools.kept`), and skips where no Java runs TLC.\nBy hand, from the repo root:\n\n```sh\nuv run python features\u002Fhome\u002Fspec\u002Fcanaries.py\n```\n\nIt prints one line a run and ends 0 when every run says what it should.\n\n- **Bounds:** `K = 2`, `Rhythm = 1`; the scenes are `a` (child a alone with both calls and a home thread that can fail, 398,880 states), `b` (the same for child b, 237,780) and `siblings` (both children, no calls, a home thread that never fails, 280,108).\n  `HomeTreeToday.cfg`, the chart's scene, is child a with one call, `K = 1` and a home thread that never fails.\n- **The canaries** (`Drop`): `hand-over`, `keep-on-fail`, `flag`, `beat`, `needs`, `nudge-cap`, `relaunch-once`, `ask`, `one-merger`, `lock`, `all-homes`, `drop-release`, `keep-alive`, `going`, `waits`, each breaking the rule that rests on it; `canaries.py` names each one's rule and scene.\n- **Assumptions:** two children; a pull request drops at most once; the home thread fails at most once; a nudge and a launch are always sent; weak fairness on the steps that happen by themselves.\n  The rest is in `features\u002Fhome\u002Fspec\u002FHomeTreeToday.md`, \"What the model leaves out\".\n\n## A real bug or a modeling error\n\nEach condition quotes its code.\nOpen each quote of a trace at its file and check the code still guards the step as quoted; a step the code cannot take is a modeling error, and the model is what gets fixed.\nWhen every step is backed, it is a bug: tell it as the homes' story (a call, a nudge, a launch, a merge) in the code's words, and add a test that drives the real code along it, as `test_home_tree_spec.py` has for the four rules the code once broke.\n\n## Change the model when the code changes on purpose\n\n- A new guard: add it with a `Drop` value and a canary in `canaries.py` that breaks the rule it holds.\n- A change to how a call reaches you: model each route the code takes (see the last upkeep below), not one `up` flag.\n- Show a changed rule failing on a scratch break first (take the guard out in your own worktree, uncommitted, see the trace, `git restore` the file).\n\n## The last upkeep\n\n`\u002Fmaintain-formal-verification-skill` ran at `228c1436c` (st-model-upkeep-run): the covered code is unchanged from it to the row's first base, and the three older mismatches were settled from the code.\n\n- **Fixed, `RaiseCall`:** a call no longer calms the spell.\n  `children.watch` leaves calls out of the spell's signature (`USERS`), so a call is only a write of the child's home thread, which ends the spell only while it is `calm`.\n  Every rule still holds in every scene with the same states (398,880, 237,780, 280,108), and every canary still breaks its rule: `uv run pytest features\u002Fhome\u002Ftests\u002Ftest_home_tree_spec.py -q` printed `46 passed`.\n- **Kept as an assumption, a failed nudge or launch:** modeled, a send that fails while T3 Code is down leaves a quiet child `calm` past its patience, which `StallFlagged` forbids as worded, and a rule's words change only on the user's word.\n  The code tries again each pass, so the step is late, not lost.\n  The README's \"leaves out\" says so.\n- **Kept as an abstraction, one route to you:** `wakes.need_items` sends a child's gate to its own home thread, and approve, stalled, install and self-asked gates to no thread; the model's single `up` flag is every route, and the README's \"leaves out\" says so.\n- The spec's header no longer names main 21112eba8, and the README and `canaries.py` give `uv run python`.\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: no covered file changed, so the sync commit moved there; the chart's record was made to match its drawing again after the rebase.\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",{"name":5,"paths":24,"description":7},"features\u002Fhome\u002Fspec\u002FHomeTreeToday.tla, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fchildren.py, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fwakes.py, features\u002Fjbus\u002Fsrc\u002Fjbus\u002Fmerge.py, features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Fcli.py, features\u002Fjmerge\u002Fsrc\u002Fjmerge\u002Flock.py, features\u002Fjbriefs\u002Fsrc\u002Fjbriefs\u002Fhome.py, features\u002Fhome\u002Fskills\u002Fhandoff\u002FSKILL.md","main","daff051d2674b46e2eb8a333bbd3f3e40f8d1cea","features\u002Fhome\u002Fproject-skill\u002Fverify-home-tree-today",0,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere","Software Engineer @ Markel\r\n","2026-11-15 11:25:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add JoshuaHayesWasHere\u002Fjstack --skill verify-home-tree-today",{"tool":39,"command":40},"bunx","bunx skills add JoshuaHayesWasHere\u002Fjstack --skill verify-home-tree-today",{"tool":42,"command":43},"pnpm","pnpm dlx skills add JoshuaHayesWasHere\u002Fjstack --skill verify-home-tree-today","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fhome\u002Fproject-skill\u002Fverify-home-tree-today\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"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",[],[]]