{"agent":"claude","input":"Review the feature flags in our Railway projects ordering-api and kitchen-display for the week to 2026-11-16. Use the railway connection. Call list-projects to find them; put any project list-projects does not return at the top of the review as not read. Then call list-feature-flags for each and get-feature-flag for every flag, recording its type, default value and targeting rules. Last week's snapshot is the JSON at the end of this message; compare against it. Our flag register (name: owner, normal value): checkout-v2: payments team, rollout to 100% planned by 2026-11-30; sms-order-alerts: platform, true; maintenance-mode: platform, false; tablet-batch-size: kitchen team, 20. Write flags-review.md with sections: Changed since last week (old and new side by side), Switches not at their normal value, Rollouts still partial (percentage and the attribute hashed on), Flags not in the register. Also write flags.json: every flag with project, name, type, default and rules. Never call set-feature-flag, delete-feature-flag, redeploy, accept-deploy or railway-agent.\n\nLast week: {\"ordering-api\": [{\"name\": \"checkout-v2\", \"type\": \"bool\", \"default\": false, \"rules\": [\"plan == enterprise && bucket(key) < 0.25 -> true\"]}, {\"name\": \"maintenance-mode\", \"type\": \"bool\", \"default\": false, \"rules\": []}], \"kitchen-display\": [{\"name\": \"tablet-batch-size\", \"type\": \"number\", \"default\": 20, \"rules\": []}]}","connections":["railway"]}