Simplify session summary filename format

Changed filename from [PROJECT_NAME]-[HOSTNAME]-session-summary.md
to [HOSTNAME]-session-summary.md

Rationale:
- Session summary is saved inside project directory
- Project name in filename is redundant
- Simpler, cleaner filename
- No timestamp (overwrites each session)

Updated files:
- agents/finish-up.md: Updated filename format in Steps 1, 3, and 7
- CLAUDE.md: Updated agent naming convention and session history
- WORKFLOW.md: Updated agent behavior description

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

CLAUDE.md

@@ -57,7 +57,7 @@ This is a shared repository containing Claude Code agents that can be deployed a
 **Agent Naming Convention:**
 - Agent files: `agents/{agent-name}.md`
 - Invocation: Match the filename (e.g., "finish-up" agent)
-- Session files: `[PROJECT_NAME]-[HOSTNAME]-session-summary.md`
+- Session files: `[HOSTNAME]-session-summary.md`
 
 ### Technical Decisions
 
@@ -115,7 +115,7 @@ This is a shared repository containing Claude Code agents that can be deployed a
   - Created CLAUDE.md for future context preservation
 - **Key Decisions**:
   - No changes needed - all requested features already implemented
-  - Session summary filename format confirmed: `[PROJECT_NAME]-[HOSTNAME]-session-summary.md`
+  - Session summary filename format updated: `[HOSTNAME]-session-summary.md` (project name removed as redundant)
 - **Next Steps** (Prioritized):
   - Test Finish Up Agent on this VPS to verify proper operation
   - Consider deploying agents to additional VPS instances

WORKFLOW.md

@@ -31,7 +31,7 @@ Edit files, configure systems, write code...
 In Claude Code, say: **"finish up"**
 
 The agent automatically:
-- Creates session summary: `{project-name}-{hostname}-session-summary.md`
+- Creates session summary: `{hostname}-session-summary.md`
 - Updates CLAUDE.md and README.md
 - Commits and pushes to: `http://100.120.125.113:3000/pdm/{project-name}.git`
 

agents/finish-up.md

@@ -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]-[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.
+**Action:** Create or update `[HOSTNAME]-session-summary.md` with this comprehensive summary. 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]-[HOSTNAME]-session-summary.md` - Comprehensive session summary from Step 1
+- `[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]-[HOSTNAME]-session-summary.md`
+- ✓ Session summary: `[HOSTNAME]-session-summary.md`
 - ✓ Project README: `README.md`
 - ✓ AI context: `CLAUDE.md` with new session entry
 - ✓ Git repository: Pushed to Gitea