Decouple dependency automation and Cursor files from the quality include slice

[jabelic]

Goal

Make the first quality-focused pilot path small and reviewable by separating lint/format baseline selection from dependency-automation and Cursor-specific files.

Background

• During the pilot validation in Pilot the base quality preset on i18n-at and document adoption gaps #2, standards diff and standards apply --dry-run against Jabelic-Works/i18n-at with --include quality proposed 5 creates: .cursor/commands/quality-check.md, .oxfmtrc.json, .oxlintrc.json, eslint.config.mjs, and renovate.json.
• The pilot is meant to validate a safe adoption path before applying anything to a real repository.
• The current quality slice mixes lint/format baseline files with dependency automation and Cursor-only files.
• i18n-at already uses Dependabot, so pulling renovate.json into the first quality pilot adds policy noise that is unrelated to the baseline lint/format validation.

Scope

• Refine preset tags, include behavior, or preset structure so lint/format baseline files can be selected without also selecting dependency-automation files.
• Decide whether Cursor-specific helper files should stay in the same path or move behind a more explicit selector.
• Update CLI help, tests, and/or README examples so the intended minimal pilot path is obvious.

Out of Scope

• Designing full stack-specific presets.
• Migrating target repositories from Dependabot to Renovate.
• Expanding the pilot into a broad editor-automation rollout.

Acceptance Criteria

• There is a documented way to select a lint/format baseline without also selecting Renovate.
• Cursor-only files are either split from that path or explicitly documented as an intentional part of it.
• diff and apply --dry-run against Jabelic-Works/i18n-at or an equivalent pilot target can produce a smaller non-dependency validation plan.

PR Plan

• 1 issue = 1 PR.
• Keep the change focused on preset tagging/include behavior, its tests, and the minimal docs/help updates needed to support the pilot.

Proposed Plan

1. Review the current base preset tags and decide whether quality should remain broad or be narrowed.
2. Adjust preset tags and/or include semantics so a dependency-free quality pilot is possible.
3. Update tests to lock the intended selection behavior.
4. Update CLI help or README examples to show the recommended pilot command.
5. Re-run the pilot validation from Pilot the base quality preset on i18n-at and document adoption gaps #2 and confirm the smaller output.

Notes

• Tracked by Pilot the base quality preset on i18n-at and document adoption gaps #2.
• This issue is about slice design, not about applying changes to i18n-at yet.