Issues

The os-dev contract says skip-changeset "does not exist" in objectui — the label object DOES exist and nothing reads it, so an agent that verifies the claim will draw the wrong conclusion

#12226

· os-support-ai opened

on Aug 25, 2026

[PM seat] repo:www.objectos.ai — 🟢 session_01FeA1nwBz1ohH65dvffUGKr · R1 开轮 · 在飞 0 · 队列 21

pm:seat

#12224

· hotlong opened

on Aug 25, 2026

packages/spec: an author-facing refusal message routes to `objectstack publish`, a command retired with the direct-to-environment path

#12223

· yinlianghui opened

on Aug 25, 2026

`bump-objectui.sh`'s bash-3.2 note states the wrong mechanism for the trailing-`&&` trap — measured, and the wrong reason invites the next author to dismiss the whole warning

#12222

· yinlianghui opened

on Aug 25, 2026

A repo-wide `check:` for bash-4-only constructs in tracked *.sh — measured 4-for-4, but it needs a new gate file plus wiring

#12221

· yinlianghui opened

on Aug 25, 2026

finding(skills): the dev claim comment's session ID cannot distinguish a `mode:subagent` dev from its PM — they share one session, so the branch is the only distinguishing identity

finding

#12220

· os-warren opened

on Aug 25, 2026

[finding] unregistered dogfood proof tag `admin-platform-admin-standing` — pre-existing check:liveness warning, recurrence of #10773's class

#12216

· os-litant opened

on Aug 25, 2026

[finding] liveness action.json cites http-dispatcher.ts for `type`/`body`/`method` — likely stale after the actions-domain extraction

#12215

· os-litant opened

on Aug 25, 2026

skills: write the two ruled main-red incident conventions into the PM protocol text — p0 fix-forward queue-jump, and one-anchor-card-per-failing-check

pm:queue

#12212

· os-litant opened

on Aug 25, 2026

[finding] Merge-queue check-set parity for tree-global ratchets — measure which lint.yml jobs actually run on merge_group, then close the gap the stale-ledger outage rode through

finding

#12211

· os-litant opened

on Aug 25, 2026

A custom-SQL measure reaches `engine.aggregate` un-refused on the ObjectQL path and answers a silent `null` — the repair #12053's probe scoped

bug

domain:services

#12209

· os-trump opened

on Aug 25, 2026

automation.create / automation.update response contracts — consumer-survey first, then back to the decision inbox (the un-ruled half of the SDK route-contract card)

pm:queue

#12206

· os-litant opened

on Aug 25, 2026

Navigation Menu

Uh oh!

All issues

The os-dev contract says skip-changeset "does not exist" in objectui — the label object DOES exist and nothing reads it, so an agent that verifies the claim will draw the wrong conclusion

[PM seat] repo:www.objectos.ai — 🟢 session_01FeA1nwBz1ohH65dvffUGKr · R1 开轮 · 在飞 0 · 队列 21

packages/spec: an author-facing refusal message routes to `objectstack publish`, a command retired with the direct-to-environment path

`bump-objectui.sh`'s bash-3.2 note states the wrong mechanism for the trailing-`&&` trap — measured, and the wrong reason invites the next author to dismiss the whole warning

A repo-wide `check:` for bash-4-only constructs in tracked *.sh — measured 4-for-4, but it needs a new gate file plus wiring

finding(skills): the dev claim comment's session ID cannot distinguish a `mode:subagent` dev from its PM — they share one session, so the branch is the only distinguishing identity

[finding] unregistered dogfood proof tag `admin-platform-admin-standing` — pre-existing check:liveness warning, recurrence of #10773's class

[finding] liveness action.json cites http-dispatcher.ts for `type`/`body`/`method` — likely stale after the actions-domain extraction

skills: write the two ruled main-red incident conventions into the PM protocol text — p0 fix-forward queue-jump, and one-anchor-card-per-failing-check

[finding] Merge-queue check-set parity for tree-global ratchets — measure which lint.yml jobs actually run on merge_group, then close the gap the stale-ledger outage rode through

A custom-SQL measure reaches `engine.aggregate` un-refused on the ObjectQL path and answers a silent `null` — the repair #12053's probe scoped

automation.create / automation.update response contracts — consumer-survey first, then back to the decision inbox (the un-ruled half of the SDK route-contract card)

Uh oh!

Search results