# Separate site operations from portable benchmark guidance

The Java FIXBench README now describes the portable engine inputs, configuration,
planning commands, result artifacts and qualification gates. Its complete
526-line predecessor is preserved byte-for-byte under
`internal/bench/java/fixbench/README.md`, with a sealed original snapshot here:

- [Original Java guidance and historical measurements](evidence/benchmark-readme-boundary-20261003/java-fixbench-original.md)
- [Snapshot seal](evidence/benchmark-readme-boundary-20261003/SHA256SUMS)

The original notebook pointers, TLS staging details and historical measurements
remain available in that snapshot; their historical grades are unchanged.
Portable guidance links the maintained full-session and Stage 2 methods.

The two site-specific C++/Java smoke operations move from `bench/` to their
matching `internal/bench/` directories. They are deployment operations around
the existing generic drivers, which remain selected by the benchmark manifest.
Relocation updates their derived source paths. Their mutable output defaults
now follow `LIBHFT_BUILD_ROOT` and live outside Windows mirrors/shared `/tmp`;
explicit `FIXBENCH_RUN_ROOT` still wins. Both actual `--help` entrypoints pass
without contacting hosts. No queued capsule, root installer or runtime moves.

The Java matrix's default comparator and private smoke operation now select
`philadelphia-fast`, as requested for this campaign. The ordinary Philadelphia
engine remains separately registered for historical results and explicit use.
No historical row is relabelled or regraded.

All **66 focused checks and 11 subchecks** pass again, with zero skips,
including the 44 complete-archive Java checks. The source-comprehensiveness
gate also passes. This is configuration/document/operation verification;
there is no new engine compilation, physical run or report timing result.

Readiness selects **710 files (9.5 MB)**, with **258 scrub findings in
80 files**, **94 textual escapes** and **zero dead documentation links**.
The portable Java README has zero scrub findings. The remaining inventory and
engine/licence/report/release gates remain open.