Feature request: Add Claude Code CLI frontend adapter

[5o1]

Summary

Implement the planned Claude Code CLI frontend adapter with the same Mineprogress workflows and safety guarantees as the existing Codex frontend.

The adapter must use Claude Code-specific plugin resources, configuration, lifecycle handling, and model execution while continuing to reuse the host-independent Core.

Problem

Mineprogress currently has:

• A host-independent backend.
• A normalized host contract.
• An implemented Codex frontend.
• A planned Claude Code capability manifest.

However, Claude Code has no executable adapter, plugin resources, lifecycle integration, background worker, or frontend-specific configuration.

Proposed Feature

Plugin and Entrypoints

Add a locally loadable Claude Code plugin and implement:

• Command entrypoint.
• Lifecycle entrypoint.
• Background-update entrypoint.
• Claude Code Hooks and Skills.
• Claude Code runtime and GitHub authentication integration.

The plugin must load locally with:

claude --plugin-dir <path>

Commands

Provide Claude Code equivalents for:

• init
• create
• bind
• unbind
• check
• status
• update

Support both:

• Direct commands such as /mineprogress:init.
• Explicit natural-language requests that mention Mineprogress and a specific action.

Only current user intent may authorize mutations. Model-initiated Skills, Hooks, previous messages, and binding suggestions must not independently authorize writes.

Lifecycle Integration

Translate Claude Code events into Mineprogress's normalized lifecycle events:

• session-start
• user-prompt
• turn-stop
• session-end

Raw Claude Code Hook fields must remain inside the Claude Code frontend.

The adapter must support:

• Session restoration.
• User and assistant journal collection.
• Asynchronous planning after completed turns.
• Recovery after interrupted execution.
• Submission of pending reviewed updates when a session ends.

Configuration and State

Claude Code must use its own private plugin data directory for:

• Configuration.
• Thread bindings.
• Journals.
• Pending plans and submissions.
• Error records.

Claude Code and Codex configurations must remain independent. Users must initialize Mineprogress separately in each frontend.

No cross-frontend configuration import, binding migration, or state synchronization is required.

Model Execution

Provide Claude Code-specific create, update, and review model configuration.

Background generation and review must:

• Run through isolated Claude Code CLI calls.
• Produce schema-constrained structured output.
• Prevent nested calls from loading Mineprogress Hooks recursively.
• Use an isolated session fork when complete thread history is required.
• Preserve the existing bounded review and recovery behavior.

Claude Code model names and defaults must not affect Codex configuration.

GitHub Access

Retain the existing authentication order:

1. Active GitHub CLI login.
2. GITHUB_TOKEN or GH_TOKEN fallback.

Permission and network failures must use Claude Code-appropriate handling rather than Codex-specific sandbox-elevation behavior.

Why This Matters

Claude Code users should receive the same thread-bound GitHub Projects workflow currently available in Codex.

A complete second frontend also verifies that Mineprogress's Core remains independent of any single coding-agent host.

Acceptance Criteria

Functional Parity

• All listed commands work from Claude Code CLI.
• Direct commands and explicit natural-language requests are supported.
• Create, bind, update, review, recovery, and submission follow the same business rules as Codex.
• Complete thread history can be used for initial backfill.
• Later updates use incremental journal evidence.
• Background planning does not block foreground turns.
• Pending writes remain recoverable until GitHub changes are verified.

Isolation

• Claude Code uses its own configuration and private data directory.
• Claude Code does not read or modify Codex plugin data.
• Raw Claude Code fields and modules do not enter src/backend/.
• Nested model calls do not recursively invoke Mineprogress.

Verification

• Tests cover lifecycle normalization.
• Tests cover direct and natural-language command authorization.
• Tests cover configuration and state isolation.
• Tests cover structured model output and session forking.
• Tests cover background execution, shutdown submission, and restart recovery.
• Existing Codex tests and behavior remain unchanged.
• npm run ci passes.
• The Claude Code manifest changes from planned to implemented only after all declared capabilities are implemented and tested.

Documentation

Document:

• Local plugin loading.
• Initialization and commands.
• Claude Code-specific configuration.
• Authentication and permissions.
• Background behavior and recovery.
• Supported environment and limitations.

Additional Notes

Supported Environment

This feature targets the latest stable Claude Code CLI APIs available during implementation.

Only local Claude Code CLI usage is in scope. Older Claude Code versions, VS Code, Desktop, Web, and Cloud environments are not acceptance targets.

Excluded Scope

The following are not part of this feature:

• Marketplace packaging or publication.
• Submission to the official Anthropic marketplace.
• Cross-frontend configuration or state migration.
• Compatibility fallbacks for older Claude Code APIs.

Pull Request Boundaries

If the adapter exposes a missing host-independent Core capability, implement that capability in a separate Core or host-contract pull request first.

Core changes must remain host-neutral and pass CI independently. Do not combine Core changes with the Claude Code frontend adapter pull request.