after moving all to cipher

worker-toolkit-stocks-in-the-future/task-shared/test-commands.toml

@@ -127,7 +127,7 @@ baseline_known_failures = [
 
 # confidence: validated
 [flaredown]
-notes = "Rails 7.1 API (Ruby 3.2.3), Mongoid 8.1 on MongoDB 7.0 + Postgres + Redis + Sidekiq. The app lives in backend/ (not the repo root), so the check cd's into it. The harbor Dockerfile's start-services.sh starts all three datastores, creates flaredown_development/flaredown_test, and loads the Postgres schema for both envs; backend/.env is materialized from env-example with PG host rewritten to localhost. Mongoid creates collections lazily (no schema to load). Browser/acceptance specs are excluded — Ember `ember test` needs a browser on PATH (phantomjs up to pin 5f859e8d, headless Chrome via CHROME_BIN from b0605ff3; neither is installed) and is bad grader signal anyway; the rspec verifier touches neither the client nor a running server. [Runtime-validated 2026-08-04 in the harbor image built from Dockerfile.flaredown @ pin b0605ff3]: 315 examples, 0 failures (~7s, 96.08% coverage) — clean, so no baseline is declared. Unchanged from the earlier validation at pin 5f859e8d (2026-07-20, same 315/0/96%); the only backend change across that pin advance is backend/lib/tasks/app.rake."
+notes = "Rails 7.1 API (Ruby 3.2.3), Mongoid 8.1 on MongoDB 7.0 + Postgres + Redis + Sidekiq. The app lives in backend/ (not the repo root), so the check cd's into it. The harbor Dockerfile's start-services.sh starts all three datastores, creates flaredown_development/flaredown_test, and loads the Postgres schema for both envs; backend/.env is materialized from env-example with PG host rewritten to localhost. Mongoid creates collections lazily (no schema to load). Browser/acceptance specs are excluded — Ember `ember test` needs a browser on PATH (phantomjs up to pin 5f859e8d, headless Chrome via CHROME_BIN from b0605ff3, which the Explore image now provides though the verifier image does not) and is bad grader signal anyway; the rspec verifier touches neither the client nor a running server. [Runtime-validated 2026-08-04 in the harbor image built from Dockerfile.flaredown @ pin b0605ff3]: 315 examples, 0 failures (~7s, 96.08% coverage) — clean, so no baseline is declared. Unchanged from the earlier validation at pin 5f859e8d (2026-07-20, same 315/0/96%); the only backend change across that pin advance is backend/lib/tasks/app.rake."
 
 [[flaredown.checks]]
 name = "rspec"
@@ -135,9 +135,24 @@ cmd = "cd backend && RAILS_ENV=test bundle exec rspec --exclude-pattern 'spec/sy
 
 # confidence: none
 [alongwithyou]
-notes = "Rails 8.1 / Ruby 4.0.5, Minitest + SQLite (file-backed, no DB service). This is a fresh scaffold being built with the Dewberry Cancer Center — at the current pin (a017fd43, a single 'First' commit; upstream main has not advanced past it as of 2026-07-20) it ships 0 test files (no *_test.rb), only the ApplicationRecord base class (no domain models), no migrations, no db/schema.rb, and a default routes.rb (just the /up health check), so `bin/rails test` collects 0 examples and there is no deterministic correctness signal to gate on. Grader scores correctness from the code + transcript directly, which is correct for an empty scaffold. When real Minitest coverage lands upstream and the pin is bumped, add a `minitest` check like endsideout's (`RAILS_ENV=test bin/rails db:test:prepare && RAILS_ENV=test bin/rails test`)."
+notes = "Rails 8.1 / Ruby 4.0.5, Minitest + SQLite (file-backed, no DB service). This is a fresh scaffold being built with the Dewberry Cancer Center — at the current pin (a017fd43, a single 'First' commit; upstream main has not advanced past it as of 2026-07-20) it ships 0 test files (no *_test.rb), only the ApplicationRecord base class (no domain models), no migrations, no db/schema.rb, and a default routes.rb (just the /up health check), so `bin/rails test` collects 0 examples and there is no deterministic correctness signal to gate on. When real Minitest coverage lands upstream and the pin is bumped, add a `minitest` check like endsideout's (`RAILS_ENV=test bin/rails db:test:prepare && RAILS_ENV=test bin/rails test`)."
 # no static verifier for this repo — no deterministic signals (0 tests / stubs / placeholder / live-external).
 
+# confidence: validated
+[breezy-complete]
+
+[[breezy-complete.checks]]
+name = "rspec (backend)"
+cmd = "cd backend && env -u DISABLE_CLERK -u CLERK_SKIP_RAILTIE RAILS_ENV=test CI=true bundle exec rspec"
+
+[[breezy-complete.checks]]
+name = "rubocop (backend)"
+cmd = "cd backend && env -u DISABLE_CLERK -u CLERK_SKIP_RAILTIE RAILS_ENV=test CI=true bundle exec rubocop app spec db config"
+
+[[breezy-complete.checks]]
+name = "eslint (frontend)"
+cmd = "cd frontend && npm run lint:ci"
+
 # confidence: validated
 [zeta-heimdall]
 notes = "Rails 7 API-only (Ruby 3.2.1), Postgres-only, no Node → RSpec is the only suite"
@@ -198,7 +213,7 @@ notes = "Rails + Postgres backend (ruby:3.2.2)"
 
 # confidence: none
 [zeta-wasabi-platform]
-notes = "Rails 3.2.2/postgres+redis app, RSpec suite (grader guidance runs `bundle exec rspec` on spec/models,graphql,services"
+notes = "Rails app on Ruby 3.2.2 + Postgres/Redis; 980 spec files (services 391, graphql 287, models 159, jobs 104, mailers 19, others 20). Dropped to no-verifier at the 2026-07 runtime validation — the full suite ran 7048 examples with 761 pre-existing failures, too noisy to park as a declared baseline. Scoping to services+graphql+models would still keep 837 of the 980 files, so it only pays off if those failures concentrate in jobs/controllers/mailers; unverified as of 2026-08-10."
 
 # confidence: none
 [zeta-jc-loadtester]
@@ -283,6 +298,11 @@ notes = "Python 3.10.12 ML repo (transaction-anomaly notebooks + SQL)"
 [zeta-dbt]
 notes = "Python 3.10.12 dbt project targeting external Snowflake"
 
+# confidence: none
+[zeta-ops]
+notes = "Ops scripts repo — the whole checkout at pin 23fd7127 is a README, a certs/netlify/ directory holding one .crt, and a single 44-line update_ssl_cert.rb that opens TLS sockets against live *.askzeta.com hosts to check certificate expiry. No test framework, no dependency manifest, and nothing runnable offline, so there is no deterministic correctness signal. Added for parity with the other zeta members (an absent entry and a checkless one behave identically — renderTestCommandsSh returns null either way — but a recorded entry says the repo was assessed rather than overlooked)."
+# no static verifier for this repo — no deterministic signals (0 tests / stubs / placeholder / live-external).
+
 # ---- speedwell-polyglot (StrongSuit / Speedwell) gradable Node members ----
 
 # confidence: validated