Issues

wave-close's two merge-order references show `algorithmic` as an array of branch strings; the verb prints an array of objects

#893

· NeoGolightly opened

on Sep 21, 2026

Usage-render residues after #856: three stale SPINE_OP_ARGS comment references, the two --id verbs disagree on their placeholder, and the alternation counter ignores a group declared inside a form

#892

· NeoGolightly opened

on Sep 21, 2026

compose-driver bare-id strip leaves the separator of a slash-joined pair — a row titled after #751/#772 shipped its PR as Residue after /:

#888

· NeoGolightly opened

on Sep 21, 2026

After #791 the Reviewer agent definition still describes the sibling list as in-flight-only, and the driver template placeholder row carries the retired sentinel

#884

· NeoGolightly opened

on Sep 21, 2026

A session's loaded plugin version is not visible at session start, and the .in_use marker cannot answer it either

#880

· NeoGolightly opened

on Sep 20, 2026

store-preflight: can a Linear API read expose a team's PR-automation state mapping, to extend the tracker-host-integration probe?

#879

· NeoGolightly opened

on Sep 20, 2026

Two residual `! cp` hand-off lines and the old file-edit-tools-declined phrasing survive in wave-setup's throwaway-consumer reference after #734

#878

· NeoGolightly opened

on Sep 20, 2026

Orphan-branch sweep can never complete under a sandboxed harness: the remote probe uses SSH and is skipped as branch-probe-failed

#876

· NeoGolightly opened

on Sep 20, 2026

issue-store annotate silently writes "undefined" as every acceptance criterion when acceptanceCriteria carries strings instead of objects

#871

· NeoGolightly opened

on Sep 20, 2026

The harness's worktree-isolation guard refuses large heredoc appends regardless of redirect target, Convention 13's Catalog names a different discriminator, and the Worker brief's shape-refusal clause does not name the file-editing tool as the working surface

#869

· NeoGolightly opened

on Sep 20, 2026

The driver template's parse gate is incidental and unnamed, and the composer writes a `--template` override that does not parse — a named gate with a negative control, and a compose-time parse refusal

#868

· NeoGolightly opened

on Sep 20, 2026

The Convention-16 clause-drift spec carries two NUL bytes in a test sentinel, so `file` classes it as data and plain `grep` prints nothing from it — every Reviewer who greps that guard hits the same wall

#867

· NeoGolightly opened

on Sep 20, 2026

Navigation Menu

All issues

wave-close's two merge-order references show `algorithmic` as an array of branch strings; the verb prints an array of objects

Usage-render residues after #856: three stale SPINE_OP_ARGS comment references, the two --id verbs disagree on their placeholder, and the alternation counter ignores a group declared inside a form

compose-driver bare-id strip leaves the separator of a slash-joined pair — a row titled after #751/#772 shipped its PR as Residue after /:

After #791 the Reviewer agent definition still describes the sibling list as in-flight-only, and the driver template placeholder row carries the retired sentinel

A session's loaded plugin version is not visible at session start, and the .in_use marker cannot answer it either

store-preflight: can a Linear API read expose a team's PR-automation state mapping, to extend the tracker-host-integration probe?

Two residual `! cp` hand-off lines and the old file-edit-tools-declined phrasing survive in wave-setup's throwaway-consumer reference after #734

Orphan-branch sweep can never complete under a sandboxed harness: the remote probe uses SSH and is skipped as branch-probe-failed

issue-store annotate silently writes "undefined" as every acceptance criterion when acceptanceCriteria carries strings instead of objects

The harness's worktree-isolation guard refuses large heredoc appends regardless of redirect target, Convention 13's Catalog names a different discriminator, and the Worker brief's shape-refusal clause does not name the file-editing tool as the working surface

The driver template's parse gate is incidental and unnamed, and the composer writes a `--template` override that does not parse — a named gate with a negative control, and a compose-time parse refusal

The Convention-16 clause-drift spec carries two NUL bytes in a test sentinel, so `file` classes it as data and plain `grep` prints nothing from it — every Reviewer who greps that guard hits the same wall

Search results