Claude Project Tracker

The consolidated fix plan says of ESLint: "--eslintrc was removed in v9; remove the flag or pin ESLint 8." That is wrong. The platform already pins ESLint 8 in the node image. The real fault, found by the team in 77f8b9d14 (TP-5958), was binary resolution: `npx eslint` resolved the REPOSITORY's ./node_modules/.bin/eslint — version 9 — which rejects the flag the image pin still requires. Removing the flag, as the plan advised, would have broken the image's ESLint 8 behaviour. Anyone acting on the plan's original wording should stop and read 77f8b9d14 instead. Note this does NOT address fix-plan item 2.3, the missing JSX parser — no ESLint configuration file is touched in the 53 files changed between qa and dev, so React frontends still return "Unexpected token <".

Testable (Pramora) · testable-platform · by saravanan@scrumclaw.ai

The claude-collab session captured 1 decision + 4 todos on the GitHub integration, but they were stamped with project_id='outputs' because the plugin's cwd in that session was Cowork's outputs folder, not the project folder. The v3.4 ephemeral-folder guard prevents this for tracker_init_project but doesn't retroactively fix existing rows. Cleanup options: (a) DELETE FROM claude_projects WHERE project_id='outputs' CASCADE in Studio, accepting the loss of those originals (they're now duplicated under claude-project-tracker by this digest), or (b) UPDATE the 5 rows to set project_id='claude-project-tracker'.

claude-project-tracker · claude-project-tracker · by saravanan@scrumclaw.ai

All 7 Ask AI Tutor requirements are intentionally Deferred (decision D6, 2026-05-17). v3.0 scope is 13 enhancements (#9–#22 minus #20), 108 in-scope REQs. Tracking as a note so it isn't mistaken for unplanned work.

Adaptive SAT · adaptive-sat · by saravanan@scrumclaw.ai

Where to find each customer field in the qr_code.credited webhook payload. Confirmed from Razorpay official docs (docs/webhooks/qr-codes). **Payload path for VPA:** `payload.payment.entity.vpa` **Trimmed sample:** ```json { "event": "qr_code.credited", "contains": ["payment", "qr_code"], "payload": { "payment": { "entity": { "id": "pay_HO2fEpc9JeOQU5", "amount": 200, "method": "upi", "vpa": "gauri.kumar@okhdfcbank", "email": "gauri.kumari@example.com", "contact": "+919000090000", "customer_id": "cust_HKsR5se84c5LTO", "notes": {}, "acquirer_data": { "rrn": "116812981837" } } }, "qr_code": { "entity": { "id": "qr_HO2e0813YlchUn", "notes": { "charger_id": "VAJRA0001", "connector_id": "2" } } } } } ``` **Two subtle gotchas:** 1. **Two separate `notes` blocks** — `payload.payment.entity.notes` is per-payment (usually empty for QR), and `payload.qr_code.entity.notes` is the QR's notes (where we set charger_id + connector_id at QR creation). Read the second one for gun identification. 2. **VPA presence:** always present for QR-triggered payments (method is always upi). Fallback: null. **Go struct extraction:** see TDD §4.3 `qrCreditedPayload`. **Fallback retrieval (webhook lost):** - `GET /v1/payments/pay_XXX` — fetch single payment; includes vpa - `GET /v1/payments/qr_codes/qr_XXX/payments` — list all payments for a QR (great for admin ops "show all payments to this gun") Sources: - https://razorpay.com/docs/webhooks/qr-codes/ - https://razorpay.com/docs/webhooks/payloads/payments/</body>

Vajra Volt Mobile App · vajra-mobile-app · by saravanan@scrumclaw.ai