Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Temporary: execution report for the Public Alpha decision follow-through (2026-10-24)

Aperta
  • Qualcosa non va?
#303 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
1/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, python
Ambito
release

Direzione di ricerca

Read the report’s operator actions and the linked durable records: PRs #296–#300, security issues #280–#284, and roadmap #184. This issue is a temporary execution report whose work is already recorded elsewhere; it asks for closure once the PRs and operator actions are settled. Check those records for settlement, then close this issue when the stated condition is met.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Artifact: execution report for the 2026-10-23 task "Resolve Maintainer Decisions and Advance Public Alpha". The maintainer authorized the work, and an AI agent session carried it out and posted this through the maintainer's gh login. It is the English version of the report delivered in that session; there is no other working copy. This is a temporary issue: close it once the PRs and operator actions below are settled. The durable records are the decision comments, the PRs and the #184 roadmap.

Seven groups of decisions were recorded. Five code PRs and one demo-repository PR are open, all unmerged. autoforge-cli is NOT PUBLISHED. Before any public upload, the security issues #280–#284 must be fixed. They are all still open, and none has a fix PR.

A. Decisions recorded

Issue Decision Comment Result
#256 D1 MIT License; D2–D4 unchanged 6377401314 Recorded; implemented in #297
#291 items 3 and 4 doctor makes a real probe with a PASS/DENIED/UNKNOWN result; the identity read is split from the checks read 6377401591 Recorded; implemented in #298
#255 C1–C7 Conservative Public Alpha claims 6377402004 Recorded; README in #296
#261 Dedicated demo repository. No fixed spend cap: a budget is planned before the run and actual usage recorded after decision, preparation note Repository created; no real run yet
#289 item 3 An empty rollup always fails closed 6377402563 Recorded; implemented in #300
#23 / #126 A new protocol takes N + 1 from main when it merges (11 → 12 today); label 6 is skipped for good #23, #126 #126's body updated; __protocol_version__ unchanged
#136 No default switches to Pi for now 6377404809 Closed as not planned

Each comment states that the maintainer made the decision and that an AI session posted it through the maintainer's gh login.

Native relationships added:

  • #289, #291 and #295 are sub-issues of #255;
  • #295 is blocked by #256 and #280–#284;
  • #289 is blocked by #291.

B. Code changes (all unmerged, CI green)

Each PR had an independent review (Opus). Every finding was fixed, and each PR body lists them one by one.

PR Content Local tests
#296 490a409 README maturity text aligned with C1–C7: merge, UPDATE_EPIC and epic run labelled Experimental; the sandbox optional and conditional; the first registration upload explicitly not the Go. Also documents state-protocol numbering 9885 passed, 1 failed (see below)
#297 b776c2d MIT LICENSE (PEP 639); distribution renamed autoforge-cli; templates shipped in the wheel; new dist CI job (3.11/3.12: non-editable install, every template rendered, LOCAL and REMOTE dry runs); compatibility matrix and docs/releasing.md Covered by #299's make check
#299 4d6f002 (stacked on #297) pypi-publish.yml: v* tags only, OIDC only on the publish job, actions pinned by SHA, uv and setuptools pinned by hash; version 0.1.0a0 9961 passed, 0 failed
#298 50a8d39 The checks read is split out; a refused checks read has its own error type; READY_FOR_MERGE and MERGE end in a diagnosable BLOCKED; doctor gains a real probe Covered by #300's make check
#300 8cbd00b (stacked on #298) An empty rollup, and a rollup with no successful check, is BLOCKED under every configuration. GitHub's plan 403 is classified as a plan limit. With the merge gate open, doctor FAILs when the required checks cannot be verified, transient errors included 9992 passed, 0 failed
iceboundrock/autoforge-demo#3 See below —

iceboundrock/autoforge-demo#3:

  • The runbook states that the demo token can merge, and that GitHub would record such a merge under the maintainer's account.
  • It describes how to keep agents from changing the controller's own files.
  • It removes the stale prompt_version: v1.
  • The committed ruleset JSON now matches the live ruleset.

The one failure on #296: an environment problem caused by this host's TMPDIR lying under ~/.cache. It fails the same way on an unmodified main. It is tracked as #301, and the suite is fully green with a short TMPDIR.

