Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Adopt the provider-neutral interaction contract for Pi (#134 part 2)

オープン
  • 何か問題がありますか？
#252 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
python
領域
ai-infra-agents, backend

調査の方向性

Start with src/autoforge/interaction.py and the Pi path, then read #126's state, pause, command, and recovery design plus ADR 0007 D6.1 and ADR 0003 §2.9. Work depends on #126, #132, and #134 Part 1, and requires resolving dialog recovery and timeout behavior and specifying rules for each crash window. Done means the acceptance criteria have tests, including durable pause and exactly-once resume, while the existing no-interaction Pi path and Claude path remain unchanged.

索引モデルが issue の本文から書いたものです。

説明

Why this issue exists

Review round 1 of the pull request for #134 found that it implements only Part 1 of #134: the provider-neutral interaction contract and broker (src/autoforge/interaction.py), the prompt and fail policies with their limits, the terminal resolver and the two type extensions. Part 2, Pi's adoption of that contract, is post-MVP and depends on #126 (ADR 0007 D6.1; ADR 0003 §2.9).

AutoForge ends every implementation pull request body with its own closing line for the run's issue. The controller writes that line, not the implementing agent: it binds the pull request to its issue through it (closingIssuesReferences) and reads the body back exactly as composed. The agent fixing review findings holds no GitHub credential and cannot edit the description, and removing the line would break that binding. So #134 is closed when the Part 1 pull request merges.

This issue carries Part 2 from then on, so the work stays tracked. ADR 0007 requires that #126 and #134 are never closed or superseded silently: this issue is the explicit hand-over. If the maintainers prefer to keep #134 itself as the tracker, reopen it after the merge and close this issue as a duplicate.

Scope: Part 2 of #134, unchanged

  • Implement the Pi mapping on top of the shared contract and #126's durable layer:
    • a client-chosen session id, persisted before launch;
    • launch with --session-dir <AutoForge-owned dir> --session-id <id>, never --session, --continue, --resume or "latest".
  • The session directory lives in the run's state directory with mode 0700, never inside the LOCAL working tree. It stays untracked and is never logged in full. AutoForge never deletes provider sessions.
  • Map an extension_ui_request dialog (select, confirm, input, editor) to an InteractionRequest, and a decision to an extension_ui_response.
    • Decide whether a dialog can be re-identified after a restart.
    • Decide whether Pi's own dialog timeout is acceptable or must be rejected.
  • Decide the interaction source: either a reviewed AutoForge-owned "ask the operator" extension, loaded explicitly (this needs #132's approval), or Pi pause/resume stays unsupported (interaction_policy: fail only).
  • Add interaction_policy to Pi's strict option keys (#129's mechanism).
  • Walk #126's crash windows for Pi, with a rule and a test for each.
  • Continuations do not increment attempt. LOCAL continuations are charged like corrections. The per-invocation interaction bound applies.

Acceptance criteria

These are the "If implemented" criteria of #134:

  • a Pi invocation that raises a dialog under pause ends in a durable, inspectable state, with the phase and attempt unchanged;
  • decision commands record only, and resume delivers exactly once or fails safely;
  • every crash window from #126 has a Pi rule and a test;
  • state written with a Pi session loads under #126's state bump, and an older state file loads as empty;
  • Pi never chooses a session id, and there is no "latest session" lookup;
  • the session directory is untracked and never logged in full;
  • Claude and the MVP Pi path (--no-session) are unchanged when no interaction source is configured.

Dependencies

  • #126 (hard): the state bump, the pending-interaction record, pause, the operator commands and recovery.
  • #132 (hard): any Pi interaction source must fit the resource policy.
  • #134 Part 1: the contract and broker, delivered by the pull request this issue was deferred from.

Non-goals

As in #134:

  • no OpenCode server work;
  • no in-session corrections;
  • no steer / follow_up mid-run instructions;
  • no full transcripts in AutoForge state;
  • no deletion of Pi sessions.

Deferred from finding R1-F2 of https://github.com/iceboundrock/AutoForge/pull/251.

主要言語
Python
スター
0
フォーク
0
平均マージ
5時間 51分
マージ済み PR（30日）
66

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

iceboundrock/AutoForge のほかの issue

iceboundrock/AutoForge の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。