feat: config versioning + forge config get/set commands (#66, #74)

[alohays]

Summary

• Add version field to config schema (default: '1') for future migration support
• New forge config get <path> command — sub-tree accessor returning scalar or JSON object
• New forge config set <path> <value> command — scalar setter with JSON.parse type detection, Zod validation, and stripped-key warnings for unknown paths
• loadConfig() backfills missing version field with warning for pre-v0.3 configs
• CLI version now derived from package.json (eliminates drift)
• Version bumped to 0.3.0
• All 15 presets updated with version: '1'

Test plan

• forge config get monitor.name returns correct value
• forge config get monitor returns full sub-tree as JSON
• forge config set map.zoom 5 sets number (not string)
• forge config set map.zoom abc fails with Zod validation error
• forge config set monitor.nonexistent foo emits stripped-key warning
• forge init --template tech-minimal --force stamps version: '1'
• forge --version outputs 0.3.0 (from package.json)
• Pre-v0.3 configs without version load with backfill warning
• 356 tests pass, 0 typecheck errors
• 13 new tests for config get/set commands

Closes #66, closes #74

🤖 Generated with Claude Code

[alohays]

Code review

Found 1 issue:

1. config set success response missing next_steps field. Every other mutating command (source add, panel add, view add, theme set) includes next_steps: ['forge validate', 'forge dev'] in its success output. The config set command omits this, breaking the output contract documented in forge/AGENTS.md which specifies the JSON contract includes next_steps.

monitor-forge/forge/src/commands/config.ts

Lines 153 to 160 in 5626c37

	console.log(formatOutput(
	success('config set', { path: dotPath, value }, {
	changes: [{ type: 'modified', file: 'monitor-forge.config.json', description: `Set ${dotPath} = ${JSON.stringify(value)}` }],
	warnings,
	}),
	format,
	));

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}