shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Foundation - JSON-based IPC #119

New Issue
Closed
opened 2026-04-03 11:13:58 +02:00 by shoko · 0 comments
shoko commented 2026-04-03 11:13:58 +02:00
Owner
Copy Link

Summary

Replace fragile Python stdout parsing with structured JSON file exchange.

Depends On

  • #116 (Foundation - Modularize Shell Script)

Details

Current code uses fragile patterns like:

python3 -c "import json; print(json.load(open('$f'))['id'])" | grep something

Replace with JSON file read/write:

python3 -c "import json; json.dump({'id': '123'}, open('/tmp/session.json', 'w'))"
session_id=$(jq -r '.id' /tmp/session.json)
  • kugetsu-index.sh handles all index.json operations
  • Session files accessed via helper functions

Backport Compatible

Internal improvement only, same behavior externally.

Acceptance Criteria

  • No fragile stdout parsing remains
  • All IPC uses structured JSON files
  • Existing functionality unchanged
## Summary Replace fragile Python stdout parsing with structured JSON file exchange. ## Depends On - #116 (Foundation - Modularize Shell Script) ## Details Current code uses fragile patterns like: ```bash python3 -c "import json; print(json.load(open('$f'))['id'])" | grep something ``` Replace with JSON file read/write: ```bash python3 -c "import json; json.dump({'id': '123'}, open('/tmp/session.json', 'w'))" session_id=$(jq -r '.id' /tmp/session.json) ``` - `kugetsu-index.sh` handles all index.json operations - Session files accessed via helper functions ## Backport Compatible Internal improvement only, same behavior externally. ## Acceptance Criteria - [ ] No fragile stdout parsing remains - [ ] All IPC uses structured JSON files - [ ] Existing functionality unchanged
shoko added the backportfoundation labels 2026-04-03 11:18:17 +02:00
shoko added this to the v0.2.x milestone 2026-04-03 11:18:17 +02:00
shoko added the ready label 2026-04-07 08:55:28 +02:00
shoko closed this issue 2026-04-08 05:35:11 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label backport foundation ready
Milestone
No items
No Milestone v0.2.x
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#119
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?