Rename Sysadmin Session Closer Agent to Finish Up Agent

Renamed the agent from 'sysadmin-session-closer' to 'finish-up' and added VPS hostname functionality to session summary filenames.

Changes:
- Renamed agent file: agents/sysadmin-session-closer.md → agents/finish-up.md
- Updated agent version to 1.1.0
- Modified agent to include VPS hostname in session summary filenames
  - Session summaries now use format: [PROJECT_NAME]-[HOSTNAME]-session-summary.md
  - Hostname is auto-detected using `hostname` command
- Updated all documentation references:
  - README.md, QUICK-START.md, agents/README.md
  - scripts/README.md, scripts/bootstrap-agents.sh, scripts/init-project.sh
- Improved agent description to mention VPS hostname functionality

Repository: http://100.120.125.113:3000/pdm/homelab-agents
Next Session Focus: Test the renamed agent on a VPS project to verify hostname detection works correctly

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

agents/README.md

@@ -2,5 +2,5 @@
 
 Agent prompt definitions for use across the homelab.
 
-## sysadmin-session-closer
-Automatically closes development sessions and creates session summaries.
+## finish-up
+Automatically closes development sessions and creates session summaries with VPS hostname in the filename.

agents/finish-up.md

@@ -1,12 +1,12 @@
 ---
-name: sysadmin-session-closer
+name: finish-up
 description: Use this agent when the user indicates they want to end a homelab or system administration work session and preserve the context for future work. Trigger this agent when the user says phrases like: 'wrap up this session', 'close this session', 'save my progress', 'I'm done for today', 'end session', or 'commit and save everything'. This agent should also be used proactively when a significant milestone has been reached and the user asks to save their work.
 model: sonnet
-version: 1.0.0
+version: 1.1.0
 color: red
 ---
 
-# Sysadmin Session Closer Agent
+# Finish Up Agent
 
 Automatically closes development sessions and generates comprehensive session summaries for Gitea-based workflows.
 
@@ -75,7 +75,7 @@ Analyze the **entire conversation history** to extract:
 - Evolution of design/implementation approach
 - Dependencies or prerequisites for next steps
 
-**Action:** Create or update `[PROJECT_NAME]-session-summary.md` with this comprehensive summary. Extract PROJECT_NAME from existing project files (README.md, package.json, docker-compose.yml, or directory name). Structure the summary with clear markdown sections.
+**Action:** Create or update `[PROJECT_NAME]-[HOSTNAME]-session-summary.md` with this comprehensive summary. Extract PROJECT_NAME from existing project files (README.md, package.json, docker-compose.yml, or directory name). Extract HOSTNAME using the `hostname` command to identify which VPS this session was on. Structure the summary with clear markdown sections.
 
 ### Step 2: Create or Update Project README
 
@@ -97,7 +97,7 @@ Keep this high-level and suitable for someone discovering the project.
 
 Ensure these files are current:
 
-- `[PROJECT_NAME]-session-summary.md` - Comprehensive session summary from Step 1
+- `[PROJECT_NAME]-[HOSTNAME]-session-summary.md` - Comprehensive session summary from Step 1
 - `architecture.md` or `DESIGN.md` - If architecture decisions were made
 - Implementation files - Code, configurations, scripts modified
 - `TODO.md` - Task tracking with completed and remaining items
@@ -285,7 +285,7 @@ Provide the user with a clear summary:
 [The most important thing to tackle next, with brief context]
 
 ### Documentation Updated:
-- ✓ Session summary: `[PROJECT_NAME]-session-summary.md`
+- ✓ Session summary: `[PROJECT_NAME]-[HOSTNAME]-session-summary.md`
 - ✓ Project README: `README.md`
 - ✓ AI context: `CLAUDE.md` with new session entry
 - ✓ Git repository: Pushed to Gitea