chore(deps-dev): bump the all-updates group across 1 directory with 3 updates

dependabot[bot] · Perdolique · commit f3c8ed57eecd · 2026-05-01T00:28:35.000+03:00
Bumps the all-updates group with 3 updates in the / directory: [drizzle-kit](https://github.com/drizzle-team/drizzle-orm), [drizzle-orm](https://github.com/drizzle-team/drizzle-orm) and [drizzle-seed](https://github.com/drizzle-team/drizzle-orm). Updates `drizzle-kit` from 1.0.0-beta.22 to 1.0.0-beta.23 - [Release notes](https://github.com/drizzle-team/drizzle-orm/releases) - [Commits](https://github.com/drizzle-team/drizzle-orm/commits) Updates `drizzle-orm` from 1.0.0-beta.22 to 1.0.0-beta.23 - [Release notes](https://github.com/drizzle-team/drizzle-orm/releases) - [Commits](https://github.com/drizzle-team/drizzle-orm/commits) Updates `drizzle-seed` from 1.0.0-beta.22 to 1.0.0-beta.23 - [Release notes](https://github.com/drizzle-team/drizzle-orm/releases) - [Commits](https://github.com/drizzle-team/drizzle-orm/commits) --- updated-dependencies: - dependency-name: drizzle-kit dependency-version: 1.0.0-beta.23 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: all-updates - dependency-name: drizzle-orm dependency-version: 1.0.0-beta.23 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: all-updates - dependency-name: drizzle-seed dependency-version: 1.0.0-beta.23 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: all-updates ... Signed-off-by: dependabot[bot] <support@github.com>
diff --git a/.agents/skills/roadmap-planning/SKILL.md b/.agents/skills/roadmap-planning/SKILL.md
@@ -12,7 +12,7 @@ Use this skill to keep `plan/` as a small, implementation-oriented roadmap inste
 Use this skill for:
 
 - editing files under `plan/**`
-- changing `plan/PLAN.md` order, links, or section membership
+- changing `plan/ROADMAP.md` order, links, or section membership
 - splitting product, backend, frontend, or test work into implementation iterations
 - moving shipped work from an active plan into `plan/completed.md`
 - recording accepted follow-up work in `plan/tech-debt.md`
@@ -21,17 +21,17 @@ Do not use this skill for generic Markdown cleanup, README/docs copy edits, arch
 
 ## Roadmap model
 
-- `plan/PLAN.md` is the top-down index and source of truth for work order.
+- `plan/ROADMAP.md` is the top-down index and source of truth for work order.
 - Active roadmap files hold only work that still matters for upcoming implementation.
 - `plan/completed.md` is a short factual journal, not an archive of execution detail.
 - `plan/tech-debt.md` is for accepted engineering follow-up after a smaller slice ships.
 - Deferred product files should explain their return conditions instead of acting as open-ended wishlists.
 
 ## Editing workflow
 
-1. Read `plan/PLAN.md` and the target plan file before changing roadmap content.
+1. Read `plan/ROADMAP.md` and the target plan file before changing roadmap content.
 2. Classify the change as active roadmap, deferred product work, engineering follow-up, or completed work.
-3. Keep links and section membership in `plan/PLAN.md` synchronized with renamed, moved, added, or completed plan files.
+3. Keep links and section membership in `plan/ROADMAP.md` synchronized with renamed, moved, added, or completed plan files.
 4. Remove stale roadmap detail when work ships. Preserve only the short completed summary needed in `plan/completed.md`.
 5. Move new follow-up ideas to `plan/tech-debt.md` or a deferred roadmap file instead of leaving TODOs inside completed or active shipped sections.
 
@@ -59,4 +59,5 @@ When drafting or revising iterations:
 - Keep planning docs in English.
 - Prefer concrete behavior and current constraints over generic platform-speak.
 - State assumptions and activation rules directly when work is deferred.
-- Remove stale guidance instead of appending contradictory notes on top of it.
+- Remove stale guidance instead of appending contradictory notes on top of it.
+
diff --git a/AGENTS.md b/AGENTS.md
@@ -37,4 +37,4 @@
 
 - Markdown changes: `pnpm run lint:markdown`.
 - TypeScript or Vue changes: `pnpm run test:typecheck`, `pnpm run test:unit:agent`, `pnpm run lint:oxlint`, `pnpm run build`, and `pnpm run test:e2e:ci`.
-- Run applicable checks in parallel where practical.
+- Run applicable checks in parallel where practical.
diff --git a/docs/architecture/container-queries.md b/docs/architecture/container-queries.md
@@ -19,4 +19,4 @@ Responsive CSS decision rules live here as architecture guidance, not as roadmap
 
 - Keep at least one real `PageContent` screen with an `actions` slot covered in Playwright.
 - Add or keep a focused assertion that the header stacks when the `PageContent` container is narrowed inside a wide viewport, so the test proves container-driven behavior rather than viewport-driven behavior.
-- Re-run the existing responsive smoke around login and sidebar shell behavior to catch regressions in rules that intentionally stay on `@media`.
+- Re-run the existing responsive smoke around login and sidebar shell behavior to catch regressions in rules that intentionally stay on `@media`.
diff --git a/plan/ROADMAP.md b/plan/ROADMAP.md
@@ -29,4 +29,4 @@ This file is the source of truth for the order of upcoming work. Each active ite
 - Every iteration must state its result, scope boundaries, non-goals, touched surfaces, required verification, and completed-work summary.
 - Prefer the smallest vertical slice that delivers one coherent user result. Use API-only work only when it produces a standalone contract that can be validated independently.
 - After an iteration ships, remove or collapse its active detail and add a short factual entry to [Completed work](completed.md).
-- Move new follow-up ideas to [Technical debt](tech-debt.md) or a deferred roadmap file instead of leaving TODOs inside completed work.
+- Move new follow-up ideas to [Technical debt](tech-debt.md) or a deferred roadmap file instead of leaving TODOs inside completed work.
diff --git a/plan/catalog-discoverability.md b/plan/catalog-discoverability.md
@@ -30,4 +30,4 @@
 - The chosen discoverability control improves an observed ownership or packing-list workflow.
 - The public URL includes only supported, user-visible state.
 - The slice does not reopen deferred admin work or speculative browse features.
-- Any follow-up controls are listed as separate iterations instead of being bundled into the first discoverability change.
+- Any follow-up controls are listed as separate iterations instead of being bundled into the first discoverability change.
diff --git a/plan/completed.md b/plan/completed.md
@@ -44,4 +44,4 @@ Migration CLI script (`tools/migrate.ts`). Playwright browser smoke covers login
 
 ## Seed data
 
-Catalog seed CLI implemented with `drizzle-seed` for reset/reference data and plain Drizzle inserts for EAV rows. Includes local (`db:seed:local`) and CI/staging (`db:seed`) entrypoints, PR staging workflow integration, deterministic groups/categories/brands, and sample items covering seeded `number`, `enum`, and `boolean` property values with validation that each property is written to the correct `value*` column.
+Catalog seed CLI implemented with `drizzle-seed` for reset/reference data and plain Drizzle inserts for EAV rows. Includes local (`db:seed:local`) and CI/staging (`db:seed`) entrypoints, PR staging workflow integration, deterministic groups/categories/brands, and sample items covering seeded `number`, `enum`, and `boolean` property values with validation that each property is written to the correct `value*` column.
diff --git a/plan/packing-lists-mvp.md b/plan/packing-lists-mvp.md
@@ -126,4 +126,4 @@ Catalog ownership is already shipped and summarized in [Completed work](complete
 - A signed-in user can add a custom entry directly on `/packing-lists/[id]`.
 - A signed-in user can toggle entries as packed and remove them.
 - A signed-in user can add an approved catalog item to an existing packing list from `/catalog/[id]`.
-- The flow remains useful even when the public catalog is incomplete.
+- The flow remains useful even when the public catalog is incomplete.
diff --git a/plan/tech-debt.md b/plan/tech-debt.md
@@ -30,4 +30,4 @@ Product-scope changes belong in the active roadmap or deferred roadmap files, no
 
 ## Responsive layout coverage
 
-- **Add container-width coverage for `PageContent` actions** — `PageContent` now uses `container-type: inline-size`, but Playwright should include a focused assertion that the header actions respond to a narrowed content container inside a wide viewport rather than only to viewport width.
+- **Add container-width coverage for `PageContent` actions** — `PageContent` now uses `container-type: inline-size`, but Playwright should include a focused assertion that the header actions respond to a narrowed content container inside a wide viewport rather than only to viewport width.
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml

Original file line number	Diff line number	Diff line change
@@ -44,4 +44,4 @@ Migration CLI script (`tools/migrate.ts`). Playwright browser smoke covers login
`44`	`44`
`45`	`45`	`## Seed data`
`46`	`46`
`47`		-Catalog seed CLI implemented with `drizzle-seed` for reset/reference data and plain Drizzle inserts for EAV rows. Includes local (`db:seed:local`) and CI/staging (`db:seed`) entrypoints, PR staging workflow integration, deterministic groups/categories/brands, and sample items covering seeded `number`, `enum`, and `boolean` property values with validation that each property is written to the correct `value*` column.
	`47`	+Catalog seed CLI implemented with `drizzle-seed` for reset/reference data and plain Drizzle inserts for EAV rows. Includes local (`db:seed:local`) and CI/staging (`db:seed`) entrypoints, PR staging workflow integration, deterministic groups/categories/brands, and sample items covering seeded `number`, `enum`, and `boolean` property values with validation that each property is written to the correct `value*` column.
Original file line number	Diff line number	Diff line change
`@@ -30,4 +30,4 @@ Product-scope changes belong in the active roadmap or deferred roadmap files, no`
`30`	`30`
`31`	`31`	`## Responsive layout coverage`
`32`	`32`
`33`		-- Add container-width coverage for `PageContent` actions — `PageContent` now uses `container-type: inline-size`, but Playwright should include a focused assertion that the header actions respond to a narrowed content container inside a wide viewport rather than only to viewport width.
	`33`	+- Add container-width coverage for `PageContent` actions — `PageContent` now uses `container-type: inline-size`, but Playwright should include a focused assertion that the header actions respond to a narrowed content container inside a wide viewport rather than only to viewport width.