What's pending across every project
4 open · sorted by priority then due-date
Filtered by tag process clear
note
Git flow: use ~/Documents/GitHub/cointrends/ship.sh — one short-lived branch per change, merged, deleted and pruned in one run
Cloud sessions started from the Cowork folder have no GitHub repo access, so Claude edits the local checkout and Saravanan runs ship.sh (branch → commit → push → PR → squash-merge → delete branch → ff base → git fetch --prune). No orphaned branches.
CoinTrends.ai
· cointrends
· by saravanan@scrumclaw.ai
from the conversationsaravanan: i dont want lot of branches created and orphaned
saravanan: Add that [git fetch --prune] as part of your script
claude: ship.sh now does the full flow and prunes stale refs on success or failure.
10d ago
10-16 19:10
10-16 19:10
decision
No changes to running systems until a final, step-by-step cleanup phase with validation and rollback
Saravanan 2026-10-19: do not stop or change anything that is running (schedulers, Cloud Run services, DB rows such as slices 1-23, live models). Findings and fixes are collected now; all production changes happen together at the end as an ordered cleanup plan where every step has a validation check and a rollback.
CoinTrends.ai
· cointrends
· by saravanan@scrumclaw.ai
from the conversationsaravanan: Keep all the changes to later stage - i do not want to stop anything that is running. we need a clean up step by step with proper validation and rollback at the end of all our work
claude: Recorded; production stays untouched until the final cleanup phase.
💬 1 comment
7d ago
10-19 14:19
10-19 14:19
decision
Staging stays retired — production-only, with local tests, pre-release backup, live validation and a ready rollback
Only production runs in the cloud. Leftovers: 3 idle staging Cloud Run services in prj-crypto538-stage-443113 (no triggers deploy to them), stage.cointrends.ai LB commented out in terraform, CryptoTrack_Stage / CryptoUserBilling_Stage DBs on the prod instance. Merging to the `stage` branch deploys nothing; `master` deploys prod. Leftovers can be reviewed in the final cleanup.
CoinTrends.ai
· cointrends
· by saravanan@scrumclaw.ai
from the conversationsaravanan: we stopped staging environmnt - its only production is enabled in cloud
claude: Confirmed; offered to log a cheap staging revival.
saravanan: leave staging retired
💬 1 comment
7d ago
10-20 01:45
10-20 01:45
note
Process: update the tracker and the MD docs on every push, not at session end
Saravanan's instruction, 2026-10-24: post a tracker update as soon as something is pushed, and fold the markdown doc updates into the same change rather than leaving them behind.
This mirrors the existing repo rule in docs (every feature commit folds in status-doc updates) — it had been slipping. Three PRs (#128, #132, #133) went out before the BRD23 status table and the BRD_V3_TRACKER annotations caught up, which meant the docs understated what was actually built.
Concretely, for each push: (1) ship.sh, (2) tracker_post_update with the PR and git_sha, (3) BRD/tracker markdown reflecting the new state in the same PR where possible.
Adaptive SAT
· adaptive-sat
· by saravanan@scrumclaw.ai
3d ago
10-24 03:19
10-24 03:19