The GitHub Actions job "CI" on rocketmq-dashboard.git/feat/litetopic-extend-ttl-20260926 has failed. Run started by GitHub user pilichoumao (triggered by pilichoumao).
Head commit for run: 67cfeb0fda208d874cf0f30c1e979ff52563ae4b / pilichoumao <[email protected]> feat(ai): add the rmq.litetopic.extend_ttl mutation tool The LiteTopic read tools expose pattern state, session detail and the quota watermark, but the one operation the console offers on that data — extending the TTL of a registered Lite parent topic — had no tool: an LLM or CLI operator could see a pattern approaching expiry and could not act on it. Add rmq.litetopic.extend_ttl (rmqctl litetopic extend-ttl) as an L2 mutation over the existing LiteTopicService.extendTTL, which enforces the instance ownership guard: dry-run previews the change and returns a confirm_token, apply consumes it through the standard mutation filter. The preview is derived from the request alone — no broker state is read — so the confirmed plan cannot drift between preview and apply; current state belongs to the read-only list/quota tools. Broker behavior that the caller must know is surfaced as deterministic plan warnings: one-minute TTL granularity and the 30-day cap. Guard rejections stay honest end to end: an unregistered resource or a non-LITE parent topic fails apply with the guard's 404/409 after the token check, never as a silent success. Co-Authored-By: Claude Code <[email protected]> Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38019840264 With regards, GitHub Actions via GitBox
