Key insight for DanOS: long-running agents should persist state as structured JSON (not markdown) between sessions. Three artifacts: progress log, git history, task list with pass/fail. Each new session starts with a startup protocol: read state, smoke test, then work. Relevant for the harness skill and any multi-session workflow.