القائمة
Implement ntn-metrics-emulator features TDD-style — red commit (failing test) → green commit (impl) → refactor. Strictly per SPEC-002 + metrics.schema.json.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run + interpret + extend the real-secrets scan. Pre-commit, pre-PR, pre-release gate. (Folder name retains "anonymity" for backwards-link compat; the anonymity-scan was retired 2026-05-01 — see CLAUDE.md §2.1.)
Audit every pitch / docs claim into one of {implemented, simulated, planned, external_reference}. Block over-claiming.
Make the AC-004 demo replay deterministic, recordable, and resilient to network blips / LLM provider failure.
Build / iterate the kind / k3d / Kustomize / Helm demo deployment. Use for any change under deploy/ or packages/nephio-stubs/.
Review copilot-api responses to ensure every answer cites metrics/logs evidence. Block any response that hallucinates or leaks system prompt.
Design and validate NTN scenarios (beam-degradation, handover-failure, gateway-fallback) — JSON conforming to scenario.schema.json with realistic Rel-19 wording.
| name | metrics-emulator-tdd |
| description | Implement ntn-metrics-emulator features TDD-style — red commit (failing test) → green commit (impl) → refactor. Strictly per SPEC-002 + metrics.schema.json. |
The disciplined workflow for landing slices in services/ntn-metrics-emulator/. Pure-function tick model (scenario, t) -> metrics exposed as Prometheus exposition at /metrics. Every metric obeys tests/contracts/metrics.schema.json.
/implement SPEC-002.docs/specs/SPEC-002-ntn-metrics-emulator.mddocs/acceptance/AC-001 / AC-002 / AC-004 .mdtests/contracts/metrics.schema.jsonservices/ntn-metrics-emulator/tests/test_spec_002_red.pytest_spec_002_red.py. If none, write one (assert against the future SPEC behavior, mark @pytest.mark.xfail(strict=True)).red(SPEC-002): test_<feature_name> documents future behavior.@pytest.mark.xfail in a separate commit titled tdd(SPEC-002): unmark <test> for implementation.services/ntn-metrics-emulator/src/ntn_metrics_emulator/ to make it green. Use prometheus-client Gauge/Counter per metrics.schema enum. Keep tick deterministic.feat(SPEC-002): <feature>.pytest services/ntn-metrics-emulator/tests -q — green../verify.sh — all 6 gates green.docs/agile/backlog.md mark slice complete; PROJECT_STATUS.md updated.Three (or more) commits in this exact order:
red(SPEC-002): ... — test added, marked xfail-strict, fails as documented.tdd(SPEC-002): unmark ... — xfail removed, test now actually fails.feat(SPEC-002): ... — implementation, test green.git log --oneline -5 must show this red→unmark→green pattern.
pytest services/ntn-metrics-emulator/tests -q -v green; XFAIL count consistent with remaining unimplemented red tests.curl localhost:8000/metrics | grep orbitops_ returns expected gauges../verify.sh 6/6.tests/contracts/metrics.schema.json enum.random() without seed) — break golden replay.copilot-api).Gauge.labels(**arbitrary_labels).