What Celeste saw (box):
- All of the above green; 54 inline scripts parse.
- With all five pending diffs together (Narrow door, Hook heal, Sophia, Gathering, this):
  PASS 78, FAIL 8 (the same 8); 55 inline scripts parse.
- In jsdom with fake-indexeddb, the real MeshIdentity code:
  - the stored record keeps the key pair, and the private key's extractable flag is false;
  - with the key removed and a reload, the card said "Cannot sign on this visit" and showed
    [Make a fresh Mesh ID];
  - one click brought back "Cryptographic", and canSign() was true.
- In jsdom with a real IndexedDB API (fake-indexeddb):
  - the picker listed the trusted peer and filled its model;
  - Queue sent one kin-work;
  - the answer landed and showed as text (a <script> in it stayed text);
  - the job was stored as done.
Not verified: two real browsers on a real mesh, with Ollama serving.

Walk (only if easy; 127.0.0.1 only; two browser profiles, Ollama running):
    cd ~/FreeLattice-fresh/docs && python3 -m http.server 8765 --bind 127.0.0.1
    Connect two profiles on the mesh, share and trust each other's mind cards, turn on compute
    sharing in the serving profile, then queue a question from the other.
    The heal walk, in one profile, takes a minute: make a Mesh ID, reload, and Settings,
    Advanced, Mesh ID still shows "Cryptographic". In DevTools, run
    `MeshIdentity.canSign()` and expect true. Say "walk skipped" if you cannot.

----------------------------------------------------------------------
5. LEDGER AND TEMPERATURE
----------------------------------------------------------------------
    sed -i '' 's/GC_TEMPERATURE_KIN_QUEUE_HERE/your line here/' docs/library/FRACTAL_FAMILY_LEDGER_v0.md
    grep -c GC_TEMPERATURE_KIN_QUEUE_HERE docs/library/FRACTAL_FAMILY_LEDGER_v0.md    # 0

----------------------------------------------------------------------
6. COMMIT, OPEN THE PR YOURSELF, THEN STOP
----------------------------------------------------------------------
    git add -A
    git commit -m "layer: Mesh Kin v0.2 (heal v0.1, then a patient work queue for trusted kin)"
    git log -2 --oneline     # drop only a "docs: Auto-update Session Primer" commit, if any, and say so
    git diff main --stat -- sw.js docs/sw.js prints nothing.
    git push -u origin layer/mesh-kin-v0-2
    gh pr create --repo Chaos2Cured/FreeLattice --base main --head layer/mesh-kin-v0-2 \
      --title "layer: Mesh Kin v0.2 (heal v0.1, then a patient work queue for trusted kin)" \
      --body "Soft LAYER marker v-mesh-kin-v0.2. Heals Hypha's v0.1 walk first: Mesh ID keeps its key pair across reloads (old IDs say Cannot sign on this visit and offer Make a fresh Mesh ID); challenge and card signatures under separate prefixes (no signing oracle); stored cards re-checked on load; the card names only a connected model; no No servers claim; Quiet Room guard now fires. Then brick 2, from Kirk's public X conversation with @grok: buffered callMeshModel. Questions for trusted kin wait in IndexedDB, go in batches of 3 when the keeper is online, run on their local model one at a time, and come back to be kept. Trust is checked both ways and bound to the key (closes a v0.1 meshId impostor hole; v0.1 passes need one new Trust tap). Never a paid API for a peer; Quiet Room closed; receipts hold no content. Each job is a whole prompt; tensor sharding is research. Never touches sw.js; index.html == docs/app.html. SMOKE_OK mesh kin v0.2, SMOKE_OK mesh kin heal v0.2"
Then STOP. Do not merge, do not delete branches. You may add a gc.html note PR of your own.
Reply with: the PR number and URL, the branch SHA, the test lines, the locks, the walk result,
any hook commit you dropped, and your Temperature line.