v0.3.14 — capture stamps feature_id/story_id (per-feature dashboard scoping)

The per-test capture now stamps each line with feature_id/story_id so the dashboard scopes reads/writes per feature. Test ids repeat across features (F1 and F2 may both have a T40); an unstamped log commingled their reads under one id. Now:

• app/consort_capture.py stamps each interaction from .consort/next.json (active feature) + the feature's pipeline.json build_active (active story; null during a whole-feature deploy).
• consort-capture.ts emitTableSnapshot stamps each snapshot via resolveOwner (scenario_file + active-feature).
• Unstamped older corpora stay back-compat (kept by test id); the stamp is forward-only.

Full suite 1318 green.