Two follow-ups filed:

  • #301: the test problem above.
  • #302: autoforge.example.yaml hard-codes prompt_version: v1. The maintainer's local autoforge.yaml (line 27) has the same value, so runs record v1 while the v12 templates actually run.

Risks to know before merging:

  • #298 and #300 have not been exercised against a real fine-grained token or a GitHub Free plan.
  • With a fine-grained token, a human merge cannot be counted, so the run cannot reach UPDATE_EPIC. This follows from decision item 4.4, and the PR says so.
  • The publish action's Docker image is pulled by a mutable tag. This is disclosed in the docs.
  • Until the first upload, anyone can register autoforge-cli. The README tells readers to check the releases page first.

C. Release progress

  • PyPI: NOT PUBLISHED. No tag has been pushed, and the publish workflow has never run.
  • LICENSE: in #297, unmerged. GitHub's license detection only shows it after the merge.
  • Wheel/sdist: the non-editable install test passes on 3.11 and 3.12, in CI and locally.
  • Trusted Publishing:
    • The workflow is ready (#299).
    • The pypi environment exists. It was created at 2026-10-24T01:20:52Z, not by this session or either of its agents; its origin is unknown, and it had no protection when found. This session set it to required reviewer iceboundrock, deployments from v* tags only, and admin bypass off. The maintainer should confirm these settings.
    • The tag ruleset and the PyPI pending publisher are not configured yet.
  • What #295 still needs:
    1. #297 and #299 merged;
    2. #280–#284 fixed;
    3. operator actions 2–4 in section E;
    4. the tag pushed and the deployment approved.
  • #280–#284: all open, with no fix PRs.

D. Roadmap (#184 updated, roadmap section only)

  • Resolved decisions: the six ❓ rows are removed, and #136 is closed.
  • In progress: #256, #295, #291 and #289, moved to Phase 1.
  • Done: no PR merged in this round, so no issue was newly completed.
  • Work an agent can advance directly:
    • #280 (the only Critical), #284, #281, #282, #283;
    • #258, #240, #241, #301, #302, #265;
    • the Phase 2b items.

E. Operator actions

Action Why Blocks How to verify
1. Squash-merge #297 → #299 and #298 → #300 in that order; #296 can merge any time. After each merge, rebase the stacked PR onto main Merging was not authorized in this task; #297 and #299 change .github/workflows/, which requires a human merge #256, #295, #291, #289 CI green on main
2. Confirm the pypi environment's settings Origin unknown; the protection was added by this session #295 gh api repos/iceboundrock/AutoForge/environments/pypi
3. Create the v* tag ruleset (docs/releasing.md, step 2) Only the maintainer may create or move a release tag #295 gh api repos/iceboundrock/AutoForge/rulesets
4. Add the PyPI pending publisher: autoforge-cli / iceboundrock / AutoForge / pypi-publish.yml / pypi Needs the maintainer's PyPI account #295 PyPI's Publishing page
5. After #280–#284 are fixed, push v0.1.0a0 and approve the deployment Security hard gate #295 docs/releasing.md, step 10
6. Demo preparation Involves credentials and paid-call authorization #261 (which also waits on #259) The preflight in the demo runbook, section 7
7. Remove prompt_version from the local autoforge.yaml Local file Accuracy of run records The state file records v12

Action 6, demo preparation:

  • merge iceboundrock/autoforge-demo#3;
  • create a fine-grained PAT limited to the demo repository;
  • set up the model logins and provider-side spend limits, and record the planned budget;
  • choose sandbox.mode;
  • configure the git identity the agents use;
  • set the interaction limits again before the run, since they expire on 2026-10-31.

F. Next step

While the four PRs are merged in order, start the fix for #280. It is the only Critical, and it blocks both #255's Gate 5 and #295's upload:

autoforge --config autoforge.yaml --state-dir .autoforge/issue-280 run --epic https://github.com/iceboundrock/AutoForge/issues/255 --issue https://github.com/iceboundrock/AutoForge/issues/280

Remove prompt_version from autoforge.yaml first (operator action 7).

A scratch test directory and two agent worktrees (.claude/worktrees/agent-*) remain on the maintainer's machine. Nothing still uses them, so they can be cleaned up.

Lingua principale
Python
Stelle
0
Fork
0
Merge medio
5h 51m
PR unite (30g)
66

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di iceboundrock/AutoForge

Tutte le issue di iceboundrock/AutoForge

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.