From 8b231bbbb52c942bfbb9fa365215394e78274804 Mon Sep 17 00:00:00 2001 From: Lucas Berger Date: Wed, 4 Feb 2026 10:25:24 -0500 Subject: [PATCH] docs(09-04): note 64-byte callback_data limitations - Long container names hit limit - Batch select limited to ~2 containers with current format - Consider short IDs or server-side state in Phase 9.1 Co-Authored-By: Claude Opus 4.5 --- .planning/STATE.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.planning/STATE.md b/.planning/STATE.md index adbe6ec..80cee34 100644 --- a/.planning/STATE.md +++ b/.planning/STATE.md @@ -86,6 +86,11 @@ Phase 11: Documentation Overhaul [ ] Pending - **Batch Update via inline keyboard** — Route Batch Loop Action "update" output is not connected. The update sequence (pull→stop→remove→create→start) is too complex to inline in the batch loop. Will be trivial once workflow is modularized into sub-workflows. +### Known Limitations (64-byte callback_data) + +- **Long container names** — Telegram's 64-byte callback_data limit causes issues with long container names in batch operations +- **Batch select limited to ~2 containers** — The `batch:toggle:{page}:{selected}:{name}` format hits the 64-byte limit quickly with multiple selections. Consider: short IDs instead of names, or storing selection state server-side in Phase 9.1 + ## Session Continuity - **Last session:** 2026-02-04