Integration fix 3: keep recipe_url out of dinner responses (Feature 12 review F1) (#97 )

Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>
Integration fix 2: conditional recipe repairs and no pasted links in logs (Feature 12 review F1, F2) (#96 )
2026-10-06 21:22:56 -04:00 · 2026-10-06 20:26:56 -04:00 · 2026-10-06 19:54:47 -04:00 · 2026-10-06 18:47:41 -04:00 · 2026-10-06 18:31:48 -04:00 · 2026-10-06 17:57:25 -04:00
5 changed files with 7 additions and 7 deletions
@@ -517,7 +517,7 @@ Regular has a name `harness.Similar` to it — the PWA's copy of the name
 rules in `web/src/dinners/names.ts` folds letters with
 `web/src/dinners/letterFolds.json`, which `gen_folds.py` writes from the
 same table as the server's, and runs the same cases,
-`web/src/dinners/testdata/dedupe_cases.json`, as the server's) and
+`internal/ai/harness/testdata/dedupe_cases.json`, as the server's) and
 notifications (`/onboarding/notifications`: what MealQuest notifies about,
 the iOS install hint, "Turn on notifications" and "Maybe later"). Either
 button sends `PATCH /api/v1/settings/household` with
@@ -8,11 +8,11 @@ import (
 	"unicode/utf8"
 )

-// TestSharedDedupeCases runs web/src/dinners/testdata/dedupe_cases.json,
-// which the PWA's copy of Normalize and Similar (web/src/dinners/names.ts)
-// runs too, so the two cannot drift apart on these names.
+// TestSharedDedupeCases runs testdata/dedupe_cases.json, which the PWA's
+// copy of Normalize and Similar (web/src/dinners/names.ts) runs too, so the
+// two cannot drift apart on these names.
 func TestSharedDedupeCases(t *testing.T) {
-	raw, err := os.ReadFile("../../../web/src/dinners/testdata/dedupe_cases.json")
+	raw, err := os.ReadFile("testdata/dedupe_cases.json")
 	if err != nil {
 		t.Fatal(err)
 	}
@@ -1,5 +1,5 @@
 import { describe, expect, it } from 'vitest'
-import cases from './testdata/dedupe_cases.json'
+import cases from '../../../internal/ai/harness/testdata/dedupe_cases.json'
 import { normalizeName, similarNames } from './names.ts'

 // The cases internal/ai/harness's tests run against Normalize and Similar.
@@ -1,7 +1,7 @@
 // The PWA's copy of the server's dinner-name rules (internal/ai/harness
 // Normalize and Similar), so a screen can tell beforehand that the dinners
 // API would refuse a name as a duplicate. The server still decides.
-// web/src/dinners/testdata/dedupe_cases.json is run against both.
+// internal/ai/harness/testdata/dedupe_cases.json is run against both.

 import folds from './letterFolds.json'
Author	SHA1	Message	Date
orchestrator-agent	f85e09ae07	Integration fix 3: keep recipe_url out of dinner responses (Feature 12 review F1) (#97 ) CI / ci (push) Successful in 2m25s Details CI / ci (pull_request) Successful in 2m25s Details Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>	2026-10-06 21:22:56 -04:00
orchestrator-agent	5dff7825d8	Integration fix 2: conditional recipe repairs and no pasted links in logs (Feature 12 review F1, F2) (#96 ) CI / ci (pull_request) Successful in 2m22s Details CI / ci (push) Successful in 2m42s Details Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>	2026-10-06 20:26:56 -04:00
orchestrator-agent	cc7875c76c	Integration fix: Feature 12 feature-review findings F1-F8 (#95 ) CI / ci (pull_request) Successful in 2m23s Details CI / ci (push) Successful in 2m27s Details Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>	2026-10-06 19:54:47 -04:00
dev_agentandClaude Opus 5.5	171c9c2d11	Fix stale Regular grounding and enforce three Regulars for onboarding CI / ci (push) Successful in 2m20s Details CI / ci (pull_request) Successful in 2m21s Details A background grounding result now applies only while the dinner is still pending under the normalized name the job searched: GroundPendingDinner and FailPendingDinnerGrounding match normalized_name, so a rename makes the old job's success or failure a no-op. Renaming a dinner still pending enqueues a fresh grounding job for the new name; if that cannot be enqueued, the dinner's grounding is failed so it is not left pending with no job. Completing onboarding (PATCH /api/v1/settings/household with onboarding_completed true) is refused with 400 invalid_settings until the household has at least three Regulars (status regular; archived and Quest log dinners do not count), and onboarding_completed_at is set only then. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 18:47:41 -04:00
dev_agent	9baabad84c	Regular dinners management screen (#93 ) CI / ci (push) Successful in 2m23s Details CI / ci (pull_request) Successful in 2m22s Details Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-06 18:31:48 -04:00
dev_agent	6a3f1f3936	Onboarding step 3 shell (#92 ) CI / ci (push) Successful in 2m19s Details Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-06 17:57:25 -04:00
dev_agent	0a5db6a9e6	Onboarding steps 1 and 2 (mock 1h) with first-run redirect (#91 ) CI / ci (push) Successful in 2m24s Details Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-06 17:34:52 -04:00
dev_agent	423b898f54	Background grounding and recipe fix-up API (#90 ) CI / ci (push) Successful in 2m24s Details Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-06 16:39:10 -04:00
dev_agent	729c5bd0fe	Dinners API for Regulars (#89 ) CI / ci (push) Successful in 2m15s Details Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-06 15:57:13 -04:00