[E17-S02-T01] Namespaced key validation #324

New Issue

2026-08-27T08:05:49Z

kpcto commented

2026-08-27 08:05:49 +00:00

Parent story: [E17-S02] Preference service (#124)

Intent

Validate that preference keys are namespaced before every read, write and delete.

Acceptance criteria

get/set/delete require a namespace and a key.
An invalid or missing namespace is rejected.
Keys are stored scoped to namespace and site.

Explicitly out of scope

Feature-supplied validation (T02) and theme-specific persistence avoidance (T03).

Test plan

Unit test rejecting an empty or malformed namespace.
Unit test that get/set/delete round-trip within a namespace.

Rollback note

Revert the commit. No data changes.

Owning stream

platform

Risk quadrant

agent-full

> Parent story: [E17-S02] Preference service (#124) ## Intent Validate that preference keys are namespaced before every read, write and delete. ## Acceptance criteria - get/set/delete require a namespace and a key. - An invalid or missing namespace is rejected. - Keys are stored scoped to namespace and site. ## Explicitly out of scope - Feature-supplied validation (T02) and theme-specific persistence avoidance (T03). ## Test plan - Unit test rejecting an empty or malformed namespace. - Unit test that get/set/delete round-trip within a namespace. ## Rollback note - Revert the commit. No data changes. ### Owning stream platform ### Risk quadrant agent-full

kpcto added this to the Sprint 5 milestone 2026-08-27 08:05:49 +00:00

kpcto added the

labels 2026-08-27 08:05:49 +00:00

Sign in to join this conversation.