v1.3.0 — journals

Published to npm as @armoryworks/md-agent@1.3.0.

New — journals

A run's journal — state.json, ledger.md, transcript.md, context.md, the seat traces in log/, spend files, and a generated JOURNAL.md cover page — can be kept in source control and pulled back on any machine. Never the project repo: journals hold transcripts and traces, so they go to a private repository per project (forge-md-agent, nom-md-agent) or one shared fallback, configured in ~/.config/md-agent/config.json.

• At the end of every run — clean, interrupted (ctrl-c), or halted — md-agent asks whether to push. A project with no repo yet is offered <owner>/<project>-md-agent, created private via gh; the shared repo; or a URL. Every prompt carries "No, and don't ask again — ever" (remembered; pushing stays available from the home screen). "Yes, and always push" turns on auto-push.
• Before every push: the remote's visibility is checked — a public repo is refused, an internal or unverifiable one needs an explicit yes — and the journal is scanned for credential shapes (API keys, tokens, private-key blocks).
• Home screen → ⇅ Journals: push runs not yet pushed, pull journals into ./runs (Continue, Look inside a seat and Combine all work on them), change the project's repo, set the run-end prompt to ask / auto / never.
• MD_AGENT_HOME relocates the config and clones.