test: re-prove strict trailing-comma rejection on current master

[lost-rob0t]

Evidence-only RAGE/TDD freshness transaction for #105 and the strict-JSON research transaction in lost-rob0t/starintel-auto-research#142.

Starting commit: 52948721d8981e9aa5ccad4efd77185e52af845b (current master after #119).

This adds the smallest hermetic regression for the exact malformed shape previously observed by ZAP: a JSON object with a trailing comma. It requires parse-json-octets to signal HTTP 400 / malformed_json. A later control fixture also proves [1,] is rejected in the resolved StarIntel runtime, so the deterministic RED is specifically the object-member trailing-comma case.

Current exact head: a2368ba58d0347af8f85efd85aba7b021ded65b5.

Exact-head result: Smoke #423 is RED on the object trailing-comma regression; Container Stack #424, Canonical schema lock #308, and Operational salvage #253 are GREEN. Preserve the failing regression unchanged.

Control-plane identity — reconciled

The authoritative research identity is now STAR-RESEARCH-060 Strict JSON HTTP Boundary in lost-rob0t/starintel-auto-research.

Historical comments on this PR used STAR-RESEARCH-041 and STAR-RESEARCH-042 while the Auto-Research corpus had ID collisions. Those identifiers are transaction history only. Auto-Research PR #142 was reconciled and merged to main as 50b0d6ad70da54af1420943b1f137b0a78e09b58; canonical adard.research-approval.v1 metadata was then landed on main at exact head dd01622f2e1acbafb7d929f824167492b7bef0e8. The exact-head Org-roam Pages workflow for dd01622... completed successfully.

Publication and green CI do not change authority. Operator research approval for STAR-RESEARCH-060 remains PENDING. Research approval would authorize design/adversarial review only, and parser implementation remains blocked until a later canonical design receives separate explicit operator design approval.

No product implementation is changed and no assertion is weakened.

[lost-rob0t]

RAGE/TDD result on exact head ad8d05c20ef2bae040af5c431de5e53d89182e6b: the freshness regression is RED.

Smoke run 32913779058, unit job 98013027383, immutable hermetic artifact 9587427516 executes TRAILING-COMMA-JSON-IS-A-400-CLIENT-ERROR and fails because the expected http-input-error condition is NIL. The follow-on accessor call then errors because HTTP-INPUT-ERROR-STATUS has no method for NIL. Suite summary: HTTP-BOUNDARY-TESTS discovered=30 executed=30 passed=29 failed=1 skipped=0.

This proves current master behavior still accepts the exact trailing-comma shape at parse-json-octets; #119 did not supersede the #105 parser defect. Other exact-head gates are green: Container Stack #407, Canonical schema lock #291, Operational salvage #236; Smoke #406 is red specifically on the new regression, while its service-backed integration job is green.

Per STAR-RESEARCH-041 governance, preserve this RED test unchanged. Do not implement a parser fix until explicit operator research approval authorizes design and explicit design approval later authorizes realization.

[lost-rob0t]

Fresh exact-head TDD refinement on a2368ba58d0347af8f85efd85aba7b021ded65b5 (2026-08-26): Smoke run 32998524065, unit job 98273937069, immutable hermetic artifact 9617577223 reports HTTP-BOUNDARY-TESTS discovered=31 executed=31 passed=30 failed=1 skipped=0.

The original object regression remains RED: TRAILING-COMMA-JSON-IS-A-400-CLIENT-ERROR still captures NIL, proving the object form with a trailing member comma is accepted by parse-json-octets instead of producing HTTP 400 / malformed_json.

The newly-added array regression is GREEN: TRAILING-COMMA-JSON-ARRAY-IS-A-400-CLIENT-ERROR passes for [1,]. Therefore the observed StarIntel runtime behavior is asymmetric: object trailing commas remain accepted, while array trailing commas are rejected. Do not generalize the proven defect to arrays from upstream-parser source inspection alone.

The implementation path on current master is still YASON -> JSOWN, and qlfile.lock resolves the Quicklisp distribution to 2024-10-12 rather than pinning YASON as a standalone revision. Empirical exact-head behavior is authoritative for this transaction.

Other exact-head gates remain green: Container Stack #424, Canonical schema lock #308, Operational salvage #253, and the Smoke service-backed integration job. Preserve the object RED regression unchanged. This evidence refines STAR-RESEARCH-041; it does not authorize parser implementation before the explicit research/design approval gates.

[lost-rob0t]

RAGE control-plane ID reconciliation (2026-08-26): the authoritative strict-JSON research transaction is STAR-RESEARCH-042, not STAR-RESEARCH-041. starintel-auto-research main had already allocated STAR-RESEARCH-041 to the approved STAR URI/FediWatch research; strict JSON was renumbered to roam/research/star-server/STAR-RESEARCH-042-strict-json-http-boundary.org. Historical comments on this PR that say STAR-RESEARCH-041 refer to the strict-JSON transaction before that renumbering.

The technical evidence is unchanged: exact head a2368ba58d0347af8f85efd85aba7b021ded65b5 keeps the object trailing-comma regression RED, the [1,] array control GREEN, Smoke #423 red, and Container Stack #424 / schema lock #308 / Operational salvage #253 green. Preserve the RED regression unchanged.

Governance is also unchanged except for the corrected identifier: explicit operator research approval of STAR-RESEARCH-042 is still PENDING and would authorize design/adversarial review only. No parser implementation is authorized until a later canonical design receives separate explicit operator design approval.

[lost-rob0t]

Control-plane correction to my prior ID note: do not use STAR-RESEARCH-042 as the strict-JSON authority ID. Current starintel-auto-research/main at 52530279e1513da61d99195d985135a9d06fe94c already owns STAR-RESEARCH-042 for the approved Bixby OAuth research (STAR-RESEARCH-042-bixby-oauth-authorization-code-provider.org, issue #144). Open strict-JSON research PR auto-research#142 is 16 commits behind main and attempts to add a second, different STAR-RESEARCH-042; that canonical-ID collision is now pinned on #142 and must be repaired through the repo-native sync/validation/publication workflow before the strict-JSON transaction has a stable authority identifier.

The TDD evidence here is unaffected: exact head a2368ba58d0347af8f85efd85aba7b021ded65b5 still proves the object trailing-comma defect RED, while [1,] is a GREEN control; Smoke #423 is red and Container Stack #424 / schema lock #308 / Operational salvage #253 are green. Preserve these tests unchanged.

Until auto-research#142 is reconciled against current main, refer to the authority as the strict-JSON research transaction in auto-research#142, not STAR-RESEARCH-041 or STAR-RESEARCH-042. Its operator research approval remains PENDING; no design or implementation is authorized.