chore: 185 - Advertise capabilities

[Exohayvan]

Roadmap step

phase-1/step-185: Step 185 - Advertise capabilities

Objective

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

Selected step

# Step 185 - Advertise capabilities

## Source Checklist Item
- [ ] Advertise capabilities.

## Goal
Define and expose a local-first capability advertisement flow so a prototype node can honestly describe what work it can perform, under which constraints, and with which validation requirements. The advertisement must preserve the creator node ID, manifest linkage, lineage, and contribution attribution without implying production decentralization, rewards, tokenomics, or frontier-grade capability.

## Implementation Checklist
- [ ] Add a local capability advertisement record that includes node ID, supported task types, runtime limits, required inputs, expected outputs, validation method, manifest reference, and contribution attribution fields.
- [ ] Ensure the advertisement is generated from local configuration and current manifests rather than hardcoded claims.
- [ ] Include lineage fields linking the advertised capability to the node manifest, validation receipt format, and any local work/result manifest it may produce.
- [ ] Mark every advertised capability with clear prototype status, local scope, and validation requirements.
- [ ] Reject or omit capabilities that do not have a matching local executor, manifest definition, or validation path.
- [ ] Store the advertisement in a deterministic local artifact that can be read by later local flow steps.

## Required Tests Or Verification
- [ ] Verify a node can emit a capability advertisement containing the correct creator node ID and manifest references.
- [ ] Verify unsupported or unvalidated capabilities are not advertised.
- [ ] Verify the artifact is deterministic across repeated runs with the same inputs.
- [ ] Verify advertised capabilities can be traced to local validation and contribution attribution metadata.

## Risks
- [ ] Capability claims may drift from what the local prototype can actually execute.
- [ ] Missing lineage or attribution fields could make later contribution tracking unreliable.
- [ ] Overstated wording could imply decentralization or production readiness before validation exists.

## Done When
- [ ] A local node produces an honest capability advertisement artifact.
- [ ] Each advertised capability is manifest-linked, validation-gated, and attribution-ready.
- [ ] Tests confirm unsupported claims are excluded and required lineage fields are preserved.

Changes

314ab3d chore: complete phase-1 step-185
 src/aethermesh_core/runtime_service.py | 132 +++++++++++++++++++++++++++++++++
 tests/test_capability_advertisement.py | 105 ++++++++++++++++++++++++++
 2 files changed, 237 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.