hypaware-query skill dropped remote cost and liveness guidance (graph-first on remote, no client-side timeout, tailnet hint)

Aperta
  • Qualcosa non va?
#2,528 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
markdown
Ambito
documentation

Direzione di ricerca

Read the Remote queries and Activity graph sections in hypaware-core/plugins-workspace/{claude,codex}/skills/hypaware-query/SKILL.md, then compare the two client copies and the linked reference guidance. The first step is a maintainer decision about whether to retain the cost, timeout, and private-network guidance. Done means recording that decision; if the guidance is restored, both copies must match and skill-host-parity must pass.

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

Descrizione

Source: #2521 at bae529098609ea41e9dc0371f32733be91ca8616
Location: hypaware-core/plugins-workspace/{claude,codex}/skills/hypaware-query/SKILL.md, 'Remote queries' and 'Activity graph' sections
Severity: minor

Evidence

git diff origin/master...bae52909 on the claude copy removes: 'On a remote target, reach for the graph first, not last. node aggregates return in ~0.3s while ai_gateway_messages aggregates over the same recordings take 16-34s'; 'a call that simply hangs (the remote path sets no client-side timeout)'; and the tailnet hint 'A target may be reachable only over a private network (a tailnet / 100.x address), so a timeout often means you are off that network'. The head keeps a compact form of the liveness point ('If a connection fails, retry once, then report the error. hyp remote list does not verify connectivity.', SKILL.md:60) but none of the cost or timeout facts. No LLP states these numbers or the timeout fact (grep of llp/ for tailnet, 0.3s, 16-34, client-side timeout finds nothing), and none is in test/fixtures/skill-constraints.json.

Why deferral is safe

This is deliberate product trimming within the PR's stated goal (a shorter skill with conditional detail in references). Nothing it removed is a documented contract: the retained text still tells the agent to retry once and report, and remote result limits are still named. The dropped lines would make a remote agent faster or more diagnostic, which is guidance quality, not correctness.

Acceptance condition

A maintainer decides whether the remote cost comparison, the no-client-timeout fact, and the private-network hint belong in SKILL.md or in a linked reference such as troubleshooting.md. If restored, both client copies carry identical wording and skill-host-parity passes; if not, close this issue with that decision.

Review preference; backlog only. A human may explicitly delegate it with neutral:fix.

Lingua principale
JavaScript
Stelle
11
Fork
0
Merge medio
2h 25m
PR unite (30g)
311

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 hyparam/hypaware

Tutte le issue di hyparam/hypaware

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.