From 0e77ac7831bac0308d1dbdd71c78b49600f137c3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ullrich=20Sch=C3=A4fer?= Date: Sun, 17 May 2026 20:41:03 +0200 Subject: [PATCH] Update local-dev-stack proposal: staging now exists Co-Authored-By: Claude Sonnet 4.6 --- openspec/changes/local-dev-stack/proposal.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/openspec/changes/local-dev-stack/proposal.md b/openspec/changes/local-dev-stack/proposal.md index 14a66a0..1aac619 100644 --- a/openspec/changes/local-dev-stack/proposal.md +++ b/openspec/changes/local-dev-stack/proposal.md @@ -1,12 +1,12 @@ ## Why -There is no staging environment — production is the only deployed instance. Infra -changes (Prometheus alerts, Caddy config, Grafana dashboards) go straight to prod -with no way to validate them locally first. Meanwhile, CI E2E tests skip ~15 of -20 tests because there is no PostgreSQL service in the workflow, and BRouter was -only recently added to CI with manual setup instead of reusing the dev compose -file. The existing `docker-compose.dev.yml` covers PostgreSQL and BRouter but -nothing else from the production stack. +Infra changes (Prometheus alerts, Caddy config, Grafana dashboards) can only be +validated against staging or production — there is no way to test them locally +first. Meanwhile, CI E2E tests skip ~15 of 20 tests because there is no +PostgreSQL service in the workflow, and BRouter was only recently added to CI +with manual setup instead of reusing the dev compose file. The existing +`docker-compose.dev.yml` covers PostgreSQL and BRouter but nothing else from the +production stack. ## What Changes