Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Proposal: opt-in Herdr status bridge and stable turn lifecycle events

未關閉
#128 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@binliu-udacity 已經在處理了。

開始於 2026年10月25日。

  • #129 來自 @binliu-udacity —— 未關閉

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
python, sqlite
領域
devtools

研究方向

The proposal describes a plugin and an unresolved lifecycle API and marketplace policy question, but names no files or tests to start from. Read the documented Hooks and identify the plugin entry points and existing lifecycle tests; clarify the supported completion and cancellation signals with maintainers before choosing an implementation. Done means maintainers have resolved the interface and review scope, and the plugin reports completion, cancellation, and permission rejection without claiming unverified success.

由索引模型根據 Issue 內容生成。

描述

Proposal

I would like to contribute zcode-herdr-status, a Standard (non-UI), developer-tools plugin that reports observational ZCode lifecycle status to an existing Herdr pane on Linux. It does not approve permissions, inject input, manage sessions, or include an Ovis patch.

An isolated internal prototype exercised a real read-only document review, permission rejection, cancellation, disconnect/reconnect and observer stop without terminating the native agent. This is limited trial evidence, not a claim of broad compatibility or unattended reliability. A portable candidate is being prepared separately with bilingual documentation, local tests and no machine-specific paths or bundled runtimes.

Public lifecycle contract question

The documented Hooks are useful, but Stop is not necessarily final completion, and the tested runtime did not always emit a terminal Hook when a user rejected a permission prompt or cancelled a request. We must not misreport those as successful completion.

The candidate therefore has two explicit modes:

  • Default Hooks-only: reports working/permission wait; Stop becomes unknown / completion unverified.
  • Optional experimental adapter: for the tested ZCode 3.16.3 runtime only, projects exact-session/current-parent lifecycle metadata from the local SQLite database in read-only mode. It does not read message text, reasoning, tool arguments/outputs or credential files. Database/schema/runtime mismatches produce unknown/refusal rather than optimistic completion.

Bindings are per inherited pane/socket and exact PID/start-time/UID lineage. Stop/release affects only the observer's source. Native ZCode parameters, model selection and permission policy remain the user's choice.

Questions for maintainers

  1. Is there a supported event or API for final turn completion, cancellation and TUI permission rejection that this plugin should use instead of internal SQLite metadata?
  2. Is an explicitly experimental, opt-in, tightly version-pinned read-only metadata adapter acceptable for marketplace review, or should the initial contribution remain Hooks-only until such an API exists?

I will link a focused draft PR for review; a draft is not a request to publish the experimental adapter before this interface question is resolved.

主要語言
Python
星號
124
分支
93
PR 合併指標
30 天內沒有已合併 PR

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

zai-org/zcode-plugins 的其他 Issue

查看 zai-org/zcode-plugins 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。