[Core]: Spectrum services[] — runtime field-service activation at session open

[rosspeili]

Component

constraints / policy

Kind

enhancement

Description

#27 shipped spectrum.level egress bind (low/mid/high/full) and stores spectrum.services[] on profiles. Today services are metadata only — summarized on membrane.ingress and session.open, but they do not auto-attach observer presets, Limit hooks, or field-service modules at runtime.

Ship:

• Map spectrum.services entries (monitor, audit, break, future limit) to concrete session wiring at open (preset attach, egress hooks, or no-op with spine note)
• Default services when unset remain ["monitor", "audit"] per aura-levels.md
• full + break in services enables Break preset without duplicating profile observers[] boilerplate (optional convenience path — explicit observers still wins)
• Tests: same profile, two service lists — Monitor notes present vs absent
• Docs: field-services.md, ROADMAP.md

Out of scope: replacing spectrum.level enforcement (already in spectrum_enforcement.py).

Code or session context (optional)

• aura/core/spectrum.py — planes() already derives escalate from services
• aura/core/session.py — _attach_profile_observers() at open
• scripts/aura_coat_flow_report.py — reference flow for tailored + services