Getting Started: the openscap path needs a `profile` target variable the page never mentions

[trevor-vaughan]

Summary

The openscap scanning path requires the workspace target to carry a variables.profile
value (for example cis_server_l1). This is documented only in the provider's own
repository, never in the getting-started. Without it, generate has no profile to tailor
and the openscap path produces nothing.

Affected

• Page: content/docs/getting-started/_index.md (no variables: block shown in the
  init/scan walkthrough)
• Reference: complytime-providers/cmd/openscap-provider/docs/configuration.md
  ("profile | Yes | SSG profile short name")

Detail

To make scan target anything, the workspace target must include variables.profile. The
provider's configuration doc lists profile as required, but the getting-started's
walkthrough shows no variables: block at all. A working run was only possible by reading
the provider repo and hand-writing the target.

Expected

The getting-started shows a complete complytime.yaml, including the targets: block and
the required variables.profile, so the openscap example runs as written.

Suggested fix

Show a complete complytime.yaml in the getting-started for the openscap example,
including a targets: block with variables.profile (and, on CentOS Stream hosts, an
explicit variables.datastream — see the related provider datastream issue). This is best
delivered as the single worked example that also resolves the missing-policy-URL gap, so a
first-time reader can run the whole flow from one copy-pasteable config.

---

Related: #60, #62, complytime/complytime-providers#91

Issue created with the help of Claude Opus 4.6