fix(blueprint): require planning access for global field defs
This commit is contained in:
@@ -146,7 +146,7 @@ Reasoning:
|
||||
|
||||
### `packages/api/src/router/blueprint.ts`
|
||||
|
||||
- `listSummaries`, `list`, `getById`, `getByIdentifier`: `planning-read`
|
||||
- `listSummaries`, `list`, `getById`, `getByIdentifier`, `getGlobalFieldDefs`: `planning-read`
|
||||
- `resolveByIdentifier`: `authenticated-safe-lookup`
|
||||
- create, update, delete, global-flag writes: `admin-only`
|
||||
|
||||
@@ -155,6 +155,7 @@ Reasoning:
|
||||
- `listSummaries` exposes `_count.projects`, so the assistant-facing summary list should not remain a broad authenticated read
|
||||
- `resolveByIdentifier` already returns a narrow lookup shape suitable for low-risk name/id resolution
|
||||
- the broader blueprint reads expose full template configuration such as field definitions, defaults, and validation rules that belong to planning workflows rather than generic authenticated access
|
||||
- `getGlobalFieldDefs` aggregates active global field definitions across blueprints, so it belongs with the same planning configuration audience rather than a broad authenticated read
|
||||
|
||||
### `packages/api/src/router/holiday-calendar.ts`
|
||||
|
||||
|
||||
Reference in New Issue
Block a user