status.yaml

phase: phase295_performance_platform_reach
status: closeout_completed
started_at: "2026-03-06"
completed_at: "2026-03-07"

spec_files:
  - spec/phase2.95/README.md
  - spec/phase2.95/SPEC_PERF_SYNC.md
  - spec/phase2.95/SPEC_REMOVE_ALL.md
  - spec/phase2.95/SPEC_WINDOWS_JUNCTION.md
  - spec/phase2.95/SPEC_DOCKER_BIND.md
  - spec/phase2.95/SPEC_INSTALL_SCRIPT.md
  - spec/phase2.95/SPEC_TEST_MATRIX.md
  - spec/phase2.95/SPEC_TRACEABILITY.md

requirement_ids:
  perf_sync: PSY-001 ~ PSY-008
  remove_all: RMA-001 ~ RMA-004
  windows_junction: WJN-001 ~ WJN-006
  docker_bind: DBM-001 ~ DBM-007
  install_script: ISC-001 ~ ISC-007

test_scenarios: TM-P295-001 ~ TM-P295-048

batches:
  batch1:
    name: "Install Scripts"
    work_packages: [WP-5]
    requirements: [ISC-001, ISC-002, ISC-003, ISC-004, ISC-005, ISC-006, ISC-007]
    status: completed
  batch2:
    name: "Remove All Symbol"
    work_packages: [WP-2]
    requirements: [RMA-001, RMA-002, RMA-003, RMA-004]
    status: completed
  batch3:
    name: "Windows Junction Fallback"
    work_packages: [WP-3]
    requirements: [WJN-001, WJN-002, WJN-003, WJN-004, WJN-005, WJN-006]
    status: completed
  batch4:
    name: "Performance Part 1: Repo-Level Cache"
    work_packages: [WP-1-pt1]
    requirements: [PSY-001, PSY-002, PSY-003, PSY-006, PSY-007]
    status: completed
  batch5:
    name: "Performance Part 2: Batch Sync + Migration"
    work_packages: [WP-1-pt2]
    requirements: [PSY-004, PSY-005, PSY-006, PSY-008]
    status: completed
  batch6:
    name: "Docker Bind Mount"
    work_packages: [WP-4]
    requirements: [DBM-001, DBM-002, DBM-003, DBM-004, DBM-005, DBM-006, DBM-007]
    status: completed
  batch7:
    name: "Regression + Closeout"
    work_packages: []
    requirements: []
    status: completed

