#17938: feat(workspace): Add GOALS.md and SOUVENIR.md for behavioral anchors

- Add GOALS.md template for direction & execution strategy - Add SOUVENIR.md template for memory & reflection layer - Update SOUL.md to reference new behavioral anchors These files enable: - Long-term goal tracking and progress measurement - Continuous self-improvement through structured reflection - Health monitoring via file timestamps and activity patterns ## Summary Describe the problem and fix in 2–5 bullets: - Problem: - Why it matters: - What changed: - What did NOT change (scope boundary): ## Change Type (select all) - [ ] Bug fix - [ ] Feature - [ ] Refactor - [ ] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [ ] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [ ] Memory / storage - [ ] Integrations - [ ] API / contracts - [ ] UI / DX - [ ] CI/CD / infra ## Linked Issue/PR - Closes # - Related # ## User-visible / Behavior Changes List user-visible changes (including defaults/config). If none, write `None`. ## Security Impact (required) - New permissions/capabilities? (`Yes/No`) - Secrets/tokens handling changed? (`Yes/No`) - New/changed network calls? (`Yes/No`) - Command/tool execution surface changed? (`Yes/No`) - Data access scope changed? (`Yes/No`) - If any `Yes`, explain risk + mitigation: ## Repro + Verification ### Environment - OS: - Runtime/container: - Model/provider: - Integration/channel (if any): - Relevant config (redacted): ### Steps 1. 2. 3. ### Expected - ### Actual - ## Evidence Attach at least one: - [ ] Failing test/log before + passing after - [ ] Trace/log snippets - [ ] Screenshot/recording - [ ] Perf numbers (if relevant) ## Human Verification (required) What you personally verified (not just CI), and how: - Verified scenarios: - Edge cases checked: - What you did **not** verify: ## Compatibility / Migration - Backward compatible? (`Yes/No`) - Config/env changes? (`Yes/No`) - Migration needed? (`Yes/No`) - If yes, exact upgrade steps: ## Failure Recovery (if this breaks) - How to disable/revert this change quickly: - Files/config to restore: - Known bad symptoms reviewers should watch for: ## Risks and Mitigations List only real risks for this PR. Add/remove entries as needed. If none, write `None`. - Risk: - Mitigation: <!-- greptile_comment --> <h3>Greptile Summary</h3> Adds two new behavioral anchor templates (`GOALS.md` and `SOUVENIR.md`) to the workspace template system, enabling structured goal tracking and reflection/learning capture. Updates `SOUL.md` to reference all memory layer files including the new additions. **Key Changes:** - `GOALS.md` template provides structure for tracking objectives, success criteria, subtasks, and dependencies with clear writing rules - `SOUVENIR.md` template enables structured reflection with timestamped entries (Context → Observation → Insight → Action) - `SOUL.md` Continuity section now documents all six workspace files (SOUL, GOALS, SOUVENIR, TOOLS, USER, AGENTS) **Quality:** - Both new templates include proper frontmatter matching the established pattern (`title`, `summary`, `read_when` fields) - Content is well-structured with clear examples and usage guidelines - Maintains consistency with existing template style and tone - Documentation-only change with no functional code impact <h3>Confidence Score: 5/5</h3> - Safe to merge - documentation-only change with no functional impact - This PR only adds template documentation files and updates references. The frontmatter issue from previous feedback has been addressed. No code logic, dependencies, or configurations are modified. The changes are well-structured and consistent with existing templates. - No files require special attention _{Last reviewed commit: f14af3a} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->