chore: 180 - Add tests proving output can be traced back to creator node ID

[Exohayvan]

Roadmap step

phase-1/step-180: Step 180 - Add tests proving output can be traced back to creator node ID

Objective

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

Selected step

# Step 180 - Add tests proving output can be traced back to creator node ID

## Source Checklist Item
- [ ] Add tests proving output can be traced back to creator node ID.

## Goal
Prove that every locally generated model or expert output carries enough attribution to trace it back to the creator node ID that produced it. The test should validate the Phase 1 local prototype behavior only: output records must preserve creator node ID, manifest reference, validation receipt linkage, lineage metadata, and contribution attribution without implying production decentralization or rewards.

## Implementation Checklist
- [ ] Identify the output record shape used for local model or expert results.
- [ ] Add a deterministic test fixture with a known creator node ID, input manifest, validation receipt, and lineage parent.
- [ ] Assert the generated output includes the exact creator node ID without rewriting, omitting, or replacing it.
- [ ] Assert the output attribution links back to the manifest or work descriptor that authorized the local run.
- [ ] Assert validation receipt metadata remains attached to the attributed output.
- [ ] Assert lineage metadata survives serialization and reload if output records are persisted locally.
- [ ] Keep the test local-first and avoid any network, tokenomics, dashboard, or later-phase assumptions.

## Required Tests Or Verification
- [ ] Unit test passes for output attribution from a known creator node ID.
- [ ] Serialization or persistence test proves creator node ID, manifest ID, validation receipt ID, and lineage fields round-trip correctly.
- [ ] Negative test fails when creator node ID is missing, empty, or mismatched.
- [ ] Test output is deterministic and can run in the normal local validation suite.

## Risks
- [ ] Attribution could be stored separately from output and become detached during persistence.
- [ ] Tests could overfit to one fixture instead of enforcing required attribution fields.
- [ ] Ambiguous field names could confuse creator identity with validator identity.

## Done When
- [ ] Local tests prove output can be traced back to the exact creator node ID.
- [ ] Tests also preserve manifest, validation, lineage, and contribution attribution links.
- [ ] Missing or mismatched creator node attribution causes validation failure.

Changes

2a349d7 chore: complete phase-1 step-180
 tests/test_job_result_schema.py | 67 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 67 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.