epic: deterministic sync?

[rdmolony]

Instead of relying on "asking" Claude to sync conversations with GitHub, we should derive conversations from the logs ourselves.

To do so, we need a tool that -

• Watches the log
• Determines when a goal has started and ended
• Creates a GitHub issue named after the goal
• Syncs the conversation with its appropriate issue
• Syncs the git commit with its appropriate issue

[rdmolony]

I should be able to setup a deterministic sync by creating watching the claude process from another process, and parsing the text

Watching Claude is needlessly complex, Claude saves conversations as jsonl in the home directory, it's far simpler to watch this instead.

Examples -

• https://github.com/ZeroSumQuant/claude-conversation-extractor
• https://github.com/ryoppippi/ccusage

[rdmolony]

How do I determine the start and the end of an issue if I'm tracking one long conversation session?

[rdmolony]

I now have ...

• feat: watch jsonl & log to terminal #12
• feat: export conversation to markdown file #13

... complete, so I next need to figure out how to split a long text chat by goal deterministically.

I don't want to force anyone to change their CLAUDE.md to include delimiters (that I can target for parsing) if I can avoid it