chore: 183 - Start or initialize a local node

[Exohayvan]

Roadmap step

phase-1/step-183: Step 183 - Start or initialize a local node

Objective

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

Selected step

# Step 183 - Start or initialize a local node

## Source Checklist Item
- [ ] Start or initialize a local node.

## Goal
Bring up one local AetherMesh node in a repeatable, validation-gated way so the prototype can create or reuse its node identity, load required manifests, and become ready for local work-flow integration without pretending to be decentralized.

## Implementation Checklist
- [ ] Add or use a local node start command that runs entirely on the developer machine.
- [ ] If no local node state exists, initialize the node directory, creator node ID, manifest files, and required local configuration.
- [ ] If local node state already exists, reuse the existing creator node ID instead of regenerating it.
- [ ] Load startup manifests before accepting any local work.
- [ ] Record a startup validation receipt that includes node ID, manifest identifiers, timestamp, command invoked, and pass/fail status.
- [ ] Keep lineage and contribution attribution tied to the preserved creator node ID.
- [ ] Fail closed when identity, manifest, or validation data is missing or malformed.
- [ ] Keep the command local-only with no claims of network participation, rewards, production security, or decentralized consensus.

## Required Tests Or Verification
- [ ] Start from an empty local state and verify the node initializes successfully.
- [ ] Start again and verify the same creator node ID is preserved.
- [ ] Verify required manifests are present and loaded during startup.
- [ ] Verify a validation receipt is written for each start attempt.
- [ ] Verify malformed or missing manifests prevent startup with a clear local error.
- [ ] Verify no tokenomics, dashboard, external network, or MoE behavior is introduced.

## Risks
- [ ] Regenerating node identity could break lineage and contribution attribution.
- [ ] Starting without validated manifests could create untrustworthy local receipts.
- [ ] Overstating local startup as decentralization could misrepresent the prototype.

## Done When
- [ ] A local node can be initialized, restarted, validated, and traced through preserved identity, manifests, receipts, lineage, and attribution.

Changes

2d11eb1 chore: complete phase-1 step-183
 src/aethermesh_core/local_startup.py | 1 +
 tests/test_local_startup.py          | 8 ++++++++
 2 files changed, 9 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.