builder_progress:
  batch_1_install_scripts:
    status: completed
    started_at: "2026-03-06"
    completed_at: "2026-03-06"
    requirements: ISC-001, ISC-002, ISC-003, ISC-004, ISC-005, ISC-006, ISC-007
    scenarios: TM-P295-001, TM-P295-002, TM-P295-003, TM-P295-004, TM-P295-005, TM-P295-006, TM-P295-007, TM-P295-008, TM-P295-009
    notes:
      - added root-level `install.sh` and `install.ps1` installers with release version resolution, target detection, SHA-256 verification, install-dir support, git warning, and post-install `--version` verification
      - added deterministic installer test hooks (`EDEN_SKILLS_RELEASE_API_URL`, `EDEN_SKILLS_RELEASE_BASE_URL`, `EDEN_SKILLS_TEST_UNAME_S`, `EDEN_SKILLS_TEST_UNAME_M`) so script behavior can be validated without live network downloads
      - added `cargo-binstall` metadata to `crates/eden-skills-cli/Cargo.toml` and updated `README.md` plus `docs/01-quickstart.md` to advertise the new one-line install flow
      - added `crates/eden-skills-cli/tests/install_script_tests.rs` with Batch 1 coverage for target mapping, checksum failures, PATH hinting, version pinning, PowerShell contract snippets, and binstall metadata
      - live `cargo binstall` end-to-end download was not executed in this environment; the release URL contract is asserted through manifest metadata tests instead
    quality_gate:
      fmt_check: passed
      clippy_workspace_deny_warnings: passed
      test_workspace: passed
      current_test_inventory: 349
  batch_2_remove_all_symbol:
    status: completed
    started_at: "2026-03-06"
    completed_at: "2026-03-06"
    requirements: RMA-001, RMA-002, RMA-003, RMA-004
    scenarios: TM-P295-010, TM-P295-011, TM-P295-012, TM-P295-013, TM-P295-014, TM-P295-015
    notes:
      - updated `crates/eden-skills-cli/src/commands/remove.rs` so interactive `remove` recognizes `*` as a wildcard that expands to all configured skill IDs in config order
      - reject mixed wildcard selections like `* 2 foo` with a dedicated invalid-arguments error while keeping positional `remove <id>...` semantics unchanged
      - strengthened wildcard confirmation flow with warning-style wording, preserved `-y/--yes` skip behavior, and updated the interactive prompt hint to advertise `* for all`
      - expanded `crates/eden-skills-cli/tests/remove_enhanced_tests.rs` with TM-P295-010 through TM-P295-015 coverage and added focused unit tests in `crates/eden-skills-cli/src/commands/remove.rs` for wildcard parsing and prompt helpers
    quality_gate:
      fmt_check: passed
      clippy_workspace_deny_warnings: passed
      test_workspace: passed
      current_test_inventory: 358
  batch_3_windows_junction_fallback:
    status: completed
    started_at: "2026-03-06"
    completed_at: "2026-03-06"
    requirements: WJN-001, WJN-002, WJN-003, WJN-004, WJN-005, WJN-006
    scenarios: TM-P295-016, TM-P295-017, TM-P295-018, TM-P295-019, TM-P295-020, TM-P295-021, TM-P295-022, TM-P295-023
    notes:
      - added `junction = "1"` as a Windows-only dependency in both `crates/eden-skills-core/Cargo.toml` and `crates/eden-skills-cli/Cargo.toml`
      - extended `crates/eden-skills-cli/src/commands/install.rs` with the three-level Windows fallback chain, a junction capability probe, transparent `symlink` mode recording, and test hooks for forced symlink/junction support plus probe logging
      - updated `crates/eden-skills-core/src/adapter.rs` and `crates/eden-skills-cli/src/commands/common.rs` so directory symlink creation falls back to NTFS junctions on Windows permission denial and existing junctions are deleted safely before reinstall
      - updated `crates/eden-skills-core/src/plan.rs`, `crates/eden-skills-core/src/verify.rs`, and the local-source install path in `crates/eden-skills-cli/src/commands/install.rs` to treat junctions as valid symlink-mode targets
      - added `crates/eden-skills-cli/tests/junction_tests.rs` and `crates/eden-skills-core/tests/junction_tests.rs` for TM-P295-016 through TM-P295-023 coverage, and refreshed the legacy hardcopy fallback regression in `crates/eden-skills-cli/tests/install_url_tests.rs`
    quality_gate:
      fmt_check: passed
      clippy_workspace_deny_warnings: passed
      test_workspace: passed
      current_test_inventory: 363
  batch_4_perf_part1_repo_cache:
    status: completed
    started_at: "2026-03-06"
    completed_at: "2026-03-06"
    requirements: PSY-001, PSY-002, PSY-003, PSY-006 (partial), PSY-007
    scenarios: TM-P295-024, TM-P295-025, TM-P295-026, TM-P295-027, TM-P295-028, TM-P295-029, TM-P295-030, TM-P295-035, TM-P295-038
    notes:
      - refactored `crates/eden-skills-core/src/source.rs` to derive repo cache keys from normalized repo URLs plus sanitized refs, group remote sync work by `(repo_url, ref)`, and store shared checkouts under `storage_root/.repos/{cache_key}`
      - added `resolve_skill_storage_root()` and `resolve_skill_source_path()` so repo-cache paths are used consistently by `plan.rs`, `verify.rs`, `safety.rs`, `reconcile.rs`, and `update.rs`, while local source installs continue using per-skill staging under `storage_root/{skill_id}`
      - updated `crates/eden-skills-cli/src/commands/install.rs` to preserve the remote discovery checkout, move it into the repo cache when available, and fall back to a fresh cache clone when the move cannot be completed
      - added `crates/eden-skills-core/tests/perf_sync_tests.rs` and `crates/eden-skills-cli/tests/perf_sync_tests.rs` for TM-P295-024 through TM-P295-030, TM-P295-035, and TM-P295-038, then migrated affected legacy tests to the new repo-cache layout
      - post-Batch-4 Windows CI follow-up: added the cross-platform `EDEN_SKILLS_TEST_GIT_CLONE_LOG` hook in `crates/eden-skills-core/src/source.rs` and `crates/eden-skills-cli/src/commands/install.rs`, and updated `crates/eden-skills-cli/tests/perf_sync_tests.rs` to stop relying on PATH/git.cmd interception for clone counting on Windows
      - post-Batch-4 Windows CI follow-up: updated `crates/eden-skills-core/tests/junction_tests.rs` to build its source fixture from `resolve_skill_source_path()` so the WJN-004 junction noop assertion follows the repo-cache layout introduced in Batch 4
    quality_gate:
      fmt_check: passed
      clippy_workspace_deny_warnings: passed
      test_workspace: passed
      windows_check_x86_64_pc_windows_msvc: passed
      current_test_inventory: 375
  batch_5_perf_part2_batch_sync_and_fast_path:
    status: completed
    started_at: "2026-03-06"
    completed_at: "2026-03-06"
    requirements: PSY-004, PSY-005, PSY-006, PSY-008
    scenarios: TM-P295-031, TM-P295-032, TM-P295-033, TM-P295-034, TM-P295-036, TM-P295-037
    notes:
      - updated `crates/eden-skills-cli/src/commands/install.rs` so remote URL-mode installs batch the selected config into a single `sync_sources_async()` call before sequential install-plan execution, while preserving the existing TTY/non-TTY sync progress output contract
      - extended `crates/eden-skills-core/src/source.rs` with repo-level skip support for grouped sync tasks, and updated `crates/eden-skills-cli/src/commands/reconcile.rs` so `apply` marks unchanged repo-cache keys as skipped without network fetch while `repair` continues to sync every repo
      - completed the remaining repo-cache migration coverage by adding `TM-P295-034` in `crates/eden-skills-cli/tests/update_ext_tests.rs` and `TM-P295-036` in `crates/eden-skills-cli/tests/doctor_copy.rs`, proving `update` and `doctor` read from repo-cache-backed sources even when legacy per-skill paths are absent or broken
      - added the `mtime + size` copy fast path in `crates/eden-skills-core/src/plan.rs`, plus `TM-P295-037` in `crates/eden-skills-core/tests/plan_copy_edge_tests.rs`, and adjusted older copy-plan fixtures so they continue to exercise unreadable-file conflict behavior outside the new fast-path
      - added `TM-P295-031`, `TM-P295-032`, and `TM-P295-033` in `crates/eden-skills-cli/tests/perf_sync_tests.rs` to verify batched install fetches, apply skip summaries, and repair’s no-skip behavior
      - post-Batch-5 Windows CI follow-up: replaced the PATH/git wrapper fetch counter in `crates/eden-skills-cli/tests/perf_sync_tests.rs` with an explicit `EDEN_SKILLS_TEST_GIT_FETCH_LOG` hook in `crates/eden-skills-core/src/source.rs`, matching the earlier clone-count stabilization pattern from Batch 4
    quality_gate:
      fmt_check: passed
      clippy_workspace_deny_warnings: passed
      test_workspace: passed
      windows_check_x86_64_pc_windows_msvc: passed
      current_test_inventory: 381
  batch_6_docker_bind_mount_and_agent_auto_detection:
    status: completed
    started_at: "2026-03-06"
    completed_at: "2026-03-06"
    requirements: DBM-001, DBM-002, DBM-003, DBM-004, DBM-005, DBM-006, DBM-007
    scenarios: TM-P295-039, TM-P295-040, TM-P295-041, TM-P295-042, TM-P295-043, TM-P295-044, TM-P295-045, TM-P295-046, TM-P295-047, TM-P295-048
    notes:
      - extended `crates/eden-skills-core/src/adapter.rs` with `docker inspect` bind-mount parsing, host-path mapping, container HOME resolution, container agent auto-detection, and bind-mount-aware install/uninstall branching
      - updated `crates/eden-skills-cli/src/commands/install.rs` so `--target docker:<container>` now auto-detects agents inside the container, preserves existing manual Docker targets when no explicit docker target is requested, routes Docker installs through `DockerAdapter`, and prints a bind-mount tip after `docker cp` fallback
      - added the new `eden-skills docker mount-hint <container>` command in `crates/eden-skills-cli/src/commands/docker_cmd.rs` and wired it through `crates/eden-skills-cli/src/lib.rs`
      - updated `crates/eden-skills-cli/src/commands/diagnose.rs` to emit `DOCKER_NO_BIND_MOUNT` info findings for running Docker targets that lack writable bind mounts
      - refreshed `docs/04-docker-targets.md` to document container agent auto-detection, bind-mount-aware install behavior, `docker mount-hint`, and the new Docker doctor guidance
      - added Batch 6 coverage in `crates/eden-skills-core/tests/adapter_tests.rs`, `crates/eden-skills-cli/tests/docker_bind_tests.rs`, `crates/eden-skills-cli/tests/install_agent_detect_tests.rs`, and `crates/eden-skills-cli/tests/phase2_doctor.rs`
    quality_gate:
      fmt_check: passed
      clippy_workspace_deny_warnings: passed
      test_workspace: passed
      windows_check_x86_64_pc_windows_msvc: passed
      current_test_inventory: 392
  batch_7_regression_closeout:
    status: completed
    started_at: "2026-03-07"
    completed_at: "2026-03-07"
    requirements: closeout_regression
    scenarios: TM-P295-001~TM-P295-048 (regression replay)
    notes:
      - "reran the full Phase 2.95 closeout quality gate: `cargo fmt --all -- --check`, `cargo clippy --workspace -- -D warnings`, `cargo test --workspace --all-targets`, and `cargo check --workspace --all-targets --target x86_64-pc-windows-msvc`"
      - "confirmed regression stability at 392 passing automated tests, with existing JSON contract suites still green and no exit-code semantic drift for `0/1/2/3`"
      - "confirmed `rg '\\x1b\\[' crates/` returns zero matches, so no hardcoded ANSI escape sequences remain in source"
      - "synced `spec/phase2.95/SPEC_TRACEABILITY.md`, `trace/phase2.95/tracker.md`, `README.md`, `spec/README.md`, `STATUS.yaml`, `EXECUTION_TRACKER.md`, and `AGENTS.md` to the Phase 2.95 closeout state"
      - "removed cross-target warning noise in `crates/eden-skills-cli/tests/install_script_tests.rs` by gating Unix-only imports and helpers behind `cfg(not(windows))`"
      - "post-closeout follow-up: `install.sh` now appends the PATH export to the shell-selected rc file when needed, avoids duplicate entries, and prints reload guidance; related docs and installer tests were updated"
    quality_gate:
      fmt_check: passed
      clippy_workspace_deny_warnings: passed
      test_workspace_all_targets: passed
      windows_check_x86_64_pc_windows_msvc: passed
      no_hardcoded_ansi_escape_in_source: passed
      json_contract_regression: passed
      exit_code_semantics_0_1_2_3: passed
      current_test_inventory: 393