observe(api,bench): carry process CPU on every construction operation (#1462)

[DecisionNerd]

Stacked on #1470. Base is observe/1462-effective-cores; review that one first. #1470 adds the measurement, this makes something call it.

Why

#1470 established an instrument that can be trusted. Nothing called it. This wires it into the four construction operations the receipt already delimits, so #1387's serialized-fraction budget is readable off an ordinary run instead of inferred from phase totals.

ImportCallTiming gains cpu_ns and cpu_unmeasured_calls, plus effective_cores() as their ratio against elapsed_ns. CallStart captures wall and CPU together at the four sites that previously captured only Instant::now().

seal.effective_cores() is the number the budget is read from — seal is 68–80% of ingest, and #1387 needs the serial region under ~10% on 16 threads.

effective_cores() returns None when no wall elapsed or any call's CPU could not be read, so an operation that never ran cannot be mistaken for one that ran on no CPU. The test asserts exactly that for the publish that never happens.

Two fail-closed surfaces this had to move with it

Both would have failed the ladder rather than this PR's own tests, which is why they are worth calling out.

benchmarks/schemas/certification-evidence.json declares additionalProperties: false over importCallTiming. Serializing two new fields would have failed harness validation outright.

They are added as optional, not required. Required rejects every bundle recorded before this change — including the S18–S24 evidence in clean-f80f69fe-evidence/ that the harness must still read. I tried required first; it failed three harness tests with 'cpu_ns' is a required property.

benchmarks/harness/graphforge_bench/lifecycle_runtime.py seeded its accumulator with a fixed three keys and then ran total[key] += value over whatever the receipt carried — a KeyError on any field added after it was written. Now total.get(key, 0) + value, which tolerates the next addition too.

It also surfaces construction_call_effective_cores per operation in the rung summary: omitted when CPU was unavailable, and absent entirely for historical bundles, matching how lifecycle_application_io already handles evidence predating its instrumentation.

Verification

• graphforge-api lib: 745 passed / 0 failed, including a new end-to-end test that runs a real import and asserts begin/append/seal all report CPU and a defined effective_cores().
• Benchmark harness via CI's own invocation (PYTHONPATH=harness uv run --locked python -m unittest): 97 passed.
• cargo clippy --workspace -- -D warnings: exit 0. cargo fmt --all -- --check: clean. uv run ruff format --check .: clean. make pre-push-fast: passed.

What this still does not do

It reports effective cores. It does not yet report a serial fraction on the rung, because that needs the worker count the operation actually ran with, and serial_fraction() in #1470 takes it as an argument for that reason. Once #1466 lands and the default resource policy stops pinning two workers, the worker count becomes meaningful and the derivation can be surfaced. Until then effective cores is the honest figure and the derived one would be misleading.

Refs #1462

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 356d6992-2b0c-41e3-aeaa-93cdfb8cbf90

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}