# Task: Integrate project-wide Project Scaffold activation

## Identity

- Task ID: 20260905-project-plugin-scope-integration-4d8a2c71
- Mode: Integration
- Branch: main
- Worktree: D:\Datas\OthersProjects\makelore
- Base commit: d642d7607c26dee01ef65b4e70dd756465dea16a
- Owner: codex-root
- Status: Ready for Integration

## Scope

- Integrate reviewed source commit `300ac89a81409440aac84ff45b1d9ca2fa186629`
  onto local client `main` from exact base
  `d642d7607c26dee01ef65b4e70dd756465dea16a`.
- Promote the accepted Project Scaffold activation exception into canonical project
  memory: Account acquisition and project enablement remain required, but explicit
  partner assignment is not; all parent Agents in the enabled project receive the
  Skill and child Agents remain empty.
- Preserve every other Plugin's assignment behavior and the three pre-existing
  untracked task records in the root worktree byte-for-byte.

## Intent And Constraints

- Concurrent Task Gate: Passed. The completed prior Integration owner was released
  only after confirming the root had no tracked changes and exactly the three
  previously adopted untracked task records. This task then acquired `main` from the
  exact base using `--adopt-existing`; no active task owns the same product paths or
  semantics.
- Planning Gate: Passed after loading the entry memory, current state, decision index,
  ADR-008, architecture overview/module map/data flow, business rules, success
  criteria, glossary, evidence, reflection, commitments, stale items, the source task
  record, and the prior Integration record.
- Project Context Loaded:
  - Positioning: MakeLore Code uses Electron Main as the Plugin/runtime authority;
    Renderer pages project state and issue existing commands rather than owning a
    second lifecycle model.
  - Current state: Project Scaffold is a code-owned bundled Skill delivered with the
    client, but the prior effective resolver still required Agent assignment after
    Account acquisition and project enablement.
  - Applicable decision: the user's explicit 2026-09-05 decision amends only
    `makelore.project-scaffold` to be project-wide. It does not remove assignment from
    Game Resource, Data Service, local packages, or other Marketplace Plugins.
  - Architecture boundary: parent workers receive the Scaffold Skill from the
    Main-owned effective resolver; child workers remain empty and running generations
    stay frozen until their normal replacement/settlement boundary.
  - Known risk: updating only the UI would leave runtime materialization blocked;
    generalizing the exception would silently change unrelated Plugin authorization.
  - Relevant commitment: source/build verification does not prove that an already
    installed client has been rebuilt and replaced; that remains a release smoke step.
- Apply the source with `git cherry-pick --no-commit`, adopt its exact task record before
  committing, and verify the source/product trees. This follows the recorded
  Integration reflection and avoids committing an unowned source record.
- Do not push, publish, package, deploy, reset, stash, clean, or modify the three
  pre-existing untracked task records.

## Outcome

- Applied reviewed source `300ac89a81409440aac84ff45b1d9ca2fa186629`
  from its exact parent with `git cherry-pick --no-commit`, adopted the unchanged
  source task record, and committed the product change on local `main` as
  `6710527e8f7150a6c4997d566a380454e33f455e`.
- Confirmed the source and product commit trees are identical at
  `7391af053cfc30bd4100cc24590c6560297affdd`; the integration introduced no conflict
  resolution or behavioral delta.
- Promoted the accepted project-wide activation rule into ADR-008, the decision index,
  system overview, module map, data flow, business rules, current state, evidence, and
  release commitment. General Plugin assignment remains intact; only Project Scaffold
  has no assignment gate.
- Removed the duplicate source task record only from the `main` documentation
  checkpoint. The source branch and its task record remain unchanged and auditable.
- Preserved the three pre-existing untracked task records byte-for-byte and did not
  stage, commit, delete, move, or otherwise modify them.

## Verification

- Integration-specific checks:
  - source parent equals integration base `d642d7607c26dee01ef65b4e70dd756465dea16a`;
  - staged source task record hash matched the source commit before product commit;
  - source/product Git tree equality passed at
    `7391af053cfc30bd4100cc24590c6560297affdd`;
  - `git diff --check` passed for both the product patch and documentation checkpoint;
  - `check_project_docs.py` passed.
- Adopted reviewed source evidence because the root checkout has no installed
  `node_modules`: TDD RED produced 3 expected failures/42 passes; focused GREEN passed
  45 tests; adjacent Plugin/runtime regression passed 87 tests; typecheck passed; full
  lint had 0 errors/5 unchanged warnings; pressure passed 1/1; all Vite targets passed.
- Source full regular unit run passed 1,888 tests with 2 skips and one unrelated
  two-second Pi real-process timing miss; that exact file passed 6/6 in isolation.
- Task-aware documentation drift and task-context completion are required after the
  documentation checkpoint commit and are recorded by the final Integration gate.

## Follow-ups

- Rebuild and install a client from this `main`, then smoke-test an Account-acquired,
  project-enabled, unassigned Project Scaffold with two parent Agents and one child:
  both parents must see the Skill and the child must remain empty. This is a release
  acceptance step, not a blocker for the local source merge.

## Promotion Candidates

- None. The feature task's confirmed semantic promotion is incorporated in this
  Integration checkpoint.