@thedecipherist/mdd 1.3.5 → 1.3.6
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.
- package/commands/mdd-ops.md +3 -0
- package/commands/mdd-plan.md +4 -0
- package/package.json +1 -1
package/commands/mdd-ops.md
CHANGED
|
@@ -232,6 +232,9 @@ Any service still failing → append entry to `known_issues` in the doc.
|
|
|
232
232
|
|
|
233
233
|
### Phase RO5 — Summary
|
|
234
234
|
|
|
235
|
+
**Update the runbook frontmatter** — write this field before displaying the summary:
|
|
236
|
+
- `last_synced: <today>`
|
|
237
|
+
|
|
235
238
|
```
|
|
236
239
|
runop complete — <slug>
|
|
237
240
|
|
package/commands/mdd-plan.md
CHANGED
|
@@ -251,6 +251,10 @@ When all features are `complete`:
|
|
|
251
251
|
2. User confirms → flip wave `status: complete` in both `waves/<slug>.md` AND the waves table in `initiatives/<slug>.md`.
|
|
252
252
|
3. Recompute hashes for both files.
|
|
253
253
|
4. If all waves in initiative are `complete` → ask: *"All waves done. Mark initiative complete? (yes / no)"*
|
|
254
|
+
- If yes → **Update initiative frontmatter** — write these fields now:
|
|
255
|
+
- `status: complete`
|
|
256
|
+
- `last_synced: <today>`
|
|
257
|
+
- `mdd_version: <current from mdd.md frontmatter>`
|
|
254
258
|
5. Rebuild `.mdd/.startup.md`.
|
|
255
259
|
|
|
256
260
|
---
|