Skip to content

Reconcile dangling untracked draft plans; remove stray binary from repo root #305

Description

@mostlydev

Part of #302 (Phase 0). Repo hygiene per the issue-first workflow: planning lives in issues (or committed docs/plans/ documents linked from issues), not in untracked local files.

Untracked files needing disposition

File Proposed disposition
docs/plans/2026-04-16-intrusion-detection-master-claw-wake-draft.md Fold summary + open privilege question into an issue; delete file (blocked on auto-injected-privilege decision)
docs/plans/2026-04-16-nanoclaw-as-claude-code-runner-draft.md Fold into its issue (driver refactor + MCP pipeline tracks); delete or commit
docs/plans/2026-04-29-issue-137-picoclaw-gateway-port.md Attach to #137 (commit + link, or fold into issue body)
docs/plans/2026-04-29-salience-memory-adapter.md Commit + link from #164 — plan has a Round 2 approval; this is ready work being lost
docs/plans/2026-04-30-issue-218-cllama-infers-self-history-identity.md Attach to #218 (Phase 2 clawdapus side unlanded)
docs/plans/2026-05-09-issue-224-claw-up-fix-descriptor-refresh.md Commit + link from #224
docs/plans/2026-05-12-issue-235-claw-authored-skills-persistence.md Commit + link from #235 — plan has integrated Round 2 approval
channel-memory (repo root) Stray locally-compiled arm64 Mach-O binary; delete and add pattern to .gitignore

Acceptance

  • git status shows none of the above as untracked.
  • Every surviving plan is committed and linked from its issue; every deleted plan's substance lives in its issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions