docs: open data service client implementation

This commit is contained in:
2026-08-26 17:30:23 +08:00
parent f245603923
commit 7e54b8fbda

View File

@@ -0,0 +1,82 @@
# Task: Implement MakeLore Development Data Service P0 client
## Identity
- Task ID: 20260826-makelore-data-service-client-b72e4c19
- Mode: Feature
- Branch: codex/20260826-makelore-data-service-client-b72e4c19-makelore-data-service-client
- Worktree: D:\Datas\OthersProjects\makelore-data-service-client-b72e4c19
- Base commit: f2456039230f68e3ecb2c8653fc3379c23bbe5ce
- Owner: codex-root
- Status: Planning
## Scope
- Coordinate the repository-local `implement-spec` run for client tickets ML-00
through ML-09 from post-Pi-integration base
`f2456039230f68e3ecb2c8653fc3379c23bbe5ce`.
- Deliver durable MakeLore project identity, Main-owned Data Service cloud/Host
operations, purpose-specific Pi tools, preview data sessions and CDP injection,
the thin generated SDK, bundled Data Service Skill, focused/full verification,
repository-local review, and one remediation pass when findings require it.
- Own the client implementation branch and merge only commits returned by isolated
ticket worktrees in dependency order.
## Intent And Constraints
- Follow the server repository's implementation specification, ticket graph,
canonical integration contract, and accepted ADR without reopening the frozen P0
product scope.
- Preserve the integrated Pi `0.84.2` hard cutover, product-neutral Snapshot/Patch
contracts, Main/Renderer trust boundary, current Host route ordering, and the
existing Agent Browser abstraction.
- `.niancode/project.json` owns the durable optional `projectId`; local project IDs,
Pi session/resource IDs, and the `opencode-projects` compatibility store name remain
local identities.
- Electron Main remains the only Works credential owner. Generated code receives only
an ephemeral exact-Origin data capability; no credential, owner, path, arbitrary
endpoint, or cloud project ID becomes a model-controlled input.
- Do not restore OpenCode, add Firebase compatibility, published-runtime support,
retries for ambiguous writes, a filesystem-copy engine, or a generic operation
multiplexer.
- The root `main` worktree remains clean and unowned. All writes stay in this isolated
coordinator worktree or ticket-specific linked worktrees.
## Planning Gate
- Result: Passed on 2026-08-26.
- Loaded MakeLore `AGENTS.md`, required project-memory entry documents, current state,
accepted auth and Pi decisions, relevant architecture/domain/evidence/commitment
material, the cross-repository Data Service spec/graph/contract, and the exact Pi,
Host API, project-storage, session, and Agent Browser seams at the recorded base.
- Registry review found 147 historical owners. Most are ready-for-integration and
represented in the selected base. Ten remain marked planning; nine have placeholder
scopes and therefore unknown coordination state, while one owns an unrelated AI
Design E2E file. No declared Data Service or owned-path semantic conflict exists.
- Real PostgreSQL, signed-in accounts, deployment inputs, and platform-specific E2E
prerequisites remain external acceptance inputs and will not be inferred as passed.
## Ticket Ownership
- ML-00: coordinator in this worktree.
- ML-01 through ML-07: isolated implementer worktrees from the exact merged frontier
commit, with the file ownership defined by the ticket graph.
- ML-08: repository-local merger in this implementation worktree.
- ML-09: read-only review followed by one isolated remediation implementer if needed.
- X-01: coordinated only after reviewed server and client branches are ready.
## Outcome
- Not completed.
## Verification
- Not run.
## Follow-ups
- None recorded.
## Promotion Candidates
- None recorded.