Yoram Kornatzky

Sep 29

Household Manager now cleans the house. Cooking still plans the meals. Shopping still builds the list. Maintenance still mails the day’s work. This slice is cleaning — mopping, vacuuming, dusting — from the same house inventory, not mixed into maintenance. Save the House screen and a cleaning sche...Read more

Household Manager now cleans the house. Cooking still plans the meals. Shopping still builds the list. Maintenance still mails the day’s work. This slice is cleaning — mopping, vacuuming, dusting — from the same house inventory, not mixed into maintenance. Save the House screen and a cleaning schedule appears. Kitchen counters daily. Vacuum and dust weekly. Bathroom weekly. Bedding weekly. Windows every three months. Pool skim in summer. Dryer lint trap weekly — the vent stays on maintenance. Override cadence, season, skip, or notes. The Cleaning calendar is a month grid. Click a day for that day’s chores. At 08:00 local time, Laravel Notifications emails the work. No tasks, no email. Screenshots: House cleaning schedule (counters daily, mop weekly, vacuum weekly); September with a day selected; the 08:00 mail. Anyone else generating a cleaning calendar from the house, instead of a static chore list? #Laravel #LaravelAI #AgenticAI #Cursor #PHP

Sep 24

Household Manager now survives a missed minute. Cooking still plans the meals. Shopping still builds the list. Maintenance still mails the day’s work. This slice is catch-up: a deploy or a crash at due time used to drop the task. It did not come back. The same four jobs still tick every minute. Th...Read more

Household Manager now survives a missed minute. Cooking still plans the meals. Shopping still builds the list. Maintenance still mails the day’s work. This slice is catch-up: a deploy or a crash at due time used to drop the task. It did not come back. The same four jobs still tick every minute. They no longer require the exact local minute. If the due time has passed and the work is not done, they run it late. Breakfast served at 08:05 is still breakfast. A prep mail a few minutes late is still the mail. A shopping week missed on Sunday still plans Monday morning — for that week, not the next one. Yesterday’s breakfast is not served at midnight. A killed run used to hold a 24-hour lock. That lock now expires in ten minutes. Meal planning and the shopping list retry after a worker dies, instead of failing once. There is no extra “did it run?” table. The meal’s serve stamp, the prep-mail stamp, the shopping-list row, and the maintenance log already say whether it ran. Cleaning is still later. Anyone else treating a missed cron as “run it when you wake up,” not “skip this one”? #Laravel #LaravelAI #AgenticAI #Cursor #PHP

Sep 22

Household Manager now maintains the house. Cooking still plans the meals. Shopping still builds the list from pantry stock. This slice is maintenance — not cleaning — generated from the house itself. A House screen records the property: floors and rooms, outbuildings (storage, BBQ cabin), inside f...Read more

Household Manager now maintains the house. Cooking still plans the meals. Shopping still builds the list from pantry stock. This slice is maintenance — not cleaning — generated from the house itself. A House screen records the property: floors and rooms, outbuildings (storage, BBQ cabin), inside facilities (pool, SPA, jacuzzi), outside (garden, trees, flowers), and equipment (fridge, oven, laundry, dryer, dishwasher). Save the inventory and a schedule appears. You can override cadence, season, start date, skip, or notes. The Maintenance calendar is a month grid. Click a day for that day’s tasks. A scheduler runs every minute. At 08:00 in the user’s timezone, Laravel Notifications emails the day’s work. No tasks, no email. Screenshots: House with a two-story inventory and the generated schedule (dryer vent yearly, gutters every six months, notes after autumn storms); then September with the 7th selected and those tasks listed. Cleaning comes later. Anyone else generating a maintenance calendar from the house, instead of a static reminder list? #Laravel #LaravelAI #AgenticAI #Cursor #PHP

Sep 17

Household Manager now starts the grocery list on the clock. Cooking still plans the meals. Shopping still builds the list from pantry stock. This slice is lead time: shopping time plus delivery time, counted back from Monday breakfast. Sunday-night prep is gone. shopping:prepare still runs every m...Read more

Household Manager now starts the grocery list on the clock. Cooking still plans the meals. Shopping still builds the list from pantry stock. This slice is lead time: shopping time plus delivery time, counted back from Monday breakfast. Sunday-night prep is gone. shopping:prepare still runs every minute. It fires when now is at or after Monday breakfast minus that lead. A three-day lead starts next week’s list on Friday at 08:00. A nine-day lead skips a Monday that is already too close and lands on the next one that still fits. Default is one shopping day and no delivery. You set days and hours on Shopping times. Under the heading, a live line shows when the next list will start preparing. The screenshot is that screen with 1 shopping day and 2 delivery days. Breakfast is 08:00 from Cooking, so the next list starts Friday, September 11 at 08:00 — three days before Monday breakfast. Groceries have to be in the house before that meal, not generated on Sunday night. Maintenance and cleaning come later. Anyone else counting the list back from breakfast instead of pinning it to Sunday? #Laravel #LaravelAI #AgenticAI #Cursor #PHP

Sep 14

Household Manager now tests the agents. Cooking still plans the meals. Shopping still builds the list. This slice is the safety net: Pest 5 on the Laravel AI SDK build, so a dish, a shopping list, and a pantry change cannot drift without a test noticing. What landed: 1. Feature tests cover agents...Read more

Household Manager now tests the agents. Cooking still plans the meals. Shopping still builds the list. This slice is the safety net: Pest 5 on the Laravel AI SDK build, so a dish, a shopping list, and a pantry change cannot drift without a test noticing. What landed: 1. Feature tests cover agents, meals, shopping, inventory, settings, and auth. 2. Architecture tests keep the shape of the app honest. 3. One Playwright browser test hits the real home page. Trap: if Vite HMR is running, Chromium waits forever on the hot file. Tests now load the built assets instead. 4. Evals cover the three application agents. They run only with --evals. Live-model cases still skip — the model rejects a temperature setting Pest wants to send. 5. Mutation testing rewrites the code on purpose and checks the suite still fails. Numbers from a fresh local run: Line coverage of app/ — 98.8% Type coverage — 98.2% Mutation score — 98.9% Suite — 313 passed, 18 skipped, 933 assertions, about 16 seconds Local Test Impact Analysis records which tests a change actually needs. CI still runs the full suite, including Chromium for the browser test. Coverage, evals, and mutate stay local. Coverage that never kills a mutant is decoration. Mutation score is the number I care about. Anyone else mutation-testing Laravel agents, or is coverage still the ceiling? #Laravel #LaravelAI #AgenticAI #Cursor #PestPHP