chore: 179 - Add a trace function or API response that connects job -> result ->

[Exohayvan]

Roadmap step

phase-1/step-179: Step 179 - Add a trace function or API response that connects job -> result ->

Objective

Complete the selected roadmap step using only the programmatically selected step details.

Selected step

# Step 179 - Add a trace function or API response that connects job -> result ->

## Source Checklist Item
- [ ] Add a trace function or API response that connects job -> result -> validation receipt -> contribution -> manifest -> creator node ID.

## Goal
Provide a local-first trace path that lets a developer inspect how a completed job produced a result, how that result was validated, how it became a contribution record, which manifest declared the work context, and which preserved creator node ID is credited. The trace must be honest, deterministic, and limited to local prototype attribution evidence.

## Implementation Checklist
- [ ] Add a trace function or read-only API response that accepts a job ID and returns the linked result ID, validation receipt ID, contribution ID, manifest ID, and creator node ID.
- [ ] Include lineage fields that show direct references between each record instead of inferring attribution from names, timestamps, or loose metadata.
- [ ] Preserve existing creator node ID values exactly; do not regenerate, normalize, or replace them during trace assembly.
- [ ] Return missing-link errors clearly when any required record is absent, invalid, or not connected.
- [ ] Keep the response local-only and avoid adding dashboards, rewards, token values, network claims, or later-phase federation behavior.

## Required Tests Or Verification
- [ ] Create or use a local fixture where one job links to one result, one validation receipt, one contribution, one manifest, and one creator node ID.
- [ ] Verify the trace response returns the full chain in order: job -> result -> validation receipt -> contribution -> manifest -> creator node ID.
- [ ] Verify attribution fails closed when the validation receipt or manifest does not match the contribution lineage.
- [ ] Verify creator node ID is preserved byte-for-byte from the manifest or node identity source.
- [ ] Verify no tokenomics, dashboard-only data, or fake decentralization fields are introduced.

## Risks
- [ ] Loose joins can create false attribution. Overeager fallbacks can hide broken lineage. Scope creep could turn a trace endpoint into a dashboard or rewards system before validation is trustworthy.

## Done When
- [ ] A local developer can query one job ID and receive a validation-gated attribution chain that proves which result, receipt, contribution, manifest, and creator node ID are connected, with clear failure behavior for incomplete or mismatched lineage.

Changes

420df60 chore: complete phase-1 step-179
 src/aethermesh_core/api.py             |  12 ++++
 src/aethermesh_core/runtime_service.py | 126 +++++++++++++++++++++++++++++++++
 tests/test_runtime_service_api_cli.py  |  82 +++++++++++++++++++++
 3 files changed, 220 insertions(+)

Validation

• PYTHONDONTWRITEBYTECODE=1 python3 scripts/full_test.py --mode fast --base origin/main --keep-going

Safety notes

• Roadmap selection was performed by the Python loop, not by the AI agent.
• No force push used.
• No hard reset used.
• Local automation paths are intentionally omitted.