Add artifact exclusion and goal mode orchestration logic

[mashan555]

No description provided.

[junie-jetbrains]

Address the identified logic and naming concerns to improve the robustness and clarity of the new artifact exclusion utility.

Comments

• src/utils/git-exclude.ts:96: Check if the header already exists before appending it to avoid duplication when patterns are added incrementally.
• test/utils/git-exclude.test.ts:61: Rename the test to reflect that the pattern is appended even if it is currently present as a comment.

---

Help us improve Junie code review (EAP): Share feedback

[junie-jetbrains]

Suggested change

	// Keep whatever the checkout already excluded and append below it.
	const prefix = existing === "" || existing.endsWith("\n") ? existing : `${existing}\n`;
	fs.writeFileSync(excludePath, `${prefix}${EXCLUDE_HEADER}\n${missing.join("\n")}\n`);
	// Keep whatever the checkout already excluded and append below it.
	const prefix = existing === "" || existing.endsWith("\n") ? existing : `${existing}\n`;
	const header = existing.includes(EXCLUDE_HEADER) ? "" : `${EXCLUDE_HEADER}\n`;
	fs.writeFileSync(excludePath, `${prefix}${header}${missing.join("\n")}\n`);

Check if the header already exists before appending it to avoid duplication when patterns are added incrementally.

[junie-jetbrains]

The test name is misleading. It should indicate that the pattern is appended even if present as a comment, as the expectation expect(added).toEqual([".junie/plans/"]) confirms.