Skip to content

Commit bb249ff

Browse files
committed
update
1 parent f00a601 commit bb249ff

File tree

3 files changed

+4
-6
lines changed

3 files changed

+4
-6
lines changed

.sudocode/issues.jsonl

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1 @@
1-
{"id":"i-7vga","uuid":"b06340a4-815e-4d8c-98cd-714af069aae9","title":"Hello World","content":"Create a simple placeholder task for future testing and onboarding workflows.","status":"open","priority":2,"assignee":null,"archived":0,"archived_at":null,"created_at":"2025-11-06 19:12:15","updated_at":"2025-11-06 19:12:15","closed_at":null,"parent_id":null,"parent_uuid":null,"relationships":[],"tags":[]}
2-
{"id":"i-3ugl","uuid":"eab0a6ef-903a-4fbd-b65a-9a494cc9ba64","title":"Decide on block cache key normalization strategy","content":"Investigate whether rendered block-level cache keys need hashing or truncation before persistence. Capture current storage limits (DB columns, external caches) and propose an approach if keys can exceed safe lengths.\n\nLinked spec: [[s-j4ju]]","status":"open","priority":2,"assignee":null,"archived":0,"archived_at":null,"created_at":"2025-11-06 19:33:19","updated_at":"2025-11-06 19:33:19","closed_at":null,"parent_id":null,"parent_uuid":null,"relationships":[],"tags":[]}
3-
{"id":"i-6j1x","uuid":"0251c19e-94b7-4ec3-b0c9-573920f14819","title":"Clarify tooling for block-level cache key variants","content":"Determine whether we need admin or UI tooling to list/manage per-block cache key variants now that templates exist. Scope could include API surface and frontend hooks.\n\nLinked spec: [[s-j4ju]]","status":"open","priority":3,"assignee":null,"archived":0,"archived_at":null,"created_at":"2025-11-06 19:33:22","updated_at":"2025-11-06 19:33:22","closed_at":null,"parent_id":null,"parent_uuid":null,"relationships":[],"tags":[]}
4-
{"id":"i-6deh","uuid":"1fba7d49-8b13-4710-84b1-03f9da95ec3e","title":"Evaluate security of exposing prior block outputs to cache templates","content":"Assess whether allowing cache key templates to reference previous block outputs introduces data governance or secret-leak risks. Document mitigations or restrictions if necessary before rollout.\n\nLinked spec: [[s-j4ju]]","status":"open","priority":1,"assignee":null,"archived":0,"archived_at":null,"created_at":"2025-11-06 19:33:28","updated_at":"2025-11-06 19:33:28","closed_at":null,"parent_id":null,"parent_uuid":null,"relationships":[],"tags":[]}
1+

0 commit comments

Comments
 (0)