You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Drop articles before domain nouns for rename safety (#56)
Apply the substrate rename-safety contract: remove "a" / "an" / "the"
directly preceding Shop, Shopkeeper, and ItemTag (in any case form)
across test descriptors, code comments, OpenAPI summaries, and
substrate meta-docs. The agent's text-only rename pipeline would
otherwise produce article disagreements like "an patient" or "a office"
when users pick consonant- or vowel-starting rename targets.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/nativeapptemplate-substrate-v2-overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -140,7 +140,7 @@ See section 6.10 for rationale on the unified permission approach.
140
140
141
141
**Endpoints unchanged but with behavior change**:
142
142
-`POST /api/v1/shopkeeper/shops/:shop_id/item_tags` — no longer auto-generates A001-A010; creates a single item with user-supplied `name`
143
-
-`POST /api/v1/shopkeeper/shops` — creating a Shop now auto-generates exactly 1 "Sample" ItemTag (instead of 10 queue-number items), so new users see a reference item on the Shop detail screen instead of an empty state
143
+
-`POST /api/v1/shopkeeper/shops` — creating Shop now auto-generates exactly 1 "Sample" ItemTag (instead of 10 queue-number items), so new users see a reference item on Shop detail screen instead of an empty state
144
144
145
145
### 2.3 UI contract
146
146
@@ -489,7 +489,7 @@ The Rails API uses a custom fixture system in `db/fixtures/<env>/` (not standard
489
489
490
490
### 8.3 What to avoid
491
491
492
-
- Do NOT resurrect the Day 1 approach of fully deleting `ItemTag`. The Shop detail screen becomes empty without a child resource, and the agent's planner prompt assumes `ItemTag` exists as a rename target.
492
+
- Do NOT resurrect the Day 1 approach of fully deleting `ItemTag`. Shop detail screen becomes empty without a child resource, and the agent's planner prompt assumes `ItemTag` exists as a rename target.
493
493
- Do NOT introduce a new child model name (e.g. `ShopItem`). Keeping `ItemTag` aligns with the agent's planner prompt.
494
494
- Do NOT add i18n / Localizable.strings indirection in Phase 2-5. UI strings should be direct literals so the agent's string-literal rename (Phase 6) can operate on them.
495
495
- Do NOT touch the `AccountsInvitation` model or multi-account join table. Those stay; Free client just hides their UI.
Copy file name to clipboardExpand all lines: docs/phase1-rails-api.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -378,7 +378,7 @@ class Shop < ApplicationRecord
378
378
end
379
379
```
380
380
381
-
**Rationale for sample item**: When a Shop is first created, the Shop detail screen would otherwise be empty. A single generic "Sample" item gives users a reference to understand the UI and something to delete/edit to learn the flow. The client-side empty state UI (already implemented) handles the case after the sample is deleted.
381
+
**Rationale for sample item**: When Shop is first created, Shop detail screen would otherwise be empty. A single generic "Sample" item gives users a reference to understand the UI and something to delete/edit to learn the flow. The client-side empty state UI (already implemented) handles the case after the sample is deleted.
382
382
383
383
Check callers of removed methods:
384
384
@@ -406,7 +406,7 @@ git commit -m "Simplify Shop model: replace queue auto-generation with single sa
- Update fixture data references (`queue_number` → `name`)
758
758
- Remove tests for removed endpoints (scan, reset_all)
759
759
- Add tests for `description`, `position` handling
760
-
- Note: tests that create a Shop will now also create a sample ItemTag via the callback. Adjust `assert_difference` expectations: creating a Shop now creates 1 Shop + 1 ItemTag.
760
+
- Note: tests that create Shop will now also create a sample ItemTag via the callback. Adjust `assert_difference` expectations: creating Shop now creates 1 Shop + 1 ItemTag.
0 commit comments