Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[RET-A4][P1] Remove LOCAL CLI, configuration, prompt templates and public documentation

Open
  • Is something wrong?
#387 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
cli, documentation

Research direction

Start by reviewing the RET-A2 and RET-A3 work and the current main branch, as the issue says this work depends on RET-A2 and must coordinate with RET-A3. Then map the LOCAL command, flags, templates, docs, examples, packaging checks, and Pi smoke scenario named in the scope. Done means LOCAL is no longer advertised or executable, legacy guidance and strict config tests agree, REMOTE CLI behavior is preserved, and relevant CLI and packaging tests pass.

Written by the indexing model from the issue text.

Description

enhancement

Parent EPIC: #383 (https://github.com/iceboundrock/AutoForge/issues/383). Planning baseline: main 01c5b7e (2026-10-28); recheck current main before implementation.

Safety: Planning only at creation; no implementation, external effects, merges, or release. Preserve Controller authority, strict state/protocol parsing, independent read-back, immutable PR HEAD/base binding, reconciliation, explicit operator approval, fail-closed sandbox and credential boundary. No real GitHub mutations/models in automated tests.

Workstream: RET-A4. Dependencies: RET-A2; coordinate RET-A3.

Scope

  • Remove supported 'autoforge local init/run/doctor' command surface and LOCAL-only flags, init templates, routing, config.local feature_dir/exclude/validation_commands/max_fix_rounds and prompt templates.
  • Preserve clear legacy-state error from A2 on status/step/resume and strict config rejection; don't hide a runnable LOCAL path behind old mode state.
  • Update README, docs/configuration.md, docs/usage.md, docs/README.md, docs/development.md, SECURITY/compatibility/docs, AGENTS.md and src scoped AGENTS, examples, CLI help, packaging resource checks, operator guides.
  • Preserve ADR 0001 as historical record, mark superseded only once retired implementation ships; avoid rewriting historical architectural evidence.
  • Explicitly replace/remove Pi live smoke scenario whose fixture depends on LOCAL, preserving optionality and accurate docs.
  • Update release notes/changelog as breaking alpha change. Do not tag or publish.

Acceptance

  • No advertised or executable fresh LOCAL commands, no local prompt in distributable artifacts.
  • --help/docs/examples and strict config tests agree; legacy guidance accurate.
  • Relevant CLI/packaging tests pass; REMOTE CLI semantics unaffected.

Blocked by: RET-A2; coordinate RET-A3. Blocks: RET-A5, RET-A6.

Dominant language
Python
Stars
0
Forks
0
Avg merge
5h 32m
Merged PRs (30d)
90

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from iceboundrock/AutoForge

All issues in iceboundrock/AutoForge

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.