🐛 fix: respect agent-level memory config priority over user settings (#13018)

* update skills

* 🐛 fix: respect agent-level memory config priority over user settings

Agent chatConfig.memory.enabled now takes priority. Falls back to user-level
memory setting when agent config is absent.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* 🐛 fix: resolve tsgo type error in memory integration test

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.agents/skills/version-release/reference/changelog-example/db-migration.md

@@ -15,4 +15,6 @@ This release includes a **database schema migration** involving **5 new tables**
 - The migration runs automatically on application startup
 - No manual intervention required
 
-The migration owner: @\[pr-author] — responsible for this database schema change, reach out for any migration-related issues.
+The migration owner: @{pr-author} — responsible for this database schema change, reach out for any migration-related issues.
+
+> **Note for Claude**: Replace `{pr-author}` with the actual PR author. Retrieve via `gh pr view <number> --json author --jq '.author.login'` or `git log` commit author. Do NOT hardcode a username.

.agents/skills/version-release/reference/patch-release-scenarios.md

@@ -105,6 +105,7 @@ git push -u origin release/db-migration-{name}
    - What tables/columns are added, modified, or removed
    - Whether the migration is backwards-compatible
    - Any action required by self-hosted users
+   - **Migration owner**: Use the actual PR author (retrieve via `gh pr view <number> --json author --jq '.author.login'` or `git log` commit author), never hardcode a username
 
 3. **Create PR to main** with the migration changelog as the PR body