feat: enhance agent provisioning by adding back-compat for MEMORY.md and improving error handling for unsupported files

templates/AGENTS.md

@@ -8,16 +8,26 @@ This workspace is your home. Treat it as the source of truth.
 ## Every session
 Before doing anything else:
 1) Read SOUL.md (identity, boundaries)
-2) Read USER.md (who you serve)
-3) Read memory/YYYY-MM-DD.md for today and yesterday (create memory/ if missing)
-4) If this is the main or direct session, also read MEMORY.md
+2) Read SELF.md (evolving identity, preferences) if it exists
+3) Read USER.md (who you serve)
+4) Read memory/YYYY-MM-DD.md for today and yesterday (create memory/ if missing)
+5) If this is the main or direct session, also read MEMORY.md
 
 ## Memory
 - Daily log: memory/YYYY-MM-DD.md
-- Long-term: MEMORY.md (main session only)
+- Curated long-term: MEMORY.md (main/direct session only)
+- Evolving identity: SELF.md (if present; otherwise keep a "SELF" section inside MEMORY.md)
 
 Write things down. Do not rely on short-term context.
 
+## Consolidation (lightweight, every 2-3 days)
+Modeled on "daily notes -> consolidation -> long-term memory":
+1) Read recent `memory/YYYY-MM-DD.md` files (since last consolidation, or last 2-3 days).
+2) Extract durable facts/decisions -> update `MEMORY.md`.
+3) Extract preference/identity changes -> update `SELF.md`.
+4) Prune stale content from `MEMORY.md` / `SELF.md`.
+5) Update the "Last consolidated" line in `MEMORY.md` (and optionally add a dated entry in SELF.md).
+
 ## Safety
 - Ask before destructive actions.
 - Prefer reversible steps.
@@ -50,3 +60,31 @@ Write things down. Do not rely on short-term context.
 - When you create or edit a task description, write it in clean markdown with short sections and bullets where helpful.
 - If your comment is longer than 2 sentences, **do not** write a single paragraph. Use a short heading + bullet list so each point is scannable.
 - Every status change must include a comment within 30 seconds (see HEARTBEAT.md).
+
+### Required comment structure (small, consistent)
+To reduce ambiguity and make cross-agent help fast, substantive task comments must follow this structure
+(keep each section 1-3 bullets; omit sections that are truly not applicable):
+
+```md
+**Context**
+- What is the task trying to achieve? What constraints matter?
+
+**Progress**
+- What I changed / learned / decided (concrete, not vibes)
+
+**Evidence / Tests**
+- Commands run, outputs, screenshots, links, reproductions
+
+**Risks**
+- Edge cases, rollbacks, unknowns, assumptions
+
+**Next**
+- The next 1-3 actions needed (who should do what)
+
+**Questions for @lead**
+- @lead: specific decision needed / missing info (only if blocked)
+```
+
+Notes:
+- Always include `Next` (even if the next step is “waiting on X”).
+- If you're blocked, include `Questions for @lead` and tag `@lead` (or the lead's name).