Release 1.0

[alvagante]

No description provided.

[Copilot]

Pull request overview

This PR prepares the codebase for the v1.0.0 release by expanding integrations (AWS/Proxmox), improving multi-source inventory linking, and refactoring the database layer to support both SQLite and PostgreSQL with a migration-first schema approach.

Changes:

• Added AWS integration types and health-check tests; updated inventory ID prefixing for Bolt/Ansible and improved node linking with per-source sourceData.
• Refactored database initialization to use a DatabaseAdapter abstraction (SQLite + Postgres) and migration-first schema management (removing legacy schema files).
• Updated docs, Dockerfiles, environment templates, and release metadata to reflect the v1.0.0 configuration model (.env as source of truth).

Reviewed changes

Copilot reviewed 89 out of 313 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
backend/src/integrations/bolt/BoltPlugin.ts	Clarifies node ID prefixing behavior in groups.
backend/src/integrations/aws/types.ts	Adds AWS integration type definitions + auth error type.
backend/src/integrations/aws/tests/AWSPlugin.healthCheck.test.ts	Adds unit tests for AWS plugin health check behavior.
backend/src/integrations/ansible/AnsibleService.ts	Prefixes Ansible group host node IDs with ansible: consistently.
backend/src/integrations/NodeLinkingService.ts	Extends linked nodes with per-source sourceData; adjusts identifier extraction.
backend/src/integrations/IntegrationManager.ts	Switches aggregated inventory nodes to LinkedNode[]; adds provisioning capability aggregation; adds per-source inventory timeout.
backend/src/database/rbac-schema.sql	Removes legacy RBAC schema file (migration-first).
backend/src/database/migrations/010_drop_integration_configs.sql	Adds migration to drop integration_configs table.
backend/src/database/migrations/009_integration_configs.sql	Adds historical migration that creates integration_configs.
backend/src/database/migrations/008_journal_entries.sql	Adds journal_entries table migration.
backend/src/database/migrations/007_permissions_and_provisioner_role.sql	Seeds new permissions and Provisioner role.
backend/src/database/migrations/002_seed_rbac_data.sql	Makes seeding timestamps consistent via CURRENT_TIMESTAMP.
backend/src/database/migrations/000_initial_schema.sql	Adds migration header documentation.
backend/src/database/migrations.sql	Removes legacy monolithic migration file.
backend/src/database/errors.ts	Adds typed DB error classes.
backend/src/database/audit-schema.sql	Removes legacy audit schema file (migration-first).
backend/src/database/SQLiteAdapter.ts	Introduces SQLite adapter implementing DatabaseAdapter.
backend/src/database/PostgresAdapter.ts	Introduces Postgres adapter implementing DatabaseAdapter.
backend/src/database/MigrationRunner.ts	Refactors migration runner to use DatabaseAdapter + dialect-aware migration selection.
backend/src/database/ExecutionRepository.ts	Refactors repository to use dialect placeholders via DatabaseAdapter.
backend/src/database/DatabaseService.ts	Refactors DB initialization to adapter factory + migrations only.
backend/src/database/DatabaseAdapter.ts	Adds unified DB adapter interface.
backend/src/database/AdapterFactory.ts	Adds adapter factory driven by DB_TYPE / DATABASE_URL.
backend/src/config/schema.ts	Adds Proxmox + AWS config schemas and provisioning safety config.
backend/src/config/ConfigService.ts	Parses Proxmox/AWS/provisioning env vars; adds getters.
backend/package.json	Bumps backend version to 1.0.0; updates build to copy migrations; adds pg + AWS SDK deps.
backend/.env.example	Updates v1.0.0 env template (integrations, provisioning safety, defaults).
README.md	Updates positioning/features/docs links/version history for v1.0.0.
Dockerfile.ubuntu	Adds prod-deps stage; copies migrations; uses shared entrypoint; updates env defaults.
Dockerfile.alpine	Adds prod-deps stage; copies migrations; uses shared entrypoint; updates env defaults.
Dockerfile	Updates version label; adjusts Bolt/OpenBolt install; copies migrations; adds env defaults.
CLAUDE.md	Updates database documentation to migration-first approach.
CHANGELOG.md	Adds v1.0.0 release notes including breaking changes.
.pre-commit-config.yaml	Tightens duplicate/backup filename detection regex.
.kirograph/config.json	Adds KiroGraph indexing config.
.kiro/todo/proxmox-restart-required.md	Documents cached build issue requiring restart (internal note).
.kiro/todo/expert-mode-prototype-pollution.md	Documents prototype pollution risk (internal note).
.kiro/todo/database-schema-cleanup-task.md	Documents DB cleanup task completion (internal note).
.kiro/todo/REMAINING_TODOS_REPORT.md	Adds prioritized TODO report (internal note).
.kiro/steering/tech.md	Adds tech stack steering doc.
.kiro/steering/structure.md	Adds repository structure steering doc.
.kiro/steering/security-best-practices.md	Adds allowlist-secret guidance for detect-secrets.
.kiro/steering/product.md	Adds product summary steering doc.
.kiro/steering/kirograph.md	Adds KiroGraph usage steering doc.
.kiro/steering/git-best-practices.md	Expands pre-commit hook documentation.
.kiro/specs/v1-release-prep/requirements.md	Adds release-prep requirements spec.
.kiro/specs/v1-release-prep/design.md	Adds release-prep design spec.
.kiro/specs/v1-release-prep/.config.kiro	Adds Kiro spec config.
.kiro/specs/pabawi-release-1-0-0/.config.kiro	Adds Kiro spec config.
.kiro/specs/missing-lifecycle-actions/bugfix.md	Adds lifecycle actions bugfix spec.
.kiro/specs/missing-lifecycle-actions/.config.kiro	Adds Kiro spec config.
.kiro/specs/azure-support/requirements.md	Adds Azure integration requirements spec (future work).
.kiro/specs/azure-support/.config.kiro	Adds Kiro spec config.
.kiro/specs/090/puppet-pabawi-refactoring/tasks.md	Adds Puppet module refactoring plan.
.kiro/specs/090/puppet-pabawi-refactoring/requirements.md	Adds Puppet module refactoring requirements.
.kiro/specs/090/puppet-pabawi-refactoring/.config.kiro	Adds Kiro spec config.
.kiro/specs/090/proxmox-integration/.config.kiro	Adds Kiro spec config.
.kiro/specs/090/proxmox-frontend-ui/requirements.md	Adds Proxmox frontend UI requirements spec.
.kiro/specs/090/proxmox-frontend-ui/.config.kiro	Adds Kiro spec config.
.kiro/settings/mcp.json	Adds MCP server config for KiroGraph tools.
.kiro/hooks/kirograph-sync-on-save.json	Adds KiroGraph sync hook (save).
.kiro/hooks/kirograph-sync-on-delete.json	Adds KiroGraph sync hook (delete).
.kiro/hooks/kirograph-sync-on-create.json	Adds KiroGraph sync hook (create).
.kiro/done/proxmox-ssl-fix.md	Marks Proxmox SSL fix as done (internal note).
.kiro/done/provisioning-endpoint-fix.md	Marks provisioning endpoint fix as done (internal note).
.kiro/done/node-linking-redesign.md	Marks node linking redesign as done (internal note).
.kiro/done/docker-missing-schema-files.md	Marks Docker schema copy fix as done (internal note).
.kiro/done/database-schema-cleanup-task.md	Marks DB schema cleanup as done (internal note).
.kiro/database-cleanup-prompt.md	Adds DB cleanup prompt (internal note).
.kiro/analysis/ManageTab_Lifecycle_Flow.md	Adds ManageTab lifecycle flow analysis (internal note).
.github/copilot-instructions.md	Updates DB schema guidance to migration-first.
.env.docker	Updates Docker env template for v1.0.0 configuration model.

