Issues

flow designer: the Start node's Entry condition is raw-CEL-only — ConditionBuilder ships in five other inspectors but not the one condition most users meet

#11940

· yinlianghui opened

on Aug 25, 2026

flaky: the ABLATION leg of `vitest-console-teardown-race.test.ts` reds a full-repo run — its instrument stops reproducing under load (1 red in 6 runs)

#11939

· os-steve opened

on Aug 25, 2026

`pnpm test` is OOM-killed at turbo's default concurrency on a 4-CPU/15 GB container — exit 137, 16 of 91 tasks never run

#11938

· os-steve opened

on Aug 25, 2026

pm-dispatch: the PM re-derives a card's numbers but not its scope — 4 measured instances in one round, one of which ordered work that had already landed

#11936

· yinlianghui-tw opened

on Aug 25, 2026

[finding] `check:ratchet-remedy-authority` sweeps `scripts/**` but declares no path, so no card that edits a gate script can derive it — the one population it exists to police

finding

#11935

· os-zhuang opened

on Aug 25, 2026

A compound-name draft has no REST promotion door — `POST /meta/:type/:name/publish` is mounted in one arity while its read twin `/published` is mounted in both

#11932

· os-zhuang opened

on Aug 25, 2026

14 internal issue-id references survive in generated `skills/**` artifacts — their source is `packages/spec` TSDoc, so the ruled strip could not reach them

#11930

· os-zhuang opened

on Aug 25, 2026

[finding] `packages/client` has no `check:exported-any` equivalent — #8140 fixed 51 sites and nothing stops the 52nd

finding

#11927

· os-zhuang opened

on Aug 25, 2026

`client.reports.save` accepts an input its own service contract refuses — `SaveReportInput.query` is required and neither the SDK nor the route checks it

#11926

· os-zhuang opened

on Aug 25, 2026

A fifth client-SDK erasure spelling no grep in #8140's census counted: 38 methods with NO return annotation, typed from `unwrapResponse< …any… >`

#11925

· os-zhuang opened

on Aug 25, 2026

Four client SDK routes answer a shape no published contract declares — `automation.create` / `automation.update` / `search` / `data.clone`

#11924

· os-zhuang opened

on Aug 25, 2026

finding(skills): the os-dev report contract's final-message wording conflicts with the sanitizer-safe marker-line practice dispatch briefs now require

finding

#11923

· os-warren opened

on Aug 25, 2026

Navigation Menu

Uh oh!

All issues

flow designer: the Start node's Entry condition is raw-CEL-only — ConditionBuilder ships in five other inspectors but not the one condition most users meet

flaky: the ABLATION leg of `vitest-console-teardown-race.test.ts` reds a full-repo run — its instrument stops reproducing under load (1 red in 6 runs)

`pnpm test` is OOM-killed at turbo's default concurrency on a 4-CPU/15 GB container — exit 137, 16 of 91 tasks never run

pm-dispatch: the PM re-derives a card's numbers but not its scope — 4 measured instances in one round, one of which ordered work that had already landed

[finding] `check:ratchet-remedy-authority` sweeps `scripts/**` but declares no path, so no card that edits a gate script can derive it — the one population it exists to police

A compound-name draft has no REST promotion door — `POST /meta/:type/:name/publish` is mounted in one arity while its read twin `/published` is mounted in both

14 internal issue-id references survive in generated `skills/**` artifacts — their source is `packages/spec` TSDoc, so the ruled strip could not reach them

[finding] `packages/client` has no `check:exported-any` equivalent — #8140 fixed 51 sites and nothing stops the 52nd

`client.reports.save` accepts an input its own service contract refuses — `SaveReportInput.query` is required and neither the SDK nor the route checks it

A fifth client-SDK erasure spelling no grep in #8140's census counted: 38 methods with NO return annotation, typed from `unwrapResponse< …any… >`

Four client SDK routes answer a shape no published contract declares — `automation.create` / `automation.update` / `search` / `data.clone`

finding(skills): the os-dev report contract's final-message wording conflicts with the sanitizer-safe marker-line practice dispatch briefs now require

Uh oh!

Search results