feat: close the management planning and delivery loop

.evozeus-wrapper/CHANGELOG.md

@@ -6,23 +6,37 @@ Wrapper harness migrations are recorded under `.evozeus-wrapper/docs/migrations/
 
 ## [Unreleased]
 
+- No unreleased changes.
+
+## [v0.2.0] - 2026-07-20
+
 ### Skill changes
 
-- Upgraded the embedded EvoZeus-wrapper harness from v0.9.1 to v0.10.0.
-- Applied the v0.10.1 patch that preserves target-owned Markdown boundaries during harness refresh.
-- Clarified that the project hook covers canonical-repository maintenance while Skill-entry preflight remains prompt-enforced.
+- Added an outcome contract for task identity, deliverables, carriers, acceptance, dependencies, deadlines, work phases, and source references.
+- Added the weekly cascade from project milestone to personal weekly outcome to today's task, plus an owned `pending_sync` queue for oral or chat-sourced orphan work.
+- Added active portfolio filtering, workstream splitting, baseline versioning, formal-effort boundaries, evidence-based weighted progress, leave-adjusted capacity, and WIP checks.
+- Added explicit draft, approval, publish, receipt, and recall gates for management messages.
+- Added structured Base fallback fields, synthetic regression scenarios, and automated contract tests.
+- Upgraded the embedded EvoZeus-wrapper harness from v0.9.1 through v0.10.1 and clarified the boundary between repository maintenance hooks and prompt-enforced Skill-entry checks.
 
 ### Feedback / Issues
 
+- MetaInFLow/metainflow-dev-tasks#3: close the management planning and delivery loop.
 - MetaInFLow/EvoZeus-wrapper#12: correct hook capability scope and add the global session dispatcher lifecycle.
 - MetaInFLow/EvoZeus-wrapper#14: preserve target headings and accurate layout labels during harness refresh.
+- Design: `.evozeus-wrapper/docs/designs/2026-07-20-management-planning-delivery-loop-v0.2.0.md`.
 
 ### Verification
 
+- `python3 -m unittest discover -s tests -p 'test_*.py'`
 - `python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py structure`
 - `python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py doctor --repo MetaInFLow/metainflow-dev-tasks`
-- Skill format validation and repository hook adapter smoke test.
-- Confirmed the v0.10.1 refresh changed only wrapper-owned version references and appended the correct version-refresh note in `SKILL.md`.
+- Skill format validation, eval JSON parsing, repository hook adapter smoke test, PR preflight, and release preflight.
+
+### Data boundary and rollback
+
+- Public artifacts use synthetic examples and contain no raw chats, customer records, internal links, Base tokens, or credentials.
+- Roll back by restoring the `v0.1.0` Skill release; wrapper harness state remains independent at `v0.10.1`.
 
 
 

.evozeus-wrapper/docs/designs/2026-07-20-management-planning-delivery-loop-v0.2.0.md

@@ -0,0 +1,64 @@
+# Management Planning And Delivery Loop v0.2.0
+
+## Related Issue
+
+Related issue: MetaInFLow/metainflow-dev-tasks#3.
+
+## Optimization Goal
+
+Turn the current evidence-gathering Skill into a closed-loop management system. Every active project and assigned task should expose its intended outcome, weekly milestone mapping, plan version, progress basis, synchronization responsibility, capacity impact, and publication authorization state.
+
+The change must preserve existing Base routing and project-specific evidence rules while preventing vague assignments, orphan verbal tasks, silent rebaselines, unsupported progress percentages, polluted active worksets, and unauthorized team-message publication.
+
+## Direction
+
+1. Keep concise mandatory gates in `SKILL.md` so they execute on every relevant invocation.
+2. Put detailed field contracts, formulas, status models, output shapes, and fallback storage rules in `references/management-contracts.md`.
+3. Extend `references/schema.md` with recommended management fields and structured-note fallbacks when the live Base lacks dedicated columns.
+4. Add public-safe regression scenarios under `evals/evals.json` and deterministic structural tests under `tests/`.
+5. Keep every example synthetic. Do not publish customer, employee, project, chat, document, Base, or credential data.
+
+## Implementation Plan
+
+### Task Outcome And Identity
+
+- Require a canonical identity composed of project/workstream, module, action, and deliverable.
+- Require deliverable, carrier, acceptance criteria, acceptance owner, dependency, due datetime, and work phase before an assignment is considered complete.
+- Use an `input -> processing -> result -> carrier -> acceptance` outcome chain for analytical and knowledge-work tasks.
+
+### Oral Task And Synchronization Closure
+
+- Convert explicit tasks from plans, meetings, and communication into mapped Base subtasks within the same management cycle.
+- Keep unmapped items in an orphan queue with source reference, candidate project, owner, synchronization target, due time, and closure state.
+- Give every `pending_sync` item an owner and SLA; never leave it as an informational label.
+
+### Weekly Cascade And Portfolio Scope
+
+- Require `project weekly milestone -> personal weekly outcome -> daily task` traceability.
+- Classify portfolio items as active, paused, completed, observation, or excluded; only active work contributes to current progress and load.
+- Split a project into workstreams when scope, baseline, owner, dependency, or customer timing differs materially.
+
+### Baseline, Effort, And Progress
+
+- Version original baseline, current forecast, and approved rebaseline separately.
+- Record change reason, approver, effective time, impacted workstream, and before/after variance.
+- Classify effort as exploration, formal execution, rework, customer waiting, or internal blocking; formal project actuals start at approved execution kickoff.
+- Calculate overall progress only from a frozen workstream/milestone denominator and evidence-backed completion coefficients. Without that contract, output schedule health and missing data instead of an exact percentage.
+
+### Capacity And Publication Gates
+
+- Evaluate capacity after leave, existing WIP, dependencies, review/test duties, and configured WIP limits. Do not invent utilization when capacity is unknown.
+- Distinguish draft generation from publication authorization. Require explicit approval of final content and destination; any material revision invalidates prior approval.
+- Return publication receipt evidence after sending and support recall when explicitly requested.
+
+## Verification Plan
+
+1. Add failing structural tests for the missing sections, required fields, progress formula, work-phase vocabulary, active-workset states, orphan-task SLA, and publication authorization gate.
+2. Add synthetic eval scenarios covering vague assignments, meeting-derived orphan tasks, partial customer delay, unsupported progress requests, leave-adjusted workload, and draft-versus-publish intent.
+3. Run the deterministic tests before implementation to demonstrate RED.
+4. Implement the Skill and reference changes, then rerun tests to GREEN.
+5. Run Skill format validation, wrapper structure/doctor/version checks, PR preflight, JSON validation, and GitHub PR checks.
+
+## Release Plan
+
+Release as Skill `v0.2.0` because this adds new required management behavior and output contracts. Update `.evozeus-wrapper/CHANGELOG.md`, merge through a reviewed PR, publish release notes that reference Issue #3, and confirm the runtime symlink still points to the canonical repository. Roll back by reverting the release PR and repointing to `v0.1.0` if the new gates block valid workflows.