feat(vitess): implement vitess_tasks for VSchema progress tracking

[aparajon]

VSchema changes were invisible during deploy progress — the TUI only showed DDL table entries from SHOW VITESS_MIGRATIONS. VSchema updates are metadata-only operations tracked by PlanetScale's deploy state machine, not Vitess OnlineDDL.

• Track which keyspaces have VSchema changes in apply metadata
• Synthesize VSchema table entries in the engine Progress response with state derived from the deploy request deployment state
• Pass synthetic VSchema entries through the LocalClient proto conversion so they reach the CLI
• Add shared VSchemaTablePrefix constant used by both the engine and CLI for consistent detection
• Fix double-space typo in "Validating deploy request" TUI message

[Copilot]

Pull request overview

This PR improves deploy-progress visibility for PlanetScale/Vitess applies by surfacing VSchema-only work (which doesn’t show up in SHOW VITESS_MIGRATIONS) as synthetic “table” progress entries, and fixes a minor TUI formatting typo.

Changes:

• Track keyspaces with VSchema changes in PlanetScale engine apply metadata and synthesize VSchema progress rows during Engine.Progress.
• Pass synthetic VSchema progress rows through the LocalClient’s proto response so they reach CLI/TUI consumers.
• Standardize VSchema task detection via a shared engine.VSchemaTablePrefix constant and fix a double-space typo in the TUI message.

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
pkg/tern/local_client.go	Appends synthetic VSchema progress rows from the engine into the proto ProgressResponse.
pkg/engine/planetscale/planetscale.go	Persists VSchema keyspaces in metadata and synthesizes VSchema “table” progress rows from deploy request state.
pkg/engine/planetscale/planetscale_test.go	Adds a metadata round-trip test for the new VSchemaKeyspaces field.
pkg/engine/engine.go	Introduces shared VSchemaTablePrefix constant for consumers to detect VSchema tasks.
pkg/cmd/commands/watch_tui_view.go	Fixes a double-space typo in the “Validating deploy request” line.
pkg/cmd/commands/apply.go	Updates VSchema task detection to use the shared prefix constant.

Comments suppressed due to low confidence (1)

pkg/engine/planetscale/planetscale.go:1804

• The new VSchema progress synthesis branch (deploy state → vschema table State mapping and table entry creation) is not covered by tests. Consider adding unit tests that assert (1) a VSchemaKeyspaces metadata value results in synthetic table rows in Progress, and (2) key deploy states map to the expected task states (pending/running/completed/failed/stopped).

	// Synthesize VSchema table entries. VSchema changes don't appear in
	// SHOW VITESS_MIGRATIONS — they're tracked by PlanetScale's deploy state
	// machine. Derive VSchema task state from the DR deployment state.
	if len(meta.VSchemaKeyspaces) > 0 {
		vsState := "pending"
		switch dr.DeploymentState {
		case deployState.InProgressVSchema:
			vsState = "running"
		case deployState.InProgress, deployState.Queued, deployState.Submitting:
			vsState = "pending"
		case deployState.Complete, deployState.CompletePendingRevert,
			deployState.InProgressCutover, deployState.PendingCutover:
			vsState = "complete"
		case deployState.Error, deployState.CompleteError, deployState.Failed:
			vsState = "failed"
		case deployState.CompleteCancel, deployState.Cancelled, deployState.InProgressCancel:
			vsState = "stopped"
		}
		for _, ks := range meta.VSchemaKeyspaces {
			result.Tables = append(result.Tables, engine.TableProgress{
				Table:     engine.VSchemaTablePrefix + ks,
				Namespace: ks,
				State:     vsState,
			})
		}
	}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.