fix(report): native --contents-file / stdin for entry submit + skill sync

[PeterGuy326]

Problem

dws report entry submit --contents-file <f> (and --contents - stdin) silently submitted contents: [null] and the report failed. Only inline --contents '[...]' worked — which is why the inline-only helper report create succeeded while report entry submit --contents-file did not.

Root cause is an architecture mismatch, not a single bad transform:

• report entry submit is an envelope-driven command (MCP tool create_report). Its --contents flag has json_parse (required); the sibling --contents-file has omitWhen empty but no transform / mapsTo, so its value mapped to the unused contentsFile param while the real contents stayed empty.
• The wukong reference reads the file/stdin natively in Go (resolveReportContentsFromFlags, priority --contents-file > --contents - > inline). The open edition already mirrors wukong on the read side via post-merge decorator hooks (AttachReportListReadableEnrichment), so this follows the same idiom.

Fix (no discovery-config change)

internal/compat/report_hooks.go — a build-time hook on the create_report leaf, wired beside the existing mail/todo/calendar/attendance hooks:

1. Clears the individual required on --contents and declares a contents / contents-file one-of group, so a --contents-file-only invocation is no longer rejected at parse time (validated before PreRunE).
2. A chained PreRunE reads the file/stdin (10MB cap, UTF-8 check) and writes the JSON back into --contents so the downstream json_parse decodes it uniformly; --contents-file is then cleared.

The existing cedar contentsFile flag declaration is kept — it is what registers the --contents-file flag the hook consumes. No Diamond / discovery change is required.

Skill sync

The multi/dingtalk-report skill tree was two versions behind mono (taught deprecated flat aliases; falsely claimed report inbox was unimplemented). Re-aligned SKILL.md + 05-reporting.md + mono intent-guide.md to the canonical template get / entry submit --contents-file / inbox list / outbox list / entry get / entry stats.

Verification

End-to-end against the live cedar envelope via --dry-run:

• --contents-file <f> (no --contents) → no required error; contents populated with the parsed array.
• --contents - (stdin) → populated from stdin.
• inline --contents → left untouched.
• neither → at least one of the flags in the group [contents contents-file] is required.

11 new unit tests in report_hooks_test.go; go test ./internal/compat/ ./internal/helpers/ ./internal/app/ green. Full wukong01 sandbox eval in progress.

[PeterGuy326]

Verification

1. Unit + dry-run (live cedar envelope)

go test ./internal/compat/ ./internal/helpers/ ./internal/app/ green; 11 new tests in report_hooks_test.go.

End-to-end report entry submit against the live cedar envelope via --dry-run:

Input	Result
--contents-file <f> (no --contents)	no required error; contents populated with the parsed array
--contents - (stdin)	populated from stdin
inline --contents '[...]'	left untouched
neither	at least one of the flags in the group [contents contents-file] is required

Before the fix the same --contents-file invocation sent contents: [null] and the report failed.

2. Full cli_to_mcp eval (wukong01 sandbox, PR binary)

Built this branch and ran the full open-edition suite as wukong01 (PAT scopes fully granted first):

• report: 4 passed / 0 failed → 100% — the fixed product, zero regression.
• 100% products: report, calendar, attendance, oa, doc, minutes, aisearch, drive, live.
• Aggregate 2358 cases, 77.6% — dragged down almost entirely by 363 sheet TIMEOUT errors (known infra issue, needs direct pytest) and the mail org-restriction (暂不支持阿里巴巴邮箱), neither related to this change.
• Every non-100% product was triaged to a pre-existing cause (sheet/aitable server timeout, contact HR-roster account permission, todo sub-task tool not yet exposed, chat group-history permission, wiki proxy route, devdoc pre-prod stub) — none caused by this change, which only adds a report-scoped compat hook plus one no-op-for-non-report hook call.

3. Discovery

No discovery-config change required. The cedar contentsFile flag declaration is kept — it is what registers the --contents-file flag the hook consumes; the hook resolves its value natively before json_parse runs.