[teckedd-code2save]

Visitors can now start GroundControl from their computer, choose local Docker or an existing Linux server, and open the private setup link printed by the launcher. Projects now represent an application with folder or GitHub sources and separate deployment instances; users can connect an existing workload or launch a new one, and dismiss discovery suggestions.

The change includes desktop-aware onboarding, a folder picker, grouped discovery, additive project migrations, and updated installation and release documentation. Existing runtime records and workload locations are preserved.

Publishing is separated from updating the operator VPS: a main merge builds a candidate image, clean server and desktop acceptance must pass before latest is promoted, and the production VPS deployment requires an explicit manual workflow input. This merge does not request a production restart.

Validation: 501 application tests and production build passed after merging latest main; all 9 launcher tests passed; desktop host execution regression passed; populated-database migration check preserved all 48 existing tables, relationships and values. CI and anonymous clean-install acceptance provide the remaining release checks.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
38763612	Triggered	Generic Password	a5dc892	scripts/check-project-discovery.cjs	View secret
38763611	Triggered	Username Password	a5dc892	scripts/check-desktop.cjs	View secret
38763610	Triggered	Username Password	30972aa	scripts/check-project-migrations.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}