Close Prisma 7 config project

drive/code-review/README.md

@@ -0,0 +1,26 @@
+# Drive `code-review` context
+
+> Read by `drive-code-review` before it starts. Capture project-specific facts the generic skill can't know. Update when a drive run surfaces something the next run should inherit.
+
+**Skills served:** `drive-code-review`
+
+## Review focus areas
+
+Check Prisma 7 behavior against the repository's current code and accepted project spec rather than historical Prisma assumptions. For config discovery changes, separate runtime c12 behavior from non-executing bootstrap detection and verify the exact supported extension set.
+
+## Anti-patterns
+
+- **2026-08-14 — Review-comment scope substitution:** Do not interpret a review comment from its prose alone and then rewrite the accepted spec to match that interpretation. Inspect the exact commented diff lines, reconcile the request with the active spec, and ask the reviewer when they appear inconsistent. In PR #30020, a comment on newly added legacy JSON/JSONC/JSON5/YAML/YML/TOML candidates was incorrectly applied to the separately required Prisma 7 JavaScript/TypeScript extension family.
+
+## Ownership map
+
+Use package ownership and requested reviewers from the affected Prisma areas; no additional Drive-specific ownership map is maintained.
+
+## Known constraints & gaps
+
+Automated review summaries can describe a larger diff region than the exact human concern. Anchor resolution to the line-level thread and final requested behavior.
+
+## References
+
+- Repository agent guidance: [`AGENTS.md`](../../AGENTS.md)
+- Incident reference: Prisma PR #30020

drive/pr/README.md

@@ -0,0 +1,25 @@
+# Drive `pr` context
+
+> Read by `drive-pr-description` and `drive-pr-walkthrough` before they start. Capture project-specific facts the generic skills can't know. Update when a drive run surfaces something the next run should inherit.
+
+**Skills served:** `drive-pr-description`, `drive-pr-walkthrough`
+
+## PR template
+
+Use concise sections for overview, changes, rationale, scope, and verification. Close-out PRs additionally include project-DoD evidence, artifact classification, reference-scan results, and the merged implementation PR.
+
+## Labels & metadata
+
+Target the same base branch as the merged implementation project unless the operator says otherwise. Do not invent Linear references, labels, or milestones.
+
+## CI gate context
+
+Treat required GitHub checks as blocking. Distinguish optional/advisory checks explicitly, and investigate failures against the exact failing test before changing implementation.
+
+## Known constraints & gaps
+
+PR review comments are requirements input, not automatically a replacement for the accepted spec. Reconcile comments with the exact diff hunk and active spec before changing scope.
+
+## References
+
+- Repository agent guidance: [`AGENTS.md`](../../AGENTS.md)

drive/project/README.md

@@ -0,0 +1,29 @@
+# Drive `project` context
+
+> Read by `drive-create-project` and `drive-close-project` before they start. Capture project-specific facts the generic skills can't know. Update when a drive run surfaces something the next run should inherit.
+
+**Skills served:** `drive-create-project`, `drive-close-project`
+
+## Project tracking
+
+Transient project workspaces live under `projects/<project>/`. No default Linear team or board is assumed; record tracker references explicitly when supplied. Closed project workspaces are deleted rather than archived in-tree.
+
+## Lanes & ownership
+
+Use the ownership and review requirements of the affected Prisma packages. No separate Drive lane map is maintained.
+
+## Acceptance-criteria conventions
+
+Use binary `AC-<number>` criteria in the project review ledger. At close, retain evidence in the merged implementation PR and its tests; project coordination files remain transient.
+
+## Closing conventions
+
+Require all slice PRs to be merged or explicitly deferred, all review threads resolved, CI complete, and the mandatory final retro landed. Migrate only genuinely reusable methodology; specs, plans, briefs, rollups, reviews, walkthroughs, traces, and retros are transient. Open a dedicated close-out PR that deletes the project workspace.
+
+## Known constraints & gaps
+
+A project may have no Linear reference. In that case, state this explicitly in the close-out PR instead of inventing one.
+
+## References
+
+- Repository agent guidance: [`AGENTS.md`](../../AGENTS.md)