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

Abierto
  • ¿Algo no está bien?
#128 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@binliu-udacity ya está trabajando en esto.

Desde el 25/10/2026.

  • #129 de @binliu-udacity — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python, sqlite
Área
devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
137
Forks
112
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de zai-org/zcode-plugins

Todos los issues de zai-org/zcode-plugins

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.