chore: 148 - Include timestamps and IDs needed to reconstruct a local run

[Exohayvan]

Roadmap step

phase-1/step-148: Step 148 - Include timestamps and IDs needed to reconstruct a local run

Objective

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

Selected step

# Step 148 - Include timestamps and IDs needed to reconstruct a local run

## Source Checklist Item
- [ ] Include timestamps and IDs needed to reconstruct a local run.

## Goal
Ensure every local audit log entry includes the minimum timestamp and identifier fields needed to reconstruct what happened during a single local AetherMesh run, without relying on external services, dashboards, or unverifiable claims.

## Implementation Checklist
- [ ] Add a required local run timestamp using an unambiguous format such as UTC ISO-8601.
- [ ] Include a stable local run ID generated at run start and reused across all audit entries for that run.
- [ ] Include the creator node ID on every relevant audit entry so work remains attributable.
- [ ] Include work item IDs, validation IDs, manifest IDs, receipt IDs, and lineage IDs when those objects are created, read, validated, or linked.
- [ ] Record event sequence numbers or monotonic offsets so entries can be ordered even if timestamps collide.
- [ ] Include parent/child linkage fields when a result depends on prior manifests, validation receipts, or contribution records.
- [ ] Keep IDs local-first and deterministic where appropriate, while avoiding fake network identity or decentralization claims.
- [ ] Document the required audit fields near the audit log schema or writer code.

## Required Tests Or Verification
- [ ] Run a local prototype flow and confirm each audit entry contains timestamp, run ID, creator node ID, and relevant object IDs.
- [ ] Verify entries can be sorted into the original local run order.
- [ ] Verify validation receipts and contribution attribution can be traced back to the originating manifest and run.

## Risks
- [ ] Missing IDs make validation, lineage, or contribution attribution impossible to reconstruct.
- [ ] Local timestamps without timezone or ordering metadata may create ambiguous audit trails.
- [ ] Overbroad fields may leak unnecessary local system details.

## Done When
- [ ] A local run can be reconstructed from audit logs using timestamps, run ID, creator node ID, object IDs, sequence/order fields, validation receipts, lineage references, and contribution attribution.

Changes

702935b chore: complete phase-1 step-148
 src/aethermesh_core/contribution_record.py |  1 +
 src/aethermesh_core/local_audit_event.py   | 18 +++++++++++++-
 src/aethermesh_core/local_shutdown.py      |  1 +
 src/aethermesh_core/local_startup.py       |  5 +++-
 src/aethermesh_core/runtime_service.py     |  5 ++++
 tests/test_local_audit_event.py            |  3 +++
 tests/test_runtime_service_api_cli.py      | 39 ++++++++++++++++++++++++++++++
 7 files changed, 70 insertions(+), 2 deletions(-)

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.