aether-colony 1.1.8 → 1.1.9

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.
@@ -267,6 +267,32 @@ Update COLONY_STATE.json:
267
267
 
268
268
  Run `bash .aether/aether-utils.sh validate-state colony` after write.
269
269
 
270
+ ### Step 5.1: Update Changelog
271
+
272
+ **MANDATORY: Record the seal in the project changelog. This step is never skipped.**
273
+
274
+ If no `CHANGELOG.md` exists, `changelog-append` creates one automatically.
275
+
276
+ Build a summary of what the colony accomplished across all phases:
277
+ - Collect completed phase names from COLONY_STATE.json
278
+ - Summarize the goal and key outcomes in one line
279
+
280
+ ```bash
281
+ bash .aether/aether-utils.sh changelog-append \
282
+ "$(date +%Y-%m-%d)" \
283
+ "seal-crowned-anthill" \
284
+ "00" \
285
+ "{key_files_csv}" \
286
+ "Colony sealed at Crowned Anthill;{goal}" \
287
+ "{phases_completed} phases completed;Colony wisdom promoted to QUEEN.md" \
288
+ ""
289
+ ```
290
+
291
+ - `{key_files_csv}` — list the most significant files created or modified across the colony's lifetime (derive from phase plans or git log)
292
+ - `{goal}` — the colony goal from COLONY_STATE.json
293
+
294
+ **Error handling:** If `changelog-append` fails, log to midden and continue — changelog failure never blocks sealing.
295
+
270
296
  ### Step 5.5: Documentation Coverage Audit
271
297
 
272
298
  Before writing the seal document, spawn a Chronicler to survey documentation coverage.
@@ -134,6 +134,32 @@ Update COLONY_STATE.json:
134
134
  2. Set `milestone_updated_at` to current ISO-8601 timestamp
135
135
  3. Append event: `"<timestamp>|milestone_reached|archive|Achieved Crowned Anthill milestone - colony archived"`
136
136
 
137
+ ### Step 5.1: Update Changelog
138
+
139
+ **MANDATORY: Record the seal in the project changelog. This step is never skipped.**
140
+
141
+ If no `CHANGELOG.md` exists, `changelog-append` creates one automatically.
142
+
143
+ Build a summary of what the colony accomplished across all phases:
144
+ - Collect completed phase names from COLONY_STATE.json
145
+ - Summarize the goal and key outcomes in one line
146
+
147
+ ```bash
148
+ bash .aether/aether-utils.sh changelog-append \
149
+ "$(date +%Y-%m-%d)" \
150
+ "seal-crowned-anthill" \
151
+ "00" \
152
+ "{key_files_csv}" \
153
+ "Colony sealed at Crowned Anthill;{goal}" \
154
+ "{phases_completed} phases completed;Colony wisdom promoted to QUEEN.md" \
155
+ ""
156
+ ```
157
+
158
+ - `{key_files_csv}` — list the most significant files created or modified across the colony's lifetime (derive from phase plans or git log)
159
+ - `{goal}` — the colony goal from COLONY_STATE.json
160
+
161
+ **Error handling:** If `changelog-append` fails, log to midden and continue — changelog failure never blocks sealing.
162
+
137
163
  ### Step 5.5: Write Final Handoff
138
164
 
139
165
  After archiving, write the final handoff documenting the completed colony:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "aether-colony",
3
- "version": "1.1.8",
3
+ "version": "1.1.9",
4
4
  "description": "Multi-agent system using ant colony intelligence for Claude Code and OpenCode — workers self-organize via pheromone signals",
5
5
  "bin": {
6
6
  "aether": "bin/cli.js",