Add: design-time-file-partition

[jedarden]

New pattern under Orchestration & Control, from running ~20 headless workers on shared checkouts. validate:patterns passes; data regeneration left to your build per CONTRIBUTING. (author of the source)

[vercel]

@jedarden is attempting to deploy a commit to the nkkko's projects Team on Vercel.

A member of the Team first needs to authorize it.

[nibzard]

Thanks—this pattern is useful and looks suitable for the catalog after a few changes:

1. Add the required ## How to use it section.
2. Remove the README.md changes; that region is auto-generated.
3. Please consider changing status from established to emerging, since the evidence currently reflects one practitioner deployment.
4. Clarify that ownership must include generated files and other incidental writes.

The Pattern Reviewer and Vercel failures appear to be workflow/infrastructure issues rather than content verdicts.

[jedarden]

Thanks for the review — all four points addressed in e1e6109 + fb88802 (branch also merged with current main):

1. Added ## How to use it (and the now-required updated_at).
2. README.md change dropped; the PR's only diff against main is patterns/design-time-file-partition.md.
3. status: emerging, with Evidence Grade low and the single-deployment caveat stated explicitly in the Evidence section.
4. Ownership is now defined as the full write set, not the intended edit set: generated outputs (lockfiles, codegen, snapshots, rendered indexes), repo-wide files (changelog, version, tracker checkpoint), formatter/linter --fix side effects, and no opportunistic edits outside the owned set — enforced by committing only owned paths. The rule is in Solution; the checklist is in How to use it.

bun run validate:patterns passes locally. The only error from validate:patterns:content is in an existing file (cross-agent-lesson-sharing.md, missing References), not this one.