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
星标
137
派生
112
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 摘要。