[Copilot]

Pull request overview

Copilot reviewed 89 out of 313 changed files in this pull request and generated 6 comments.

[Copilot]

The migration runner now claims PostgreSQL support, but splitting SQL by ; is not safe for many valid Postgres migrations (e.g., functions/procedures with $$...;...$$, trigger bodies, complex statements containing semicolons). This can cause migrations to fail or be applied partially. A concrete improvement is to execute the entire migration file as a single execute(sql) when dialect === "postgres", while keeping per-statement execution for SQLite (or alternatively, add a more robust SQL statement parser/marker-based splitter).

[Copilot]

This directory creation is now duplicated with SQLiteAdapter.initialize() (which already creates the directory when the path isn’t :memory:). To keep responsibilities clear (and avoid doing filesystem work when DB_TYPE=postgres), consider removing this block from DatabaseService and letting the SQLite adapter handle it internally, or conditionally running it only when the selected adapter dialect is SQLite.

[Copilot]

getAllProvisioningCapabilities() introduces a large inline return type and relies on runtime duck-typing + no-unsafe-* suppressions. This makes the API harder to maintain and refactor safely. A more robust approach is to define a shared exported type (e.g., ProvisioningCapability) and a small interface like ProvisioningCapableExecutionTool { listProvisioningCapabilities(): ProvisioningCapability[] }, then narrow via a typed type-guard—removing the need for ESLint suppressions and making the contract explicit for plugin implementers.

