# Phase 172 locally actionable completion evidence

Date: 2026-07-15

## Completion audit

The phase checklist contains 253 feature requirements across 28 focused Neith
packages plus 15 validation requirements. This audit found one locally missing
package and two validation exclusions whose comments no longer matched the
repository state.

`libs/neith/dcc-file-browser` now provides the complete Phase 172.28 model:

- `entry` owns file typing, case-insensitive filters, directory-first ordering,
  preview metadata, stable thumbnail keys, regeneration revisions, and cache
  invalidation;
- `paths` owns bounded/deduplicated recents, bookmarks, system places, lexical
  relative/absolute conversion (including external `..` assets), an opt-in
  project-boundary guard, base-move target preservation, and subtree-preserving
  remap-on-move;
- `library` owns active/writable library roots and deterministic missing-file
  discovery, candidate ranking, and relinking;
- `datablocks` owns typed blend-file block browsing, link/append drag-drop,
  ordinary file import, and binary-safe pack/unpack with overwrite control and
  path-traversal rejection.

The Phase 172.29 suite now links the actual Phase-138 `neith-pathtracer`, MRQ,
texture-paint, and golden-image comparison crates. The MRQ gate accumulates a
real Phase-138 transport sample in reference mode and compares the resolved
image. The paint gate executes the production brush against the checked-in
`texture_paint_reference.ppm` image. These gates no longer rely on comments,
enum selection alone, or candidate-to-itself comparisons.

## Requirement-to-evidence matrix

| Requirements                  | Authoritative evidence               | Automated proof |
| ----------------------------- | ------------------------------------ | --------------: |
| 172.28.1, .28.9               | `dcc-file-browser/src/entry.rs`      |         2 tests |
| 172.28.2, .28.6, .28.7        | `dcc-file-browser/src/paths.rs`      |         3 tests |
| 172.28.5, .28.8               | `dcc-file-browser/src/library.rs`    |         2 tests |
| 172.28.3, .28.4, .28.10       | `dcc-file-browser/src/datablocks.rs` |         2 tests |
| 172.29.1–.29.14 except .29.15 | `parity172-testing`                  |        14 tests |

The earlier checked feature packages remain covered by their package-local test
suites and the cross-crate validation suite. The current audit specifically
reopened every unchecked item, rather than treating those existing checkmarks as
proof for the missing Phase 172.28 package.

## Open external acceptance gate

Only **172.29.15** remains unchecked. It asks for a _full Phase 27 shoot_ using
the combined Phase 171+172 stack. This is not a repository-local software gate:
Phase 27 still explicitly lacks its production drafts and shooting scripts
(27.22.2.13–.14), production designer and schedule (27.22.3.7, .15), virtual
production pipeline and capture (27.22.3.16, 27.22.4.13), pickup/B-roll shoots
(27.22.4.10–.11), and final premium-production verification (27.28.4.11).
Checking 172.29.15 without those real production artifacts would fabricate
dogfood evidence. The locally executable stack is covered by 172.29.1–.14; the
remaining acceptance requires the Phase-27 production to occur.

## Verification

The canonical gates for both changed Rust workspaces are:

```bash
cargo fmt --manifest-path <manifest> -- --check
cargo clippy --manifest-path <manifest> --all-targets -- -D warnings
cargo test --manifest-path <manifest> --all-targets
cargo build --release --manifest-path <manifest> --all-targets
```

All four commands passed for both manifests: 10 file-browser tests and 14
cross-crate parity tests passed with zero failures or ignored cases. The focused
Nx `@neith/dcc-file-browser:lint` target and the package-manager test target
also passed, and the workspace lockfile contains the new package importer.

Verification was serialized on a 15 GiB host with 31 GiB swap and 11 GiB
available memory. A small BFF development watcher was active, so no broad Nx
gate was run. No browser/PWA/mobile implementation changed; the file-browser
package is a headless shared DCC model, so Playwright and mobile automation are
not applicable.
