feat(agents): add engagement reporting package

[tasdevani21]

Summary

Add a reusable Engagement Reporting package to HVE Core for source-grounded weekly status reports. The package coordinates evidence collection, report synthesis, review, optional Council critique, explicit user approval, and optional Outlook draft creation.

Problem

Engagement teams repeatedly assemble status reports from Microsoft 365, delivery boards, transcripts, and previous reports without a shared HVE Core workflow. Ad hoc reporting can blur primary evidence with historical context, overstate delivery status, retain unnecessary source data, or treat report approval as approval to distribute.

Outlook distribution also needs an explicit formatting contract. An approved Markdown report must be rendered as HTML without flattening headings, links, lists, emphasis, or tables. If faithful conversion is unavailable, draft creation must stop rather than fall back to plain text.

Proposed contribution

• Add an interactive Engagement Report Generator agent.
• Add delegated Council Critic, Council Arbiter, and Engagement Report Reviewer agents.
• Add data-handling, style, and terminology instructions.
• Add an independent Council critique prompt.
• Add the Engagement Reporting skill with a workspace configuration template, weekly report template, and research, report, and distribution contracts.
• Add generated reference documentation and plugin-manifest registration.
• Add advisory Vally coverage for every contributed agent, prompt, instruction, and skill surface.

Behavioral boundaries

• Material report claims trace to primary evidence.
• Previous reports provide continuity context, not factual evidence.
• Coverage or verification gaps stop finalization instead of being filled with assumptions.
• Report approval and Outlook draft approval are separate decisions.
• Outlook integration creates at most one approved draft through /me/messages.
• Outlook draft bodies use contentType: "HTML" and preserve <table> markup for tabular reports.
• Draft creation stops if faithful HTML conversion is unavailable; it never falls back to flattened text.
• The workflow never sends, replies to, forwards, or publishes content.
• Working evidence and customer configuration remain local and excluded from version control.
• The package declares no hooks.

Acceptance criteria

• HVE Core includes the four Engagement Reporting agents.
• HVE Core includes the reporting prompt, three instructions, and skill.
• The plugin manifest includes the complete package and no hooks.
• Reference documentation explains setup, invocation, approval, retention, and HTML-only Outlook draft behavior.
• Eval coverage links every contributed AI artifact to at least one advisory stimulus.
• Validation confirms manifest, documentation, skill structure, eval schema, stimulus presence, and safety consistency.
• A maintainer reviews the contribution against HVE Core AI-artifact standards.