fix: accept boolean and number types for manifest default field

[olamide226]

Summary

• Widens the default field in .rep.yaml manifest schema from string to string | number | boolean
• Users can now write default: false instead of default: "false" for boolean variables (and default: 3 for numbers)
• Fully backward compatible — existing string defaults are unaffected

Changes

• schema/rep-manifest.schema.json + cli/schema/rep-manifest.schema.json — updated JSON schema type
• cli/src/utils/manifest.ts — widened TypeScript interface type
• cli/src/utils/__tests__/manifest.test.ts — added tests for boolean and number defaults

Test plan

• All 76 existing CLI tests pass
• New tests verify default: false (boolean) and default: 3 (number) validate successfully
• Manually test with rep validate against a .rep.yaml using default: false

[Copilot]

Pull request overview

This PR expands the REP manifest (.rep.yaml) schema and CLI typings so variables.*.default can be specified as a boolean or number (in addition to string), enabling more natural YAML like default: false and default: 3.

Changes:

• Widened default type in the root and CLI-bundled JSON schemas to allow string | number | boolean.
• Updated the CLI ManifestVariable TypeScript interface to match the schema.
• Added CLI unit tests ensuring schema validation accepts boolean/number defaults.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
schema/rep-manifest.schema.json	Broadens manifest default type in the published schema.
cli/schema/rep-manifest.schema.json	Keeps the CLI-bundled schema in sync with the root schema change.
cli/src/utils/manifest.ts	Updates TS types so CLI code can represent boolean/number defaults.
cli/src/utils/tests/manifest.test.ts	Adds validation tests for boolean and number default values.

---

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

[Copilot]

There are additional checked-in copies of this schema that still restrict variables.*.default to string (e.g. docs/public/schema/rep-manifest.schema.json and the docs table in docs/src/content/docs/reference/manifest-schema.mdx). As-is, the docs site will keep publishing/validating the old schema even though schema/ and cli/schema/ were updated. Please update/remove those copies or introduce a single-source sync step so all published schemas stay consistent.

Suggested change

	"type": ["string", "number", "boolean"],
	"description": "Default value if the environment variable is not set. Only valid for non-required variables. Non-string values are coerced to strings."
	"type": "string",
	"description": "Default value if the environment variable is not set. Only valid for non-required variables."