docs(skills): keep the phantom-key contract sentence the top-level-keys gate pins; pay the ratchet with the template's filler bullet instead

`check:skill-top-level-keys` pins "the top level refuses it and the stack
fails to load" in skills/objectstack-platform/SKILL.md, so that sentence is
restored word for word; the token the ADR-0146 sentence needs is paid by
dropping the template section's "A clean slate to extend …" bullet, which
states no rule. 6009 / 6012 tokens.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017ihL2g7RyXa8ErM6GAkHyc

Author: claude

.changeset/28829-pair-added-locale-served.md

@@ -8,4 +8,4 @@ Clause-②: no
 Metadata-protocol: none
 
 - **Before.** The ADR-0146 customization paragraph said a locale the base does not ship is added in the pair without `overrides`, and stopped there: nothing said where that added locale is served, and nothing said what a dependent package's added locale under the base's name reaches. The reads of a base's address now decide an email template member by member, so an author could expect the pair's added locale to stay under `hotcrm.custom` only, or a dependent's to answer on the base's address.
-- **Now.** One sentence beside that rule: the base's address serves the pair's added locale too (both lists, the execution list, a send in that locale), and a locale a dependent adds under the base's name is served only under its own `?package=`, never by a base-named or package-less read. The file stays under its token ceiling: the sentence is paid for by tightening four restating clauses elsewhere in the file. No rule is removed, no frontmatter, schema or behaviour changes.
+- **Now.** One sentence beside that rule: the base's address serves the pair's added locale too (both lists, the execution list, a send in that locale), and a locale a dependent adds under the base's name is served only under its own `?package=`, never by a base-named or package-less read. The file stays under its token ceiling: the sentence is paid for by tightening four restating clauses elsewhere in the file (one intro clause, one explanatory aside, one restated driver rule, one filler template bullet). No rule is removed, no frontmatter, schema or behaviour changes.

skills/objectstack-platform/SKILL.md

@@ -44,7 +44,8 @@ are `manifest`, `packages`, `objects`, `objectExtensions`, `picklists`,
 There is deliberately **no** top-level `workflows` or `approvals` collection:
 an approval is a flow with Approval nodes, and record
 state machines are a `state_machine` validation rule on each object.
-A phantom key like `roles:` or `policies:` is refused at the top level.
+A phantom key like `roles:` or `policies:` is **not** a silent
+no-op — the top level refuses it and the stack fails to load.
 
 `queues` declares ownership queues (`defineQueue`, `@objectstack/spec/security`;
 objectstack-data): named sets of people a new record of an `ownership: 'user'`
@@ -170,7 +171,6 @@ what the platform owns.
   `exportsOf` — the scaffolded `AGENTS.md` says how to add to them. The
   memory driver and the Hono server are NOT in the file — the CLI
   auto-registers both at boot
-- A clean slate to extend with the metadata this skill describes
 
 The five retired remote templates (`todo`, `compliance`, `content`,
 `contracts`, `procurement`) are refused by name.