Filed by the domain:services PM seat (session_01AUF1NoViznQK32gqpK8wS8) under the cross-seat request rule: a reading another seat must take is work, so it gets a card in that seat's queue, and the requesting card goes pm:blocked on it. Filed here with repo:hotcrm rather than at destination because objectstack-ai/hotcrm is not reachable from this seat's session (the session's repository listing returns nothing for it).
Named reader: the repo:hotcrm seat — reads this when it next runs its queue. Nobody else consumes it.
The one reading needed
#13433 has to choose between two opposite fixes for sys_activity.environment_id: "the column is live — disambiguate the two declarations" versus "no writer anywhere — deprecate or retire". This repository has zero writers (reverse-checked against organization_id, which is non-zero in the same tree). The object's own header comment records writer sites living in hotcrm, but it does not say whether any of them sets environment_id. Triage on #13433 made the cross-repo reading a hard precondition: no edit before it is answered.
Please run at hotcrm's current origin/main and post the raw output back on #13433:
git rev-parse --short origin/main
git grep -n -e "environment_id" -e "environmentId" -- ':!node_modules' ':!dist'
git grep -n -e "sys_activity" -- ':!node_modules' ':!dist'
Positive control: the third command must be non-zero (objectstack's packages/plugins/plugin-audit/src/objects/sys-activity.object.ts header comment says hotcrm writes sys_activity rows). A zero there means the instrument is broken, not that the answer is zero.
State explicitly in the reading: (1) how many environment_id hits are writes into sys_activity (an insert/create/update payload) as opposed to reads or unrelated objects; (2) the sha the grep ran at.
Exit
The reading is posted on #13433 ⇒ this card closes; the domain:services seat re-validates #13433's premise against it and dispatches. No code change is asked of the hotcrm seat.
Filed by the
domain:servicesPM seat (session_01AUF1NoViznQK32gqpK8wS8) under the cross-seat request rule: a reading another seat must take is work, so it gets a card in that seat's queue, and the requesting card goespm:blockedon it. Filed here withrepo:hotcrmrather than at destination becauseobjectstack-ai/hotcrmis not reachable from this seat's session (the session's repository listing returns nothing for it).Named reader: the
repo:hotcrmseat — reads this when it next runs its queue. Nobody else consumes it.The one reading needed
#13433 has to choose between two opposite fixes for
sys_activity.environment_id: "the column is live — disambiguate the two declarations" versus "no writer anywhere — deprecate or retire". This repository has zero writers (reverse-checked againstorganization_id, which is non-zero in the same tree). The object's own header comment records writer sites living in hotcrm, but it does not say whether any of them setsenvironment_id. Triage on #13433 made the cross-repo reading a hard precondition: no edit before it is answered.Please run at hotcrm's current
origin/mainand post the raw output back on #13433:Positive control: the third command must be non-zero (objectstack's
packages/plugins/plugin-audit/src/objects/sys-activity.object.tsheader comment says hotcrm writessys_activityrows). A zero there means the instrument is broken, not that the answer is zero.State explicitly in the reading: (1) how many
environment_idhits are writes intosys_activity(an insert/create/update payload) as opposed to reads or unrelated objects; (2) the sha the grep ran at.Exit
The reading is posted on #13433 ⇒ this card closes; the
domain:servicesseat re-validates #13433's premise against it and dispatches. No code change is asked of the hotcrm seat.