ContextQMD
Back to Prisma

Brief: D1 R2 — preserve explicit error attribution

projects/prisma7-config/briefs/D1-R2.md

7.10.0-integration-fix-prisma-publish-token.12.2 KB
Original Source

Brief: D1 R2 — preserve explicit error attribution

Task

Resolve reviewer finding F1 in projects/prisma7-config/reviews/code-review.md: explicit configFile load failures must retain and report the authoritative requested file path rather than configRoot, including explicit Prisma 7-specific and custom filenames, without weakening automatic Prisma 7 hard-failure semantics or legacy automatic error extraction.

Scope

In: Narrow packages/config loader correction and focused regression tests for explicit invalid paths beside competing automatic candidates.

Out: Any broader discovery refactor, CLI/bootstrap/init/guidance/e2e work, dependency changes, new warnings, or unrelated cleanup.

Completed when

  • Explicit invalid Prisma 7-specific and custom config paths return the requested resolved path in load errors, with regression tests that would fail against current HEAD.
  • Automatic versioned hard-failure and legacy fallback behavior from D1 R1 remain green.
  • pnpm --filter @prisma/config build, pnpm --filter @prisma/config test loadConfigFromFile.test.ts, Prettier, git diff --check, and transient-ID scan pass on final HEAD.
  • F1 is addressed in a new explicitly staged commit; do not edit the reviewer ledger.

Standing instruction

Stay focused on the goal; control scope. Anything beyond the concrete finding halts and surfaces.

Operational metadata

  • Model tier: orchestrator — focused but load-error attribution is correctness-sensitive.
  • Time-box: 30 minutes wall clock.
  • Halt conditions: Halt if the finding conflicts with evidence, requires a public API redesign, or any validation gate cannot run/remains red for unrelated reasons.

Carry-over

  • F1 (must-fix): explicit invalid config paths currently report configRoot; preserve the explicit requested path and add non-tautological regression coverage.
  • Decisions standing: explicit paths remain authoritative; automatic versioned selected-file failures hard-fail; fallback is absence-only.

Return shape

Report reconnaissance, decision, exact diff paths, gate results, commit SHA, surprises, deferrals, and any evidence-based pushback. Write heartbeats to wip/heartbeats/implementer.txt; do not edit project specs/plans/reviews.