fix: statusline path resolution + audit report formalization

[dean0x]

Summary

This PR fixes the statusline script execution issue and formalizes the audit report storage structure across all agents. Additionally, it enhances the release agent with documentation verification and persistent release notes.

🔧 Bug Fixes

Statusline Path Resolution

Problem: Statusline script failed to execute because settings.json used ~/.devflow/scripts/statusline.sh but Claude Code doesn't expand tilde (~).

Solution: init.ts now reads the settings template and dynamically replaces ~ with the actual absolute path during installation.

Files Changed:

• src/cli/commands/init.ts - Template processing with path replacement

Impact: Statusline now works correctly on all installations.

✨ Features

1. Release Agent Enhancements

Release Notes Persistence:

• Saves comprehensive release notes to .docs/releases/RELEASE_NOTES_v<version>.md
• Includes version bump, changelog, commit history, build/test results, and distribution links

Documentation Verification:

• Checks ROADMAP.md for features to mark complete
• Verifies version references across all READMEs (monorepo support)
• Validates installation instruction consistency
• Confirms CHANGELOG.md has proper version entries and links
• Scans docs/ directories for outdated version references
• Provides search-and-replace commands for fixing mismatches

Files Changed:

• src/claude/agents/devflow/release.md - Added Steps 13-14
• src/cli/commands/init.ts - Creates .docs/releases/ directory

2. Audit Report Formalization

Standardized Directory Structure:

.docs/audits/
├── <branch-name>/
│   ├── security-report.<timestamp>.md
│   ├── performance-report.<timestamp>.md
│   ├── architecture-report.<timestamp>.md
│   ├── tests-report.<timestamp>.md
│   ├── complexity-report.<timestamp>.md
│   ├── dependencies-report.<timestamp>.md
│   ├── documentation-report.<timestamp>.md
│   ├── typescript-report.<timestamp>.md (if applicable)
│   ├── database-report.<timestamp>.md (if applicable)
│   └── comprehensive-review.<timestamp>.md
└── standalone/
    └── <audit-type>-report.<timestamp>.md

Orchestration Updates:

• /code-review command creates branch-specific audit directories
• Passes CURRENT_BRANCH, AUDIT_BASE_DIR, TIMESTAMP to all sub-agents
• Saves comprehensive review to branch directory
• Lists all individual audit report paths in final summary

Agent Standardization (all 9 audit agents):

• audit-security.md
• audit-performance.md
• audit-architecture.md
• audit-complexity.md
• audit-tests.md
• audit-dependencies.md
• audit-documentation.md
• audit-typescript.md
• audit-database.md

Each agent now:

• Receives orchestrator variables
• Saves to branch-specific location when invoked by /code-review
• Falls back to .docs/audits/standalone/ for direct invocations
• Uses consistent report structure with severity sections

Benefits:

• ✅ Organized by branch for tracking multiple reviews
• ✅ Timestamped for historical tracking and comparison
• ✅ Consistent naming across all audit types
• ✅ Supports both orchestrated and standalone invocations
• ✅ Easy audit artifact discovery and archival

3. Production Build Standards

Added comprehensive production build and test safety standards to src/claude/CLAUDE.md:

• Separate dev/prod build configurations
• Test suite safety (sequential execution, memory limits)
• Production artifact exclusion (no tests, sourcemaps, debug symbols)
• Build optimization best practices

📊 Impact

Lines Changed: 1024 insertions, 40 deletions across 13 files

Token Efficiency:

• Audit agents now have clear, consistent storage logic
• Reduced duplication across agent implementations

Developer Experience:

• Statusline works immediately after installation
• Release process catches documentation drift
• Audit reports are organized and discoverable
• Historical audit comparison now possible

🧪 Testing

• ✅ Built successfully (npm run build)
• ✅ Verified statusline path replacement logic
• ✅ Tested audit directory creation during init
• ✅ Confirmed all 9 audit agents have consistent Report Storage sections
• ✅ Validated release agent documentation verification steps

📝 Related Issues

• Part of statusline refinements discussion
• Addresses audit report organization needs
• Resolves release notes persistence request

🚀 Next Steps After Merge

1. Test installation with npx devflow-kit@latest init
2. Verify statusline execution
3. Run /code-review on a branch to test audit report organization
4. Prepare v0.3.3 patch release

---

🤖 Generated with Claude Code