docs(todos): close D7 status and activate next P0 fix claim - #180
Merged
Conversation
Update D7 lifecycle status across project/agentscope boards and feature aggregation evidence to reflect merged delivery.\n\nChanges:\n- Mark CLM-20260302-D7 and CLM-20260302-AG3 as done with merged PR evidence (#138).\n- Align D7 priority table/stage annotations from active closeout to completed baseline.\n- Promote feature doc docs/features/agentscope-d7-plan-state-tools.md to status=done and add review/merge links (#138/#143/#146).\n- Activate next fix claim CLM-20260304-AG10 for T0-6 (search_file path contract regression) and move T0-6 status to doing.\n\nWhy:\n- Keep claim ledger, dependency board, and feature lifecycle synchronized with actual merged state.\n- Start next highest-priority, dependency-free P0 fix immediately after D7 closure.\n\nVerification:\n- ./scripts/ci/check_governance_evidence_truth.sh => passed\n- ./scripts/ci/check_governance_traceability.sh => passed\n- ./scripts/ci/check_design_doc_drift.sh => passed
Reorganize Claim Ledger structures so project-level aggregation and AgentScope detailed execution are fully cross-referenced and auditable. Key updates: - project_overall_todos.md: - Add explicit completeness policy: T5-* keeps aggregate claims here; detailed execution is owned by agentscope_domain_execution_todos.md. - Extend Claim Ledger with to map AG claims to D claims. - Add reconciliation snapshot notes to make current coverage explicit. - Keep AG10 (T0-6) as active project-level claim and clarify it is project-only. - Add explicit single-entry statement for AgentScope detailed TODO source. - agentscope_domain_execution_todos.md: - Add explicit reconciliation policy against project_overall_todos.md. - Extend Claim Ledger with for reverse mapping. Why: - Prevent claim drift between aggregate/project and detailed/domain views. - Make it obvious where to read detail vs. summary and ensure no hidden/unmapped claim entries. Verification: - ./scripts/ci/check_governance_evidence_truth.sh => passed - ./scripts/ci/check_governance_traceability.sh => passed - ./scripts/ci/check_design_doc_drift.sh => passed
Claim Ledger completeness fix for project-level TODOs. Changes: - Add CLM-20260304-AG11 for unfinished P0 scope T0-4 + T0-5 as planned/unassigned. - Update reconciliation snapshot text to include AG11 in project-only claim set. Why: - T0-4 and T0-5 are unfinished but previously had no claim declaration, causing mismatch between TODO list and claim ledger. - Keep project_overall_todos claim ledger complete before continuing execution sequencing. Verification: - ./scripts/ci/check_governance_traceability.sh => passed - ./scripts/ci/check_design_doc_drift.sh => passed - ./scripts/ci/check_governance_evidence_truth.sh => passed
Complete project-level Claim Ledger coverage for all unfinished T* items. Changes: - Add AG12 for T1-3. - Add AG13 for T2-1 remaining scope + T2-2 + T5-1. - Add AG14 for T3-1..T3-4. - Add AG15 for T4-2 + T4-3. - Add AG16 for T5-5 remaining scope outside D7. - Update reconciliation snapshot to include new project-only claims. Why: - Eliminate unclaimed unfinished items in project_overall_todos Claim Ledger. - Clarify partial-completion semantics where AgentScope sub-scope is done but parent project task remains open. Verification: - open-but-unclaimed check => empty - ./scripts/ci/check_governance_traceability.sh => passed - ./scripts/ci/check_design_doc_drift.sh => passed - ./scripts/ci/check_governance_evidence_truth.sh => passed
…e mapping Clarify AgentScope Claim Ledger completeness and remove ambiguity between domain task cards (D*-1..4) and execution slices (D*_a/b/c).\n\nChanges:\n- Add reconciliation snapshot under Claim Ledger showing unfinished domains are all covered by planned claims.\n- Add explicit mapping table from domain task-card ranges (D1-1..D8-4) to slice claims (D1S/D3S/D6S/D8S and completed domains).\n\nWhy:\n- Avoid confusion where a TODO exists but the corresponding claim is not obvious.\n- Make claim coverage auditable at a glance before dispatch.\n\nVerification:\n- ./scripts/ci/check_governance_traceability.sh => passed\n- ./scripts/ci/check_design_doc_drift.sh => passed\n- ./scripts/ci/check_governance_evidence_truth.sh => passed
Align project and AgentScope TODO governance docs so Claim Ledger entries are TODO-level only and no longer contain slice-level scope IDs.\n\nKey changes:\n- Updated AgentScope Claim Ledger to use D1/D3/D6/D8 TODO claims instead of D1S/D3S/D6S/D8S slice claims.\n- Revised deprecated historical rows to reflect TODO-level aggregate scope wording.\n- Added explicit ledger contract note that slices are maintained only in section 5.2.\n- Refactored section 0.2 mapping into TODO-claim coverage view and pointed slice details to section 5.2.\n- Updated execution rules to enforce active-claim at TODO level while keeping slice sequencing in detailed split section.\n- Kept project-level cross references in sync with new AgentScope claim IDs (CLM-20260304-D1/D3/D6/D8).\n\nRationale:\nThis resolves structural confusion where slice decomposition leaked into claim declaration, and restores a single source of truth model: Claim Ledger declares TODO ownership/status, while slice planning/execution stays in the detailed task breakdown.
Remove section "0.2 任务卡与 TODO Claim 映射" from AgentScope execution TODO doc because claim tracking is already fully represented in the TODO-level Claim Ledger and slice details are maintained in section 5.2.\n\nKey changes:\n- Deleted the extra mapping table that repeated claim coverage information.\n- Kept Claim Ledger as the single TODO-level declaration source.\n- Preserved slice planning details only in the detailed split section, matching the agreed governance structure.\n\nRationale:\nAvoid duplicate status surfaces and reduce maintenance drift between top-level claims and mapping snapshots.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ba3a0f047f
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | CLM-20260304-AG13 | T2-1（剩余范围） + T2-2 + T5-1 | | planned | 2026-03-04 | 2026-03-11 | `pending` | `—` | Layer-2 策略补齐：D5 子范围已完成，剩余上下文融合/多阶段 prompt/session 补齐待分配。 | | ||
| | CLM-20260304-AG14 | T3-1 + T3-2 + T3-3 + T3-4 | | planned | 2026-03-04 | 2026-03-11 | `pending` | `—` | Layer-3 工程化与文档治理未完成项补齐认领声明。 | | ||
| | CLM-20260304-AG15 | T4-2 + T4-3 | | planned | 2026-03-04 | 2026-03-11 | `pending` | `—` | 运行期配置统一与默认可观测采集持久化未完成项补齐认领声明。 | | ||
| | CLM-20260304-AG16 | T5-5（剩余范围，D7 子范围外） | | planned | 2026-03-04 | 2026-03-11 | `pending` | `CLM-20260302-D7` | `T5-5` 对应 D7 子范围已 done，剩余架构设计收口范围待分配。 | |
There was a problem hiding this comment.
The new AG16 row says its scope is the remaining T5-5 work outside the D7 sub-scope, but Detail Claim Ref points to CLM-20260302-D7, which is the already-completed D7 claim; this creates a false reconciliation link and can make the remaining work look traceable to a detail claim that does not actually cover it. In the project claim ledger, that undermines the stated “single detailed source + ref-based reconciliation” model for pending work.
Useful? React with 👍 / 👎.
Collaborator
Author
There was a problem hiding this comment.
Fixed in commit 5f60684.
CLM-20260304-AG16Detail Claim Refwas changed fromCLM-20260302-D7to—.- Note now explicitly states D7 was already closed by
AG3/CLM-20260302-D7, and AG16 only tracks remaining T5-5 scope outside D7.
This removes the false reconciliation link for pending remaining scope.
Adjust AG16 in project claim ledger to avoid a false detail-claim reconciliation reference. Key changes: - Set AG16 Detail Claim Ref to — because AG16 covers remaining T5-5 scope outside D7 and does not map to an existing detail claim. - Updated AG16 note to clarify D7 sub-scope was already closed by AG3/CLM-20260302-D7, while AG16 tracks only the remaining scope. Rationale: Using CLM-20260302-D7 as AG16 detail ref made pending remaining work look traceable to an unrelated completed claim, which violates the ledger reconciliation model.
Normalize status vocabulary in project_overall_todos so TODO entries and Claim Ledger use the same lifecycle states. Key changes: - Added explicit status-governance note under Claim Ledger: TODO items and claims share planned/active/done/deprecated. - Converted legacy TODO item statuses: - doing -> active - todo -> planned - merged -> done - Added missing Status lines for open P0/P1/P2/P3 items so claim-covered tasks are explicitly traceable. - Synced claim-covered items to ledger state, including: - T0-6 -> active (matches AG10) - T0-4/T0-5/T1-2/T1-3/T1-5/T2-1..T2-4/T3-1..T3-4/T4-2/T4-3/T5-1/T5-3/T5-4/T5-5 -> planned - Clarified T5-5 mixed progress: D7 sub-scope done via AG3/CLM-20260302-D7 while remaining scope stays planned. Rationale: This removes status drift between planning ledger and execution TODO entries, reducing assignment ambiguity and reconciliation errors during handoff.
Collaborator
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. Hooray! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
donein both AgentScope and project-level ledgers after merged deliverydoneand add merged PR links (feat(plan_v2): implement D7 plan state machine and revise/finish tools #138/docs(pr138): retrofit acceptance-pack evidence for evidence-first review gate #143/stack(pr138): integrate D7 implementation on top of evidence-first gate #146)T0-6) and move task status todoingWhy
Verification
./scripts/ci/check_governance_evidence_truth.sh=> passed./scripts/ci/check_governance_traceability.sh=> passed./scripts/ci/check_design_doc_drift.sh=> passed