Reviewed 2026-10-04. Canonical issue for the incident also reported in archie-core-nam3. Read-only live checks still show runs #25 and #26 as error/manual/main, and pipeline ps for #25 returns no steps. The latest run #209 is success/push/main. Even pipeline show with output requested as JSON renders the summary table without the failure reason. No new manual pipeline was triggered, so recurrence on the current configuration is not yet proven. The old claims that authentication is unavailable or the error exists only in the database are not established; the CLI authenticates successfully today. Next: retrieve the original pre-step error through an authenticated supported diagnostic, distinguish configuration rejection from scheduling/agent failure, and reproduce against the current configuration before changing it. Do not infer that all zero-step failures share a cause.
Acceptance criteria
The original failure reason is recorded; a manual run on the current configuration either executes eligible steps or exposes an actionable pre-step error through a supported operator surface. Push remains functional.
Imported from beads archie-core-hn7u · GitHub #1098 · type bug · priority P2 · created 2026-09-22
Reviewed 2026-10-04. Canonical issue for the incident also reported in archie-core-nam3. Read-only live checks still show runs #25 and #26 as error/manual/main, and pipeline ps for #25 returns no steps. The latest run #209 is success/push/main. Even pipeline show with output requested as JSON renders the summary table without the failure reason. No new manual pipeline was triggered, so recurrence on the current configuration is not yet proven. The old claims that authentication is unavailable or the error exists only in the database are not established; the CLI authenticates successfully today. Next: retrieve the original pre-step error through an authenticated supported diagnostic, distinguish configuration rejection from scheduling/agent failure, and reproduce against the current configuration before changing it. Do not infer that all zero-step failures share a cause.
### Acceptance criteria
The original failure reason is recorded; a manual run on the current configuration either executes eligible steps or exposes an actionable pre-step error through a supported operator surface. Push remains functional.
---
_Imported from beads `archie-core-hn7u` · GitHub #1098 · type bug · priority P2 · created 2026-09-22_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Reviewed 2026-10-04. Canonical issue for the incident also reported in archie-core-nam3. Read-only live checks still show runs #25 and #26 as error/manual/main, and pipeline ps for #25 returns no steps. The latest run #209 is success/push/main. Even pipeline show with output requested as JSON renders the summary table without the failure reason. No new manual pipeline was triggered, so recurrence on the current configuration is not yet proven. The old claims that authentication is unavailable or the error exists only in the database are not established; the CLI authenticates successfully today. Next: retrieve the original pre-step error through an authenticated supported diagnostic, distinguish configuration rejection from scheduling/agent failure, and reproduce against the current configuration before changing it. Do not infer that all zero-step failures share a cause.
Acceptance criteria
The original failure reason is recorded; a manual run on the current configuration either executes eligible steps or exposes an actionable pre-step error through a supported operator surface. Push remains functional.
Imported from beads
archie-core-hn7u· GitHub #1098 · type bug · priority P2 · created 2026-09-22