sparq:config

To edit sparq.config.json safely, use an interactive configuration editor that validates changes against the schema and previews diffs before applying safe writes. This non-destructive workflow prevents broken integrations.

Interactive configuration validation checks sparq.config.json against the schema during guided edits. It enforces YAML frontmatter metadata rules and ensures settings like Jira project keys or checkpoint levels are structurally correct before saving.

Changing Jira project keys requires opening the SparQ configuration file in the interactive editor. The guided workflow lets you adjust integration settings, validates the new keys against the schema, and applies the change via a safe write.

Yes, the SparQ interactive editor provides non-destructive edits by generating change diff previews before writing. You can review the exact modifications to sparq.config.json and confirm the safe write to apply them.

Configuration issues after adjusting checkpoint levels often stem from schema validation failures. The interactive editor diagnoses these config issues by validating sparq.config.json metadata and highlighting errors before applying safe writes.

No, the SparQ interactive configuration editor operates without external dependencies. It independently handles schema validation, change diff previews, and safe writes directly to the sparq.config.json file.