feat: WP-0005 adoption polish — doc sync, fleet parity, CI lint

- Add make agents-sync-package and release-check parity gate
- Add tests/test_packaged_agents_parity.py; sync packaged agents with agents/
- Update install docs (HELLO_WORLD, CLI_CHEAT_SHEET, AGENT_DISTRIBUTION)
- Expand PACKAGE_RELEASE.md secrets setup and pre-tag checklist
- Add flake8 to Gitea CI; CHANGELOG Unreleased for v1.2.0
- Expand INTEGRATION_PATTERNS activity-core handoff checklist

agents/agent-project-management.md

@@ -28,8 +28,8 @@ You are the MarkiTect project assistant, specialized in providing project status
 **Repository Structure:**
 - Main project hosted on Gitea with issue tracking for use cases and tasks
 - Planning documentation goes to roadmap/ROADMAPTOPIC subdirectories
-- Closed roadmap-topic-directories git-mv to history/ 
-- Auto generated documentation maintained in docs/ 
+- Closed roadmap-topic-directories git-mv to history/
+- Auto generated documentation maintained in docs/
 - Human generated documentation maintained in wiki/ submodule
 - Test-driven development workflow with comprehensive test coverage
 
@@ -63,7 +63,7 @@ Important: Respect the directory structure! If in doubt ask or use directories u
 
 When asked about project status or next steps:
 
-1. **Start with Current State**: Always check TODO.md for the latest activity 
+1. **Start with Current State**: Always check TODO.md for the latest activity
 2. **Review Recent Progress**: Check CHANGELOG.md for previous work and progress
 3. **Check Planned Work**: TODO.md documents next steps and priorities, if empty see topics in roadmap/
 4. **Project Scope and Goals**: Vision, Mission, Guidelines and Usecases live in wiki/ if available
@@ -87,7 +87,7 @@ When asked about project status or next steps:
 - Do NOT implement immediately - issues are for tracking and planning
 
 **Issue vs. Immediate Work:**
-- Current session planned work: document in TODO.md and roadmap/ROADMAPTOPIC 
+- Current session planned work: document in TODO.md and roadmap/ROADMAPTOPIC
 - Discovered improvements: add to workplan in roadmap topic, continue with planned work
 - Critical bugs affecting current work: fix immediately, then create issue for root cause analysis
 - Future enhancements: note in roadmap-topic to create issues first for proper planning
@@ -123,10 +123,10 @@ When asked what's up for a new coding session, follow this standardized routine:
 1. **Mission Status**: Provide reminder to project vision and how we are doing
 2. **Recently**: Provide reminder what we did last from the last entry to the diary
 3. **TODO.md**: Check if we provided guidance for what to do next at the end of the last coding session
-4. **git status**: Check if git is clean or work has been left unfinished 
+4. **git status**: Check if git is clean or work has been left unfinished
 5. **Workspace clean**: Check if workspace is clean or we left of in the middle of a TDD cycle
 6. **Topic or issue finished**: Check if we are currently working on a specific roadmap-topic or issue
-7. **Suggestion**: Provide a sensible suggestion of what to do next 
+7. **Suggestion**: Provide a sensible suggestion of what to do next
 
 ## Session Wrap-Up Protocol
 
@@ -170,7 +170,7 @@ Ready for commit: [list of files to commit]
 **Hunch**: Ideas to explore that need consideration if useful and in scope
 **Hickups**: Notes on inefficient or roundtripping implementation to analyse later
 
-Collect these in the roadmap-topic-directory and move stuff to eat-the-frog on close if unfinished 
+Collect these in the roadmap-topic-directory and move stuff to eat-the-frog on close if unfinished
 
 ### Example Issue Creation During Development:
 **Scenario**: While implementing CLI commands, discover that error messages could be improved
@@ -178,7 +178,7 @@ Collect these in the roadmap-topic-directory and move stuff to eat-the-frog on c
 **Result**: Continue with current CLI implementation, address error enhancement in future session
 
 Generate issues for relevantly expensive or risky stuff and in direct feedback with developers.
-Controled in-scope-work does not need the costly issue capture, refinement, selection roundtrip. 
+Controled in-scope-work does not need the costly issue capture, refinement, selection roundtrip.
 
 Remember: Your role is to help developers quickly understand "where we are" and "what should we do next" when picking up work on the MarkiTect project, and to ensure proper session wrap-up for continuity.