[finding] board-snapshot is red on every run: the archive holds 59 open (113 total) issues GitHub no longer shows. Restore them or record them in gone.json #22999

Activity

1. objectstack-fleet commented on Oct 12, 2026

   

   objectstack-fleetbot

   on Oct 12, 2026

   Contributor

   More actions

   Triage: first grade, tooling · priority:p2 · domain:skills · area:devpath, into pm:queue for step 1, the list. Steps 2 and 3 follow from it

   Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-12T09:22Z. ⛔ Not a claim, ⛔ not a dispatch.

   • Why it enters the queue: this is tooling (scripts/pm/board-snapshot.mjs, PM tooling, domain:skills). The maintainer filed it and directed the work, which exempts it from the queue-entry lines.
   • Why p2: the archive exists for content destroyed with a suspended fleet account (PM board snapshot: a scheduled workflow archives every issue, comment and PR record to an orphan branch, so an account suspension destroys no record — with a restore recipe #17390). About 113 records it holds no longer show on GitHub. The red is 4 runs a day, and the archive cannot tell new losses apart while it stands.
   • Direction, step by step:
     1. The seat measures and records the list on this card. For every number the archive holds as open, plus the closed surplus, it reads the live API: 404 or 410 means gone, and a state difference means stale. It is read-only. ⛔ No restore and no gone.json entry in this step.
     2. Then the card moves to the decision box with a 「维护者速读」 and one question: restore the gone numbers (--restore=N), or record them as gone. The seat recommends one letter, with the count and a sample of titles.
     3. Any stale-only surplus is a separate card about the delta walk (related to board-snapshot: once the open set completes, every run spends its whole budget on the closed history and never re-reads the live board — cards created or updated since 2026-09-10 are in no snapshot #18045), filed by the measuring seat, ⛔ not fixed here.
   • ⛔ The count check is not loosened to make the run green.
   • Triage: lands in scripts/pm/board-snapshot.mjs and board-archive (domain:skills); rationale: PM tooling, maintainer-directed.
2. objectstack-fleet

   added

   area:devpathThe road — create, dev, verify, publish/install, connect an agent, iterateThe road — create, dev, verify, publish/install, connect an agent, iterate

   domain:skills

   pm:queue

   priority:p2Medium: important, M3Medium: important, M3

   tooling

   on Oct 12, 2026
3. hotlong commented on Oct 12, 2026

   

   hotlong

   on Oct 12, 2026

   ContributorAuthor

   More actions

   Maintainer decision: accept as gone (do not restore).

   I checked each of the 65 archived-open issues the live board no longer lists against the API on 2026-10-12:

   • 42 destroyed (404), all authored by suspended accounts (os-sam 32, os-musk 8, os-altman 2): [finding] sys_user.manager_id now carries two independent organization screens, in two packages, with no shared code #11286, manifest.integrity declares per-file artifact digests the spec says the runtime re-verifies at unpack — nothing computes them and nothing checks them #11331, manifest.permissions is live on its LEGACY string[] arm only — the structured PluginPermissionsSchema (services / hooks / network / fs) has zero readers, and new code is told to prefer it #11333, INotificationOutbox has no cancellation, and ack() on an unclaimed pending row silently succeeds in both implementations #11453, The Clone dialog for a permission set now offers five raw JSON blobs as editable inputs — defaultFromRow has no non-editable carry-over #11753, A multi: true hook that writes the SAME key with per-row VALUES still applies one row's value to every matched row — the residue #14099's key-set refusal deliberately leaves open #14744, action-governance-scope-divergence.test.ts's prose describes the C4 boundary as still open after #15252 closes it — a reader trusting it could revert the fix #16613, [finding] Ruling A on #16231 narrows IScopedObjectRepository, but ctx.api.object(name) resolves through the CLASS ObjectRepository — the hook-facing door keeps Promise<any>, and updateById keeps it too #16786, [finding] check-adr-0087-registration's type-surface-only category is unclaimable by the class it was built for: TWO predicates refuse it whenever the narrowed declaration lives in packages/spec/src/contracts/** #16787, retiredFromLoadPath: true does not keep a conversion off any load path — three runtime seams replay every retired entry with includeRetired: true, and apply.ts says only migrate meta does #16864, [finding] FieldSchema refuses notNull / not_null by prescribing required — the one key ADR-0113 says is NOT a column constraint — while the correct sentence is reachable only from storageNotNull, a spelling nobody writes #16867, [finding] packages/cloud-connection/vitest.config.ts carries #16189's defect verbatim — "No test block" and "this file's only effect the alias above" are both false there too #16917, analytics: POST /analytics/dataset/query never Zod-parses its selection at the door, so a malformed member reaches dataset-executor unrefused — the sibling routes lift the same failure to a 400 #17058, Phase 1b of #11333: make the registered granted-permission set actually REFUSE — the ADR-0025 materialize seam that gives each plugin its own SecurePluginContext #17147, Reading needed from the cloud side: can ArtifactKernelFactory serve an artifact that declares grantedPermissions but carries NO packages array? #17148, driver-memory: the stored-ARRAY value axis is still unrepaired outside the equality arm — $in/$nin, the text family and the ordering family answer one filter two ways, and the two exclusion arms answer it in the WIDENING direction #17286, driver-memory answers a text operator over a DECLARED temporal column by matching its canonical ISO text — the opposite of #15683's declared-type answer, and the existing pin passes for the wrong reason (a millisecond mismatch) #17348, [finding] post-stamped stamp contract is one-way on long-lived bodies: a bare stamp inside a quoted span can neither stay nor be declared, so the artefact can never take a now-token write again #19238, sys_user: declare a set_user_manager row action posting the admin set-user-manager endpoint (moved from objectui#9361; objectstack#16678 Phase 2, ruled) #19249, [finding] the hand-over rule 「Served-tier: takes a bare N/M」 is WRONG and would be refused — the checker requires the constant's NAME, with N/M only as an optional prefix #19309, [finding] the REST proxy appends its footer to EVERY PR-body PATCH, so a body that already carries one comes back with two — the remedy is to PATCH the body with the footer STRIPPED #19336, feat(spec): ISecurityService gains the effective-object-permission reader — the packages/spec half of objectstack-ai/objectstack#18783, split out under 强制条款② #19354, [reading request from domain:spec] Re-measure the PluginCapabilityManifestSchema census on objectstack-ai/cloud — #18623's ruled retirement is STOPPED on it, and no seat with cloud access has taken it #19361, [finding] three sibling list doors carry the same declared-but-never-read limit/cursor shape that #17667 is retiring on /packages — export jobs, AI conversations and automation runs #19365, spec: declare what an ABSENT scale means per numeric field type — percent ⇒ 0 — the @objectstack/spec half of objectstack-ai/objectui#9843 (ruled A′) #19368, [Decision] app / position 声明 allowRuntimeCreate: true 而作者期规则零命中 —— 退役这个声明,还是把规则造出来? #19370, [finding] a { $field } reference as a $between endpoint is refused by the schema door and accepted by the runtime door — the #19071 shape, one endpoint spelling over, already ruled on the schema side #19377, [finding] check-widening-tells T2 fires on ANY lone quoted string on a contract-source line — no closed-set opener required, so the row asserts "a new member of a closed set" it never measured (7 false tells blocking PR #19314) #19384, [finding] datasource is a 14th allowRuntimeCreate: true type with zero live runtimeTypes declarations — invisible to #19275's census because its registry entry is the only MULTI-LINE one #19389, [finding] connector.connectionTimeoutMs is authorable, bounded and defaulted, and nothing reads it — every one of its five non-spec mentions WRITES a hardcoded 30000; and a WHATWG fetch cannot observe the connect phase, so it is not implementable as declared #19410, Document the /meta/types erased-authoring-input mark on the hand-written metadata API page — the documentation half of #19295 #19415, [finding] check-issue-citations never probes a self-qualified citation: buildBoard drops every qualified row from the probe set while classifyCitation resolves objectstack#N against that same board — so a valid same-repo number always reports allocated-but-absent #19420, [finding] zod 4.4.3's treeifyError and error.format() throw on any issue path containing __proto__ — so the formatter crashes on exactly the refusal PR #19147 landed to make that key safe #19421, [finding] check-dts-closure.mjs shares check-dts-emitted’s manifest criterion, so the post-build sweep is chunk-blind the same way #19443, [finding] check-dts-references.mjs is wired into packages/spec only — 67 of the 68 builds that run the sibling guard do not run it #19444, [finding] check:skill-examples spells a PREREQUISITE refusal as exit 1, so --ran reconciliation reads it as a RED #19450, spec(lint): wire the inert runtime-create rules for action / hook / report / skill / email_template / mapping — six types, one edit (ruling #203/4 group A+C) #19474, reading(spec): which write door governs a runtime translation create — TranslationItemSchema and TranslationBundleSchema disagree (ruling #203/4 group B) #19476, reading(spec): the tools universe rule can only REMOVE findings — what would a runtime tool create actually be judged by? (ruling #203/4 group B) #19477, [finding] the permission-set publish door derives its zero-row failure reason by ELIMINATION, so an unreadable row and an engine-rejected write are both reported as 'publish carried no owning package' #19481, feat(spec): ISecurityService gains the effective-object-permission reader — the packages/spec half of #18783 (RECONSTRUCTED after the os-sam suspension) #19539, Charter(grading contract): the triage criterion missed ten times across ruling #202 B — each with the card it was measured on (REBUILD of the lost #19494) #19546
   • 17 transferred inside the org: #11617 → hotcrm: the six screen-flow dialogs become visible to os lint once the CLI's flow/screen i18n bucket lands — translate them or record the debt hotcrm#1975, #13469 → RelatedList renders user columns as raw IDs while ordinary lists resolve user names objectui#10112, #14026 → Re-raise of #4375 with the downstream confirmation it asked for: the console import wizard never sends mappingName and hardcodes writeMode:"insert", so a named mapping's upsert can never reach a user objectui#10102, #14482 → hotcrm: carry the wall-clock unit of the case SLA matrix in identifiers and one test, collapse the four prose warnings to one (app half of objectstack#13801, mechanism B) hotcrm#1974, #14831 → [seam → repo:objectui] Retire DEFAULT_UPGRADE_URL = '/settings/billing' — the app-shell's tolerant default for the entitlement upgrade CTA points at a path no router serves (objectui half of cloud#1869) objectui#10437, #14887 → [repo:objectui] Pure date fields shift one day for viewers west of UTC — '2026-08-01' renders 7月31日 in PDT; the display formatter parses the date-only string via new Date('YYYY-MM-DD') (UTC midnight) then reads local getters objectui#10110, #14912 → [repo:objectui] Edit affordance is derived from the object-level writeScope only — a user holding a record-level edit share (sys_record_share) sees no Edit button while PATCH on the same record succeeds objectui#10107, #15138 → finding(objectui chatbot): detectBuiltAppPackage reads any drafted[] carrying a type:'app' entry as a whole-app build — now also true of an incremental apply_edit that stages the app artifact; the envelope's kind:'edit' is the disambiguator objectui#10109, #15417 → objectstack-ai/cloud#2526, #16127 → [repo:objectui] Master-detail form's batch save sends owner_id on every parent and child operation, so a permitted line edit 403s with "'owner_id' is system-managed" — the list view's inline grid sends only the dirty cell and succeeds objectui#10108, #16519 → hotcrm #1586 step-3 table: annotate the security-owd-alias row with its intake scope — the rule is alive but unreachable on a defineStack-authored app (measured in #16109) hotcrm#1973, #17163 → objectstack-ai/cloud#2521, #18377 → [seam -> repo:objectui] the confirm card should send back the IDENTITY of the blueprint it rendered — the runtime's receiving side is already built and is the last gap in the consent gate (cloud#2006) objectui#10438, #18387 → [seam -> repo:objectui] the 80% / 100% storage banner has no renderer — cloud serves the numbers and the verdict, nothing shows them objectui#10439, #18397 → [seam -> repo:objectui] Re-seed / Purge throw the error CODE away — readApiError(payload, res).message renders the withheld 5xx constant while ENVIRONMENT_KERNEL_UNAVAILABLE arrives unread objectui#10432, #20787 → [repo:hotcrm] switch hotcrm's vendored half-state patrol to objectstack's composite action pinned to a sha, and delete the vendored copies — hotcrm's half of #18471 (ruling 只做②) hotcrm#1972, #21767 → [finding] spec(ui): an action:group / action:menu member with an object params on a non-api type passes the component-props gate, and the container drops it at run time objectui#11638
   • 6 closed after the 08:47Z snapshot and refreshed by the next delta, so they are not in the ledger: platform-checklist + NORTH-STAR: retire records-forms.picklist-org-append and the "customers append values per organization" promise — the per-organization picklist append is ruled out #22869, finding: a stack's functions array accepts two entries authoring one name, and objectstack build exits 0 shipping the second under a suffixed name (on main, not callable after load), where composeStacks already refuses a duplicate function name #22902, check:platform-checklist is red on main #22924, plugin-audit: a user's own sys_user_preference writes (ui.recent) come back to them as "Updated User Preference 'ui.recent'" inbox notifications — the console bell shows six of them and nothing else #22961, hourly full run: red on main (CI) #22968, write-pace self-test: the lease battery's "children's own starts are that far apart too" case compares two processes' spawn latencies and went red on a loaded runner (149 ms against a 150 ms floor) #22986

   Those 59 (destroyed plus transferred), and only those, are recorded in board/gone.json on board-archive (commit 9efc902), one row per number with its reason. The count check subtracts the ledger's size, so listing anything beyond the real surplus would hide the next disappearance.

   Verification run: https://github.com/objectstack-ai/objectstack/actions/runs/38231206449 is green. board-snapshot exited 0; count check ok: 171 archived open − 112 on the board − 59 in the ledger = 0. R2 synced 101 objects; the 2026-10-12 daily tarball was already present.
4. hotlong

   closed this as completedon Oct 12, 2026