chore: 147 - Log contribution ledger update

[Exohayvan]

Roadmap step

phase-1/step-147: Step 147 - Log contribution ledger update

Objective

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

Selected step

# Step 147 - Log contribution ledger update

## Source Checklist Item
- [ ] Log contribution ledger update.

## Goal
Record every contribution ledger update as a local audit event so prototype runs can prove when contribution attribution changed, which node initiated it, what manifest or work receipt caused it, and which validation evidence supports the update. This step is audit-only: it must not introduce rewards, tokenomics, rankings, dashboards, or claims of decentralization.

## Implementation Checklist
- [ ] Add an audit log event for each contribution ledger update attempt, including success, rejection, and validation failure cases.
- [ ] Include the creator node ID, contributing node ID, work ID, manifest ID, validation receipt ID, lineage reference, timestamp, and deterministic ledger update ID when available.
- [ ] Store the audit entry locally in an append-only format suitable for replay during Phase 1 testing.
- [ ] Ensure the audit entry records the reason for the update without overstating trust, consensus, or network finality.
- [ ] Keep contribution attribution tied to validated work and manifests, not inferred reputation or reward value.
- [ ] Avoid logging secrets, private prompts, raw credentials, or unnecessary payload data.

## Required Tests Or Verification
- [ ] Run a local ledger update and verify exactly one audit entry is created.
- [ ] Run an invalid ledger update and verify the rejection is logged with validation failure context.
- [ ] Confirm audit entries preserve creator node ID, manifest reference, validation receipt, lineage, and contribution attribution.
- [ ] Confirm repeated test runs produce traceable, deterministic IDs where required.

## Risks
- [ ] Audit logs could imply stronger trust guarantees than the local prototype provides.
- [ ] Missing lineage or validation references could make contribution attribution unverifiable.
- [ ] Over-logging could expose sensitive local data.

## Done When
- [ ] Contribution ledger updates always emit local audit logs with validation-grounded attribution and replayable evidence references.

Changes

2c0145e chore: complete phase-1 step-147
 docs/local-audit-event-schema.md           |   6 +
 src/aethermesh_core/contribution_record.py | 184 ++++++++++++++++++++++-------
 tests/test_contribution_record.py          |  53 +++++++++
 3 files changed, 198 insertions(+), 45 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.