start-vibing-stacks 2.25.2 → 2.26.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -2,11 +2,15 @@
2
2
 
3
3
  > **CHARACTER LIMIT**: Max 40,000 chars. Validate with `wc -m CLAUDE.md` before commit.
4
4
 
5
- ## Last Change
5
+ ## Recent Changes
6
6
 
7
- **Branch:** main
8
- **Date:** {{DATE}}
9
- **Summary:** Initial project setup with start-vibing-stacks (PHP — API-first React SPA)
7
+ <!-- APPEND-ONLY LIFO. Each Claude instance PREPENDS a new `### YYYY-MM-DD · branch · vX.Y.Z` heading
8
+ + 1-4 lines below it. Drop only the OLDEST entry when count > 10. NEVER edit a peer's entry.
9
+ `domain-updater` v3.0.0+ does this automatically post-commit.
10
+ Compactor (`claude-md-compactor.md §5-§6`) enforces the cap, not the prepend. -->
11
+
12
+ ### {{DATE}} · main · v0.1.0
13
+ Initial project setup with start-vibing-stacks (PHP — API-first React SPA).
10
14
 
11
15
  ## 30 Seconds Overview
12
16
 
@@ -141,17 +145,17 @@ project/
141
145
 
142
146
  | Change Type | Sections to Update |
143
147
  |-------------|-------------------|
144
- | Any file change | Last Change (branch, date, summary) |
148
+ | Any file change | PREPEND new entry to `## Recent Changes` (heading: `### YYYY-MM-DD · branch · vX.Y.Z` + 1-4 lines) |
145
149
  | API/routes | Critical Rules, Architecture |
146
150
  | New feature | 30s Overview, Architecture |
147
151
  | New gotcha | FORBIDDEN or NRY |
148
152
  | New dependency | Stack |
149
153
  | Workflow change | Workflow section |
150
154
 
151
- 1. **Last Change** documents WHAT was done
152
- 2. **Other sections** document HOW things work NOW
153
- 3. **Both must be current** — updating only Last Change is insufficient
154
- 4. Keep only the LATEST Last Change entry (no stacking)
155
+ 1. **`## Recent Changes`** documents WHAT was done across recent sessions (append-only LIFO, cap 10).
156
+ 2. **Other sections** document HOW things work NOW.
157
+ 3. **Both must be current** — prepending to Recent Changes is insufficient if rule sections went stale.
158
+ 4. **APPEND-ONLY** — PREPEND your entry below the HTML comment anchor; drop only the OLDEST entry when count > 10. NEVER edit a peer's entry, NEVER collapse two entries into one. Multi-instance safe by construction.
155
159
 
156
160
  ## Critical Rules
157
161
 
@@ -372,7 +376,7 @@ $results = DB::select('SELECT * FROM users WHERE id = ?', [$id]);
372
376
  3. IMPLEMENT → Bottom-up: FormRequest+Policy → Service → Resource → Controller → Route → React page
373
377
  4. TEST → PHPUnit feature tests (happy + 401 + 403 + 422); React: api.test.ts
374
378
  5. DOCUMENT → documenter agent for modified files; update domain docs
375
- 6. UPDATE → Update THIS FILE (CLAUDE.md) — Last Change + relevant sections
379
+ 6. UPDATE → Update THIS FILE (CLAUDE.md) — PREPEND entry to ## Recent Changes (LIFO) + refresh relevant rule sections
376
380
  7. QUALITY → PHPStan + PHPUnit + PHP-CS-Fixer + tsc + eslint
377
381
  8. COMMIT → Conventional commits; merge to main
378
382
  ```
@@ -2,11 +2,15 @@
2
2
 
3
3
  > **CHARACTER LIMIT**: Max 40,000 chars. Validate with `wc -m CLAUDE.md` before commit.
4
4
 
5
- ## Last Change
5
+ ## Recent Changes
6
6
 
7
- **Branch:** main
8
- **Date:** {{DATE}}
9
- **Summary:** Initial project setup with start-vibing-stacks (Python)
7
+ <!-- APPEND-ONLY LIFO. Each Claude instance PREPENDS a new `### YYYY-MM-DD · branch · vX.Y.Z` heading
8
+ + 1-4 lines below it. Drop only the OLDEST entry when count > 10. NEVER edit a peer's entry.
9
+ `domain-updater` v3.0.0+ does this automatically post-commit.
10
+ Compactor (`claude-md-compactor.md §5-§6`) enforces the cap, not the prepend. -->
11
+
12
+ ### {{DATE}} · main · v0.1.0
13
+ Initial project setup with start-vibing-stacks (Python).
10
14
 
11
15
  ## 30 Seconds Overview
12
16
 
@@ -213,22 +217,31 @@ pytest --tb=short # Tests (MUST pass)
213
217
 
214
218
  | Change Type | What to Update |
215
219
  |-------------|----------------|
216
- | Any file change | Last Change section |
220
+ | Any file change | PREPEND new entry to `## Recent Changes` (LIFO, cap 10) |
217
221
  | New feature | 30s Overview, Architecture if needed |
218
222
  | New pattern | Add to relevant section |
219
223
  | Gotcha discovered | Add to FORBIDDEN or NRY |
220
224
  | New dependency | Update Stack table |
221
225
 
222
- ### Last Change Format (MANDATORY)
226
+ ### Recent Changes Format (MANDATORY)
227
+
228
+ Each new entry is a `###` block PREPENDED below the HTML comment anchor. Multi-instance safe by construction (append-only LIFO, cap 10).
223
229
 
224
230
  ```markdown
225
- ## Last Change
231
+ ## Recent Changes
232
+
233
+ <!-- APPEND-ONLY LIFO ... (HTML comment, do NOT edit) -->
226
234
 
227
- **Branch:** feature/example
228
- **Date:** YYYY-MM-DD
229
- **Summary:** 1-2 sentences describing WHAT and WHY.
235
+ ### YYYY-MM-DD · feature/example · v0.2.0
236
+ 1-4 plain-text lines describing WHAT and WHY. Inline `code` allowed for agent/skill/file names.
237
+ No bullets, no nested headers, no horizontal rules.
238
+
239
+ ### YYYY-MM-DD · main · v0.1.0
240
+ (previous entry below — never edit a peer's entry)
230
241
  ```
231
242
 
243
+ `domain-updater` v3.0.0+ does the prepend automatically post-commit. Drop only the OLDEST `### ` block when count exceeds 10. NEVER reorder middle entries; NEVER collapse two entries into one.
244
+
232
245
  ## Agent System
233
246
 
234
247
  | Agent | Purpose |