TeraStor Firmware Console

Mission Control

Phase A scaffold. Week 1 wires these cards to CV-Hub. staging

My open work

5 pull requests
  • CI
    feat(schemas): Phase 1.1 per-entity schemas + alarms / registers samples
    terastor/firmware-pipeline #1 · reviews 0 of 1 · +1040 / -481
  • CI
    chore(scaffold): bootstrap firmware-console Phase A
    terastor/firmware-console #1 · reviews 0 of 1 · +4779 / -2
  • CI
    feat(k8s): deploy firmware-console-api staging to DOKS
    terastor/firmware-console #2 · reviews 0 of 1 · +379 / -13
  • CI
    feat(mcp): add list_runs and list_releases tools
    controlvector/cv-hub #6 · reviews 0 of 1 · +857 / -1
  • CI
    feat(ci): auto-register pipelines from .cv-hub/pipeline.yml on push
    controlvector/cv-hub #7 · reviews 0 of 1 · +147 / -1

Pipeline status

last 10 runs on main
  • pendingterastor/firmware-pipelinepipeline auto-register lands in cv-hub PR #7
  • pendingterastor/firmware-consolefirst run after PR #1 + #2 merge
  • greencontrolvector/cv-hublast 10 main runs green

Safety bulletin

cv-safe linkage
0 anomaliesNo symbols lost their cv-safe.yaml reference. No deprecated alarms with active callers.

Live data lands when cv_safety_check wires up in week 1.

In-flight changes

6 active branches
  • feat/phase-1-1-per-entity-schemasterastor/firmware-pipeline+1 ahead
  • chore/scaffold-phase-a-bootstrapterastor/firmware-console+3 ahead
  • feat/deploy-manifests-phase-aterastor/firmware-console+2 ahead
  • feat/mission-control-ui-placeholderterastor/firmware-console+1 ahead
  • feat/mcp-list-runs-list-releasescontrolvector/cv-hub+1 ahead
  • feat/auto-register-pipeline-on-pushcontrolvector/cv-hub+1 ahead

Recent releases

across both repos
none yetFirst tag lands when Phase A acceptance passes; bundle storage at releases.controlvector.io.

Powered by Control Vector.