Skip to content

refactor(market): give shared records and protected posting one owner - #168

Merged
LIghtJUNction merged 12 commits into
mainfrom
fix/market-boundaries-20260929
Sep 29, 2026
Merged

LIghtJUNction merged 12 commits into
mainfrom
fix/market-boundaries-20260929

Conversation

@LIghtJUNction

@LIghtJUNction LIghtJUNction commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Current implementation

Refs #159 #83 #85. Head 65b7330, tree 4c76f69dc2ec93fed09e4748e3aa5d846bcf35f0. Based on original main476e64f; synchronization with newly merged #165/current main is still required before final integration.

The existing shared order records, catalog reads, protected ledger posting and bounded managed-delivery verification now have canonical owners in market.order_records, market.catalog, market.ledger, and market.managed_delivery. Old plugin paths re-export the identical function objects. All existing market use cases, including function-local imports, stop importing the four orders/store/money/delivery business entrypoint modules.

The single _ESCROW_WRITE object is defined with protected posting in ledger and re-exported by escrow; identity guards and checked release call sites stay the same. No second escrow/ledger/state machine, public capability or Root issuance path. Versioned schemas, transactions, account locks, signatures, IDs and receipt bytes are not changed.

Independently inspected evidence

  • Red 36483360971, exact8692ad6c / tree907f518: 7 failed, 3 passed, 0 errors/skips. All failures were new ownership checks; actual PostgreSQL buyer/seller privacy, forged escrow authority with zero ledger writes, and signed-receipt byte preservation/replay passed. Artifact10998081065 SHA256 07f566e15500142c37223782d5cc10086bb9e92a967e5a204c52c374abae3600 verified.
  • Source-only assembly 36483781552 succeeded: checked exact source blobs, all 23 moved functions, all remaining entrypoint bodies/schemas and existing market state machines after excluding only import rewiring. Output f92390f / treef3f8a2c.
  • Artifact10997307359 downloaded/read/hashed: 2dbcbf167086480216596757ffd32b42fa8ccc61cdea3d767e2862d1aba3ae74. Patch digest independently verified as 0f3ee2de9d5cb04c50ebf4b573c44652fa7a50a225f3e006f50944432e9173c9.
  • Both one-shot source assembly files are removed from the submitted tree. Current-head focused/full CI has been triggered; green is not yet claimed.

Final gates and coordination

New contracts, existing v1/v2/v3 checkout/clearing/Bounty/redemption/recovery, complete four-shard exact-node-ID, conformance/build and applicable Recovery safety must pass on the final synchronized head. No existing test skipped or weakened. Notes: docs/MARKET_BOUNDARY_PROGRESS.md.

Does not overwrite #155 recovery, #165/#167/#169 core/tool/executor implementations, or #166 supplemental storage tests. This does not close #71/#72/#85's broader production acceptance. No production deployment, real Root/PIN, funds, outbound delivery, backup destruction or recovery promotion.

LIghtJUNction and others added 5 commits September 29, 2026 05:09
… cloud branch

Refs #158 #82 #83 #85. Patch SHA-256 244778f572724b991a8b14ff3334b810a3af14329de999bf148c5445950c8a02. Restrict publishing to 19 enumerated files and this feature branch; remove the one-shot publisher in the generated source commit. Record RED and explicit full-server installation compatibility.
…al format

The source archive normalizes pyproject formatting; cloud run36484923358 refused that hunk before any publish. Commit the same reviewed dependency split against the live repository file and apply the unchanged verified source patch excluding only that already-committed metadata. Refs #158 #83.
…endencies

Refs #158 #82 #83 #85. Preserve signed bytes, credential persistence and explicit full-server installation.
… implementation

Combine #171 client5f56bbe4 with #167 e768cbc without changing either other work stream's ref. Retain #167 executor, packet/schema, QuerySession/RelationalSession and all regression tests; retain merged #165 tool contract. Core codec owns the one result_wire function; packet re-exports that same object and executor keeps its packet import. Preserve all client helper, installation and signature tests. Apply the complete frozen-JSON comparison correction from #169 3db973a, whose 34 focused regressions passed in cloud.

Refs #158 #156 #157 #83 #85. Final combined tree requires new full/focused cloud gates; no historical GREEN or production acceptance is claimed.

Copy link
Copy Markdown
Contributor Author

专项 GREEN 已独立验证:run36484188517,精确 head 65b7330d248f4af96ac9ecd1f1fad3fdc6f59782 / tree 4c76f69dc2ec93fed09e4748e3aa5d846bcf35f0 / dirty=false,10 新契约 +118 既有回归 =128 passed,0 failures/errors/skips。已下载artifact10998581967,ZIP SHA256 240197b4324974bfdf23376e01c61c7e40bf9ffddeb983a37f6abc256368348d 与提供方一致,读取source.json及两个JUnit并核对实际testcase数量。

Recovery36484195539已成功;完整PR run36484195530仍有分片执行中,不能以专项替代。已读取GitHub合并提交59b22f919924885e75211d2a27c70f9a094a3af9的父列表,确为main08c58928 +feature65b7330d;最终合并前还将核对当前main/最终树和完整四分片节点集、conformance/build。现阶段不关闭#159,不动生产。

@LIghtJUNction
LIghtJUNction marked this pull request as ready for review September 28, 2026 21:31
Copilot AI lite review requested due to automatic review settings September 28, 2026 21:31

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
🔒 Security Review ✅ Completed 2026-09-28T21:38:02.937538Z 65b7330 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Join #167 2d1cc44 and client integration3ae9f8ef. Adopt its five exact workflow/test/note blobs, including the expanded ledger/migration/recovery selection and the same complete frozen-JSON assertion. No product source changes from the preceding integration. Record the independently verified isolated client7/wheel/four-transport GREEN without treating it as this final combined head's result.

Refs #158 #156 #157 #83 #85. Only the client feature branch will advance; all final-head gates remain required.

Copy link
Copy Markdown
Contributor Author

接续现有#168(不重写市场实现)。实际head65b7330d248f4af96ac9ecd1f1fad3fdc6f59782已刷新;已读取全部新所有者、回归测试和差异,以及原RED/专项128通过证据。下载旧full36484195530的shard0 artifact10998743543,独立SHA2567087df67dfaec8bdcf4e8ffa2e6fdc62376fa150b34d9cd2971b11406ee69028核对,源码仅用于静态审读。

目前main04ffad5已含#167/#175/#173。#171客户端正在组合head6c1ea44/tree9e5f82de上跑CI;本流准备在#168保留65b733与6c1ea两个真实父链,只处理market.policy的QuerySession类型接线,原#168其余业务函数/版本/SQL保持。已对照当前main:四个入口剩余函数排除import后AST逐个相同,其余市场状态机变化仅原import重接线和_ESCROW_WRITE唯一owner移动;不会覆盖当前核心/hosting/token/client。

最终需在组合头重新跑原128专项和完整四分片/node-ID/conformance/build/Recovery;按#171再#168的顺序合并。旧body的GREEN pending由原评论澄清,但旧绿不替代新组合验收。不操作真实资金/Root/外发,不关闭#71/#72/#85生产验收。

@LIghtJUNction
LIghtJUNction merged commit 1f35232 into main Sep 29, 2026
13 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[P1] 确定性清算、银行边界、报价兑换与 Entitlement

2 participants