Feature: per-project task isolation when tracking multiple projects in one session

[Vdc-K]

Problem

When using a single CC session to manage multiple concurrent projects in task.md, the PACE hook treats all tasks as one pool. This causes cross-project interference:

• A [!] blocked task in Project A prevents Project B's work from closing normally
• <!-- APPROVED --> is matched globally — approval in one project bleeds into another
• Progress count (X/Y done) mixes tasks across projects, making it meaningless

Scenario

task.md
├── ### CHG-A: Project Alpha feature
│     - [!] T-001 blocked on external dependency
└── ### CHG-B: Project Beta bugfix
      - [x] T-002 done
      - [x] T-003 done

PACE stop hook reports "1 pending task" and blocks exit, even though Beta work is fully complete.

Expected Behavior

Either:

1. Section-aware parsing — support ## Project Alpha / ## Project Beta section headers in task.md, where each section is checked independently for pending tasks, APPROVED, and VERIFIED markers
2. Scoped markers — a way to scope <!-- APPROVED --> / <!-- VERIFIED --> per project group so they don't bleed across CHG blocks from different projects

Alternatives Considered

• Separate CC sessions per project — works but breaks the "single command center" workflow where one CC session manages all active work
• Separate task files — task.md + task-project2.md — requires hook changes to know about multiple files, and loses the unified view

Context

This comes up naturally when someone uses OnlyClaude (or any PACE-enabled repo) as a central hub to coordinate multiple projects simultaneously. The more projects tracked, the worse the interference gets.

[paceaitian]

这是一个设计问题，设计的本意是cc从项目文件夹启动，例如CD：Project-Alpha claude，paceflow使用纯正则脚本配合hook强制执行规定流程，使用claude code 环境变量current work dir来确认cwd路径，不涉及AI判断，无法在同一session里区分Project Alpha、Project Beta，且cc也无法在同一session区分mutl project（只有通过上下文判断），如果引入AI判断就破坏了hook100%强制执行的设计初衷，推荐不同项目不同project folder，不要共用session。