Define a resource and energy baseline per verified workload

[ta2jam]

Problem

Morfeus cannot make a defensible green-software claim without a stable functional unit and measurement boundary. Attempt count or model calls are manipulable denominators.

Desired outcome

Create a reproducible local benchmark manifest using one acceptance-verified workload as the primary functional unit. Record at least wall time, CPU time, peak RSS, bytes read/written, stored bytes, and retry waste. Energy values must be marked measured, estimated, or unknown.

Acceptance

• Benchmark inputs and acceptance output are content-pinned.
• Baseline can be rerun on Python 3.11+ without third-party runtime dependencies.
• Failed and retried attempts remain inside the reported workload cost.
• Results include platform, methodology, sample count, variance, and limitations.
• No carbon number is produced without a declared SCI boundary, signal source, and uncertainty.

Reference: Green Software Foundation SCI 1.1 and docs/ROADMAP.md.