[Copilot]

getAllProvisioningCapabilities() introduces a large inline return type and relies on runtime duck-typing + no-unsafe-* suppressions. This makes the API harder to maintain and refactor safely. A more robust approach is to define a shared exported type (e.g., ProvisioningCapability) and a small interface like ProvisioningCapableExecutionTool { listProvisioningCapabilities(): ProvisioningCapability[] }, then narrow via a typed type-guard—removing the need for ESLint suppressions and making the contract explicit for plugin implementers.

Suggested change

	getAllProvisioningCapabilities(): {
	source: string;
	capabilities: {
	name: string;
	description: string;
	operation: "create" | "destroy";
	parameters: {
	name: string;
	type: string;
	required: boolean;
	default?: unknown;
	}[];
	}[];
	}[] {
	const result: {
	source: string;
	capabilities: {
	name: string;
	description: string;
	operation: "create" | "destroy";
	parameters: {
	name: string;
	type: string;
	required: boolean;
	default?: unknown;
	}[];
	}[];
	}[] = [];
	for (const [name, tool] of this.executionTools) {
	// Check if the plugin has listProvisioningCapabilities method
	if (
	"listProvisioningCapabilities" in tool &&
	typeof tool.listProvisioningCapabilities === "function"
	) {
	try {
	// eslint-disable-next-line @typescript-eslint/no-unsafe-assignment, @typescript-eslint/no-unsafe-call
	const capabilities = tool.listProvisioningCapabilities();
	// eslint-disable-next-line @typescript-eslint/no-unsafe-member-access
	if (capabilities && capabilities.length > 0) {
	result.push({
	source: name,
	// eslint-disable-next-line @typescript-eslint/no-unsafe-assignment
	export interface ProvisioningCapabilityParameter {
	name: string;
	type: string;
	required: boolean;
	default?: unknown;
	}
	export interface ProvisioningCapability {
	name: string;
	description: string;
	operation: "create" | "destroy";
	parameters: ProvisioningCapabilityParameter[];
	}
	export interface ProvisioningCapabilitySource {
	source: string;
	capabilities: ProvisioningCapability[];
	}
	export interface ProvisioningCapableExecutionTool {
	listProvisioningCapabilities(): ProvisioningCapability[];
	}
	private isProvisioningCapableExecutionTool(
	tool: ExecutionToolPlugin
	): tool is ExecutionToolPlugin & ProvisioningCapableExecutionTool {
	return (
	"listProvisioningCapabilities" in tool &&
	typeof tool.listProvisioningCapabilities === "function"
	);
	}
	getAllProvisioningCapabilities(): ProvisioningCapabilitySource[] {
	const result: ProvisioningCapabilitySource[] = [];
	for (const [name, tool] of this.executionTools) {
	if (this.isProvisioningCapableExecutionTool(tool)) {
	try {
	const capabilities = tool.listProvisioningCapabilities();
	if (capabilities.length > 0) {
	result.push({
	source: name,

[Copilot]

Setting linkedNode.source to linkedNode.sources[0] can be order-dependent (based on discovery/iteration order), which may result in inconsistent “primary source” selection across runs and potentially incorrect behavior for code paths that still rely on node.source. To make this deterministic, pick the primary source using a consistent rule (e.g., highest configured plugin priority, or a stable predefined ordering), and then set linkedNode.source from that chosen source.

[Copilot]

Pull request overview

Copilot reviewed 82 out of 303 changed files in this pull request and generated 5 comments.

Comments suppressed due to low confidence (1)

backend/src/integrations/IntegrationManager.ts:1

• Using Promise.race for timeouts here can create unhandled rejections: if timeoutPromise wins, the Promise.all([source.getInventory(), ...]) continues running in the background, and if getInventory() later rejects it may surface as an unhandled rejection (and still consume resources). Consider wrapping each source call in a timeout helper that attaches a .catch(...) to the losing branch, or use AbortController-based cancellation (if supported by the integrations) so timed-out work is actually stopped/handled.

/**

[Copilot]

This maps every group.hosts entry into a string template without validating the runtime type. If the Ansible inventory contains non-string host entries (or mixed types), this will produce IDs like ansible:[object Object], breaking node lookups/linking. Filter to typeof h === \"string\" (and consider trimming/ignoring empty strings) before prefixing.

Suggested change

	const hosts = Array.isArray(group.hosts) ? group.hosts.map((h: string) => `ansible:${h}`) : [];
	const hosts = Array.isArray(group.hosts)
	? group.hosts
	.filter((h: unknown): h is string => typeof h === "string")
	.map((h) => h.trim())
	.filter((h) => h.length > 0)
	.map((h) => `ansible:${h}`)
	: [];

[Copilot]

This maps every group.hosts entry into a string template without validating the runtime type. If the Ansible inventory contains non-string host entries (or mixed types), this will produce IDs like ansible:[object Object], breaking node lookups/linking. Filter to typeof h === \"string\" (and consider trimming/ignoring empty strings) before prefixing.

[Copilot]

Using Promise.race for timeouts here can create unhandled rejections: if timeoutPromise wins, the Promise.all([source.getInventory(), ...]) continues running in the background, and if getInventory() later rejects it may surface as an unhandled rejection (and still consume resources). Consider wrapping each source call in a timeout helper that attaches a .catch(...) to the losing branch, or use AbortController-based cancellation (if supported by the integrations) so timed-out work is actually stopped/handled.

[Copilot]

If COMMIT/ROLLBACK fails (e.g., connection issue), _inTransaction will remain true, leaving the adapter in an inconsistent state and potentially blocking future transactions. Set _inTransaction = false in a finally block (and consider surfacing a structured DB error type for these cases, similar to query/connection failures).

Suggested change

	await this.execute("COMMIT");
	this._inTransaction = false;
	}
	async rollback(): Promise<void> {
	await this.execute("ROLLBACK");
	this._inTransaction = false;
	try {
	await this.execute("COMMIT");
	} finally {
	this._inTransaction = false;
	}
	}
	async rollback(): Promise<void> {
	try {
	await this.execute("ROLLBACK");
	} finally {
	this._inTransaction = false;
	}

[Copilot]

Directory creation is now duplicated (SQLiteAdapter.initialize already creates the parent dir when appropriate). More importantly, when running with DB_TYPE=postgres, DATABASE_PATH may not represent a filesystem path, and dirname(...)/mkdirSync(...) can behave unexpectedly or fail. Prefer moving the directory creation responsibility fully into SQLiteAdapter.initialize() and only doing it when the selected dialect is SQLite.