Issues

plugin-approvals: the hand-built contexts its writes run under don't fully carry the deciding user's context, so a runAs:'user' hook they fire gets neither the user's organisation peers nor the user's own grants (the producer half of #24497)

objectstack-ai/objectstack#24519 · opened

on Oct 19, 2026

pm-dispatch lanes/hotcrm.md:8 and :33 still forbid the repo:hotcrm seat to grade and point at a dead "SKILL.md 多仓协调规则 4": align them with the single-lane rule, as ruled on hotcrm#2178 (A)

objectstack-ai/objectstack#24517 · opened

on Oct 19, 2026

1

A conditional validation rule's `when` that reads through a lookup (`record.account.status`) saves at every door, but `checkConditional` evaluates it unhydrated, so every write the rule guards is refused as unevaluable

objectstack-ai/objectstack#24512 · opened

on Oct 19, 2026

1

fix(release): the console injection assertion has a real witness on a .objectstack-sha pin, instead of passing vacuously

objectstack-ai/objectstack#24510 · opened

on Oct 19, 2026

1

plugin-approvals: the request and action list views show an Object column with the target object's API name (`object_name`, such as `showcase_announcement`), the type half of the record pointer pair, drawn as plain text

objectstack-ai/objectstack#24501 · opened

on Oct 19, 2026

4

objectql: a runAs:'user' hook fired from a hand-built system context (plugin-approvals' writes) runs without org_user_ids, so sys_user's org-members scope drops out and the hook sees only the acting user's own row

objectstack-ai/objectstack#24497 · opened

on Oct 19, 2026

4

chore(cli)!: 18.x restore of the 18.0 guards — re-open the upgrade ceremony and walled boots

objectstack-ai/objectstack#24489 · opened

on Oct 19, 2026

plugin-security: the shipped permission sets stop copying the identity objects' row-scope literals once those objects declare them as their default row scope (#24340 follow-up, ruling E′ item 3)

objectstack-ai/objectstack#24484 · opened

on Oct 19, 2026

1

nightly-tiers: red on main

objectstack-ai/objectstack#24473 · opened

on Oct 19, 2026

1

objectql: a foreign bound action named like an action the target object already declares is not attached and nothing reports it, while the two packages' handlers overwrite each other silently — the collision follow-up of #24400 (PR #24458)

objectstack-ai/objectstack#24472 · opened

on Oct 19, 2026

4

docs(qa): re-author access-security.platform-owner-email-anchor for the Default Organization grant — PR #24373 landed #11979, the trigger the item names for its own re-author

objectstack-ai/objectstack#24465 · opened

on Oct 19, 2026

1

Registry canary failed: fresh npx create-objectstack install is broken

objectstack-ai/objectstack#24462 · opened

on Oct 19, 2026

1

upgrade-impact comparison after v18: report the non-access classes to the administrator, and retire the zero-consumer package-upgrade.zod.ts

objectstack-ai/objectstack#24447 · opened

on Oct 19, 2026

upgrade-impact comparison, access class (v18): a vendor upgrade that would orphan, re-enable or collide with a customer's access choice is refused until an administrator confirms, and raised at boot

objectstack-ai/objectstack#24446 · opened

on Oct 19, 2026

3

pm-dispatch(decision-analysis): a decision analysis recommends exactly one option — retire the 「回退项」 line (the maintainer's word, 2026-10-19)

objectstack-ai/objectstack#24444 · opened

on Oct 19, 2026

plugin-sharing: refuse a new or renamed sys_sharing_rule row that takes a declared rule's name, and reconcile the shadowed declaration's grants on a same-name write (ruling B′ on #24378)

objectstack-ai/objectstack#24421 · opened

on Oct 19, 2026

7

tooling(board-snapshot): the scheduled Board Snapshot failed its count check twice running (exit 2 at 08:25Z and 14:18Z on 2026-10-18): the archive and the live board disagree on the open-issue count

objectstack-ai/objectstack#24351 · opened

on Oct 18, 2026

3

ADR-0131 D9 on a walled control plane: three framework writers land NULL organization_id rows on every sign-up (the self-registration grant, the verification mail, activity about org-less records)

objectstack-ai/objectstack#24343 · opened

on Oct 18, 2026

15

platform-objects: the identity objects declare their default row scope (the literals the shipped sets copy today), and the registry refuses an `extend` contributor that loosens a platform object's default (#24164 ruling E′)

objectstack-ai/objectstack#24341 · opened

on Oct 18, 2026

13

metadata-core: `MetadataEventSchema.source`'s describe and the `sys_metadata_history.source` docs name labels ("studio", "rest", "ai", "git-import") that no producer writes — the family's collector after #24328

objectstack-ai/objectstack#24336 · opened

on Oct 18, 2026

A resumed flow run writes as its trigger user (the submitter), not the approver who resumed it, so post-decision writes in an approval flow name the submitter as Last Modified By and in the audit log

objectstack-ai/objectstack#24321 · opened

on Oct 18, 2026

6

platform-objects sys_organization: change_slug targets a cloud-only route, so on an open-source multi-organization composition the record page offers Change Slug and the click answers 404

objectstack-ai/objectstack#24318 · opened

on Oct 18, 2026

6

[PM seat] repo:cloud · seat 2 — 🟢 os-zhuang · session_01Cbdek8SKSHxddGqTPZXdqX

objectstack-ai/objectstack#24145 · opened

on Oct 17, 2026

12

plugin-security: organisation admins assign positions and permission sets to their own members inside the D12 boundary — gate branch, overrides, explain and my-delegable-scope, three-posture acceptance (ruling B on #23960)

objectstack-ai/objectstack#24136 · opened

on Oct 17, 2026

3

driver-memory and driver-mongodb force-stamp `updated_at` on every update and ignore `DriverOptions.preserveAudit`, which the contract says keeps a supplied `updated_at` — historical import and the system backfills move the stamp on those two drivers

objectstack-ai/objectstack#24027 · opened

on Oct 16, 2026

3

Navigation Menu

Repository navigation

Issues

plugin-approvals: the hand-built contexts its writes run under don't fully carry the deciding user's context, so a runAs:'user' hook they fire gets neither the user's organisation peers nor the user's own grants (the producer half of #24497)

pm-dispatch lanes/hotcrm.md:8 and :33 still forbid the repo:hotcrm seat to grade and point at a dead "SKILL.md 多仓协调规则 4": align them with the single-lane rule, as ruled on hotcrm#2178 (A)

A conditional validation rule's `when` that reads through a lookup (`record.account.status`) saves at every door, but `checkConditional` evaluates it unhydrated, so every write the rule guards is refused as unevaluable

fix(release): the console injection assertion has a real witness on a .objectstack-sha pin, instead of passing vacuously

plugin-approvals: the request and action list views show an Object column with the target object's API name (`object_name`, such as `showcase_announcement`), the type half of the record pointer pair, drawn as plain text

objectql: a runAs:'user' hook fired from a hand-built system context (plugin-approvals' writes) runs without org_user_ids, so sys_user's org-members scope drops out and the hook sees only the acting user's own row

chore(cli)!: 18.x restore of the 18.0 guards — re-open the upgrade ceremony and walled boots

plugin-security: the shipped permission sets stop copying the identity objects' row-scope literals once those objects declare them as their default row scope (#24340 follow-up, ruling E′ item 3)

nightly-tiers: red on main

objectql: a foreign bound action named like an action the target object already declares is not attached and nothing reports it, while the two packages' handlers overwrite each other silently — the collision follow-up of #24400 (PR #24458)

docs(qa): re-author access-security.platform-owner-email-anchor for the Default Organization grant — PR #24373 landed #11979, the trigger the item names for its own re-author

Registry canary failed: fresh npx create-objectstack install is broken

upgrade-impact comparison after v18: report the non-access classes to the administrator, and retire the zero-consumer package-upgrade.zod.ts

upgrade-impact comparison, access class (v18): a vendor upgrade that would orphan, re-enable or collide with a customer's access choice is refused until an administrator confirms, and raised at boot

pm-dispatch(decision-analysis): a decision analysis recommends exactly one option — retire the 「回退项」 line (the maintainer's word, 2026-10-19)

plugin-sharing: refuse a new or renamed sys_sharing_rule row that takes a declared rule's name, and reconcile the shadowed declaration's grants on a same-name write (ruling B′ on #24378)

tooling(board-snapshot): the scheduled Board Snapshot failed its count check twice running (exit 2 at 08:25Z and 14:18Z on 2026-10-18): the archive and the live board disagree on the open-issue count

ADR-0131 D9 on a walled control plane: three framework writers land NULL organization_id rows on every sign-up (the self-registration grant, the verification mail, activity about org-less records)

platform-objects: the identity objects declare their default row scope (the literals the shipped sets copy today), and the registry refuses an `extend` contributor that loosens a platform object's default (#24164 ruling E′)

metadata-core: `MetadataEventSchema.source`'s describe and the `sys_metadata_history.source` docs name labels ("studio", "rest", "ai", "git-import") that no producer writes — the family's collector after #24328

A resumed flow run writes as its trigger user (the submitter), not the approver who resumed it, so post-decision writes in an approval flow name the submitter as Last Modified By and in the audit log

platform-objects sys_organization: change_slug targets a cloud-only route, so on an open-source multi-organization composition the record page offers Change Slug and the click answers 404

[PM seat] repo:cloud · seat 2 — 🟢 os-zhuang · session_01Cbdek8SKSHxddGqTPZXdqX

plugin-security: organisation admins assign positions and permission sets to their own members inside the D12 boundary — gate branch, overrides, explain and my-delegable-scope, three-posture acceptance (ruling B on #23960)

driver-memory and driver-mongodb force-stamp `updated_at` on every update and ignore `DriverOptions.preserveAudit`, which the contract says keeps a supplied `updated_at` — historical import and the system backfills move the stamp on those two drivers