# nobrainer-tech-flow 2.0.0 verification record

Source version: 2.0.0. Publication is a separate check against the public tag
and release archive; this document alone does not establish distribution.

## What is included

- One workflow entrypoint and 18 modules, including standard first-setup Auto Fine Tune.
- Read-only repository/client preflight, stable selection IDs and situational recommendations.
- Selected installation plus required entry/audit modules, client-specific personalization,
  idempotent readback and guarded rollback.
- Task-sized planning, SDD, wiki use, native-worker routing and integration contracts.
- Optional bounded Jev/Laya decision adapters, explicit data/call limits and fallback.
- Daily active-use version checking, browser preference guidance and safe worktree cleanup.

## Reproduce the repository checks

From the exact reviewed release checkout, run:

```sh
python3 scripts/validate_skills.py --suite
python3 -m unittest discover -s tests -q
```

The suite includes isolated Codex and Claude homes, partial selection and required
dependencies, multiple-client state, idempotence, preservation of later edits,
rollback, offline preflight, update responses, decision-adapter error/fallback
handling and worktree cleanup refusal/removal cases. It does not write the user's
actual client configuration. The public tests are executable evidence; older
internal review journals are not part of the current proof.

For a narrower setup check:

```sh
python3 -m unittest discover -s tests -p 'test_guided_onboarding.py' -v
python3 -m unittest discover -s tests -p 'test_personalization.py' -v
python3 -m unittest discover -s tests -p 'test_typed_decisions.py' -v
```

## Evidence limits

These checks establish local helper behavior and source contracts. They do not
prove that every client loads the workflow, that a requested model was honored,
that all hosts support parallel workers, or that live Jev/Laya inference improves
quality, latency or cost. Auto Fine Tune records unverified values as UNKNOWN or
UNMEASURED. Native tools, access and authorization remain host-dependent.

The website's automatically animated portal scenario is a scripted illustration.
Its worker states, console lines and verification steps are not a live run or a
benchmark. A real task must supply its own inspected artifacts and readback.

Before upgrading a real client, follow the migration guide, preserve its previous
instructions and verify the exact new entrypoint in a fresh client session.