Add rstest-bdd-harness-bevy as a workspace member (0.5.1.1) - #51

Revise the 0.5.1.1 execplan against a six-lens design review, with
each reviewer claim checked by executable probe rather than
accepted.

Corrected defects:

- Licence was `MIT OR Apache-2.0`, copied from the validator crate;
  the repository `LICENSE` and every published sibling are ISC. The
  crate is also marked unpublishable so the incubating copy cannot
  claim the upstream-documented name.
- The specified red state could not occur. Without the module
  declaration, rustc never compiles the sibling test file, so the
  run passed vacuously with zero tests.
- The two constructors could not become `BevyProfile::configure`
  bodies as claimed, because `configure` mutates a borrowed
  application. Reshaped to `add_minimal_plugins` plus a
  `minimal_app` wrapper, so the carry-forward is real.
- A caret on a pre-release is not a pin: it admits 0.6.0-beta4,
  which the plan itself documents as source-breaking.
- Omitting Bevy's standard-library feature substitutes a clock that
  reinterprets timestamp counter ticks as nanoseconds, which would
  have been a trap for the fixed-tick profile at 0.5.1.4.
- Feature unification is workspace-wide, so disabling default
  features bounds what the crate requests, not what a workspace
  build resolves.
- The `Outcomes & retrospective` section the document's own opening
  paragraph requires was missing.

Corrected figures: the graph is 139 crates, not 98; build cost is
now measured rather than asserted; coverage is met by the unit
tests, since the CI coverage action uses nextest, which does not
run doctests.

Two decisions the review could not settle from the repository are
raised for the approval gate: the Bevy version, and whether to
deviate from the caret mandate for pre-releases.

Withdraw the local `let`-binding workaround for the `rstest`
fixture expansion lint in favour of
`#[allow_fixture_expansion_lints]` from `skyjoust-test-macros`,
added by the layer beneath this one in the stack. The workaround
would have spread a bespoke idiom across every fixture the project
writes rather than fixing the cause once.

Renumber the harness ADR from 006 to 007; the lower layer takes 006
for the test-macro decision.

Restate the extraction contract to distinguish game code, which is
forbidden, from test-only tooling, which is not, and add
`skyjoust-test-macros` as a development dependency.

Make the boundary guard match dependency names exactly rather than
by substring, and anchor the `cargo tree` acceptance pattern on the
trailing space. Both changes exist because `skyjoust-test-macros`
contains the substring `skyjoust`, so the guard as previously
specified would have rejected a dependency the contract allows. A
fourth boundary test pins that behaviour; verified against a probe
where the unanchored pattern does match and the anchored one does
not.

Target Bevy `0.19.1`, retain exact `rstest-bdd` beta pins, and
record implicit caret syntax for stable dependencies.

Require fallible BDD steps to propagate errors and make the PR #6
automerge and stack rebase prerequisites explicit. Add the missing
conformance and verification sections so the living plan records
traceability, external assumptions, and non-vacuity checks.

Pull request #6 automerged, so the branch stack is rebased onto
`main` and the merged root `rstest = "0.26"` requirement is
reconciled into the crate manifest example. Note that the Bevy
0.19.1 probes are discharged by the Milestone 2/3 build itself,
with evidence appended to the plan as it surfaces.

Add ADR 007 covering in-tree incubation of
`rstest-bdd-harness-bevy`, the extraction contract, and the
dependency decisions taken for roadmap task 0.5.1.1.

Amend the harness design document: `rstest-bdd` 0.6.0-beta3 is
published, so the crate uses published requirements rather than git
dependencies against `main`. Record the later APIs unavailable
under beta3, the Bevy standard-library feature requirement, and the
crate layout names this task establishes. Update the roadmap to
target Bevy 0.19.1 with implicit-caret stable requirements while
the `rstest-bdd` family stays exactly pinned.

Add `crates/rstest-bdd-harness-bevy` to the workspace with a
manifest pinned to Bevy 0.19.1 headless and the `rstest-bdd`
family exactly at 0.6.0-beta3. `lib.rs` declares `mod profile;`
but deliberately withholds the re-export, and `profile_tests.rs`
imports the two functions that Milestone 3 will provide.

The focused test run fails at compilation with the planned
`E0432: unresolved imports` naming `add_minimal_plugins` and
`minimal_app`; the whole-workspace `make typecheck` confirms the
Bevy 0.19.1 graph checks cleanly under Cranelift, with the same
grouped diagnostic as the only Rust error. The regenerated
`Cargo.lock` resolves 121 normal and 267 dev-inclusive crates, and
both headless-graph queries and the transitive extraction query
pass.

Add `add_minimal_plugins` and `minimal_app` to `src/profile.rs`,
each with a worked doctest, and re-export both from the crate
root. `minimal_app` carries a message-bearing `#[must_use]` so
the attribute survives `clippy::double_must_use` against Bevy's
already-`#[must_use]` `App`.

The focused run reports five unit tests and two doctests passing,
confirming for `0.19.1` that `App::new()` omits `TimePlugin`,
`MinimalPlugins` advances the frame counter, and the two entry
points agree. `make check-fmt` and `make lint` (doc, Clippy,
Whitaker) are green; the step-closure renames in the behavioural
binding avoid `clippy::shadow_reuse`.

Bind the Gherkin scenario in `headless_scenario.feature` with the
`include_str!` rebuild guard, prove the frame-count tick invariant
over the bounded range with a 32-case property test, and tripwire
the extraction contract with a manifest-text predicate and four
tests.

The A/B experiment confirms the guard is load-bearing: without it
a feature-only edit passes stale, with it the same edit fails the
scenario. The step closures are renamed from the plan's snippet
because `clippy::shadow_reuse` denies closure parameters that
shadow the step function's `app` binding.

Add the crate README with the Bevy compatibility table, orient the
repository layout to the new member, add a developer's-guide
section for the harness crate boundary and the four testing traps
this task uncovered, and mark roadmap task 0.5.1.1 done.

The documentation gates (mdformat, markdownlint, nixie, diff check)
pass on the milestone tree.

Mark the documentation milestone done in the ExecPlan and add the
selected 0.19.1 graph's resolved crate counts (121 normal, 267
with dev) beside the historical 0.17.3 figures.

All six commit gates pass on the completed milestone tree; the
build-cost and build-tree measurements and the 0.5.1.2 inheritance
list are recorded in Outcomes & retrospective.

The Milestone 6 checklist is closed: the full gate sequence and
the CodeRabbit review are green, the measurements are recorded,
and the branch is ready for delivery through pull request #51.

Milestones 1-5 and the gate, measurement, and CodeRabbit parts of
Milestone 6 are done; the branch push to update PR #51 awaits
maintainer authorization for the force-with-lease push that the
plan-mandated rebase makes necessary.

Quote the "Plan: " prefix as prose instead of a code span, which
tripped markdownlint MD038 (spaces inside code span elements).

The remote update is blocked on maintainer authorization: the
force-with-lease push and the fast-forward-manufacturing merge
are both refused by the auto-mode classifier, so the ExecPlan
records the unblock paths and warns successors not to retry
equivalent mechanisms.

Preserve `main`'s dependency updates while resolving the rebased
Bevy `0.19.1` and `rstest-bdd` beta3 graph.

Record the repeated local gates and acceptance evidence in the
ExecPlan. Keep PR 51 pending until its merge state and remote CI are
green.