fix(agents): document exact lh CLI flags in every agent profile

Every agent's PROCEDURE/OUTPUTS referenced lh subcommands vaguely (e.g.
'Run lh run event', 'lh memory get --shard failures'), forcing models to
guess flags at runtime instead of following the profile. Two real bugs
found this way:

- 'lh memory get --shard X' silently ignores --shard (it's a positional
  arg on get, not a flag) and returns the whole INDEX.md instead of the
  targeted shard. Fixed to 'lh memory get X' everywhere.
- lh run event/lane create calls had no required --type/--status/--id/
  --kind/--scope documented, so agents had to trial-and-error discover
  them. Added full, exact invocation syntax inline for every command
  each agent actually issues (run event, lane create, memory get/put,
  host --strategy, graph).

.github/agents/conductor.agent.md

@@ -16,7 +16,7 @@ Run the full lean harness pipeline. Edit no product files.
 1. Run `lh doctor`.
 2. If it reports `config not initialised`, run `lh init --yes` (non-interactive defaults), then run `lh doctor` again.
 3. Do not proceed past a `lh doctor` failure you cannot self-heal (for example missing `verify.commands`); report the exact failing check and stop.
-4. Run `lh host`.
+4. Run `lh host --strategy` (prints only the orchestration-strategy text; drop `--strategy` to also see the detection table, or add `--json` for structured output).
 5. Read the printed host strategy before any other action.
 6. If the strategy permits parallel lanes, use host fan-out.
 7. If the strategy says sequential, run every lane one at a time.
@@ -39,7 +39,7 @@ Run the full lean harness pipeline. Edit no product files.
 24. Re-plan at every checkpoint.
 25. Spawn, kill, merge, or re-scope lanes only through updated `plan.dag.json` and `lh lane` commands.
 26. For read lanes, run `scout` on the shared checkout.
-27. For write lanes, run `lh lane create` before any builder starts.
+27. For write lanes, run `lh lane create --id <laneId> --title "<text>" --kind write --scope <glob1,glob2> [--depends-on <laneId1,laneId2>] [--acceptance AC-001,AC-002] --run-id <runId>` before any builder starts.
 28. Assign each builder exactly one lane and one worktree.
 29. Give each builder its declared scope globs and acceptance ids.
 30. Run builder and verifier in the Ralph loop.