# Integrate web-agent Project Control work

audience: AI coding agents first.

status: ACTIVE
task IDs: #1
source request: Owner said: “this is a work a web-agent made. integrate it and push to main”. Owner clarified goal: “complete integration push deploy”. Treat `/home/user/Projects/overdeck/temp-user/project-onboarding/overdeck-project-control-implementation/` as submitted implementation evidence, not trusted repository state.

## Outcome

Integrate only valid, current web-agent changes into Overdeck; fix conflicts or defects; verify affected surfaces; deploy owner-visible runtime; push completed work to `main`.

## Acceptance criteria

- Inventory package bytes, deletions, base assumptions, and verification receipts.
- Reconcile every proposed path against current `main`; NEVER overwrite newer work blindly.
- Apply only changes that remain correct and requested.
- Read mandatory scoped instructions before touching affected areas.
- Run required focused tests, typechecks, builds, and factory suite when factory machinery changes.
- Resolve every warning or failure.
- Independently review final diff.
- Deploy through canonical path and prove installed behavior.
- Push to `main`; record commit and proof.

## Preserved WIP

- Submitted package remains unchanged at `/home/user/Projects/overdeck/temp-user/project-onboarding/`.
- Shared checkout pre-existing changes remain untouched.
- Work executes only in `.worktrees/integrate-web-agent-project-control-2`, branch `wt/integrate-web-agent-project-control-2`, base `b6040af91`.

## Constraints

- Package reports collector, deck-ui, and web checks exited `127`; prior verification is incomplete and MUST NOT be trusted as green.
- Package spans web/UI, harness, monitor, buildbox, collector, and root project files; apply scoped project rules per path.
- NEVER use package `apply.sh` until its behavior and every target are reconciled against current main.
- Owner explicitly authorized complete integration, push, and deployment.

## Execution steps

1. Extract exact path inventory, package provenance, apply behavior, and captured failures.
2. Compare package final bytes with current `main`; classify additions, stale overwrites, deletions, and conflicts.
3. Read scoped instructions and relevant existing plans/specs for retained changes.
4. Integrate surgically; repair defects and update tests.
5. Run required focused and repository gates with zero ignored signals.
6. Run independent pre-ship review; fix confirmed findings; reverify.
7. Deploy and prove owner-visible behavior.
8. Commit, reconcile latest `origin/main`, push `main`, and confirm remote receipt.

## Current receipt

- 2026-08-13: task #1 active in main session.
- Guarded worktree `.worktrees/integrate-web-agent-project-control-2` confirmed on branch `wt/integrate-web-agent-project-control-2`, base `b6040af91`.
- Package payload is a broad 485-path checkout snapshot: 430 bytes already equal current main, 49 are stale/different, 2 are unrelated new cursor-orchestrator files, and 4 inventory entries are directories/symlinks without payload bytes.
- Package verification names Project Control source files but neither extracted payload nor ZIP contains them. Current `main` already contains those files through landed commit ancestry; package `apply.sh` would overwrite 49 newer paths and MUST NOT run.
- Current source verification: deck-ui 76 files / 402 tests pass; deck-ui typecheck passes; web build completes including `/projects`; web typecheck reports 0 errors, 0 warnings, 0 hints; permission queue 12 tests pass.
- One dependency-install warning occurred only during concurrent first-run installation (`tsc` bin race). Sequential rerun reused the completed install and all gates passed cleanly; no source or dependency defect remains.
- Independent review found one blocker: bot mention history accepted unbounded time ranges and prompt history. TDD repair now caps time ranges to 52 weeks, database reads to 250 newest messages, and prompt history to 24 KiB while retaining newest fitting messages. Regression tests 2/2 and bot typecheck pass.
- Local deployment completed at source `bbca2df8`; web release reused the matching built release and reports active at `http://127.0.0.1:31337`. Deployment also reported pre-existing uncommitted shim copies in other worktrees; those are unrelated preserved WIP and were not modified.

## Next executable action

Review the final repair diff, commit it with the durable receipt, deploy the repair, reconcile latest `origin/main`, push `main`, and confirm remote/runtime receipt.
