fix(ci): geef runtime-env door via -e i.p.v. --env-file

docker run --env-file behoudt letterlijke quotes (bewezen test),
waardoor DATABASE_URL ongeldig was en de container crashte. Nu wordt
.env gesourced en elke sleutel met -e doorgegeven: exact dezelfde
waarden als bij de build. Contract-test verbiedt --env-file.

src/lib/deploy-workflow-contract.test.ts

@@ -44,11 +44,16 @@ describe("deploy job", () => {
 	});
 
 	it("runs container with production env and volumes", () => {
-		expect(deployJob).toContain("--env-file /var/www/atom-nexst/.env");
+		expect(deployJob).toContain(". /var/www/atom-nexst/.env");
+		expect(deployJob).toContain('"${ENV_ARGS[@]}"');
 		expect(deployJob).toContain("/var/www/Gamedata:/var/www/Gamedata");
 		expect(deployJob).toContain("/app/storage");
 	});
 
+	it("does not use --env-file (it keeps literal quotes)", () => {
+		expect(deployJob).not.toContain("--env-file");
+	});
+
 	it("frees port 3002 by stopping the compose container", () => {
 		expect(deployJob).toContain("docker stop epicnext-cms 2>/dev/null || true");
 	});