feat: add resources directory validation for init and install commands

[itschip]

Summary

This PR implements automatic resources directory detection and validation for both init and install commands, ensuring that modules.json is always created in the correct location.

Key Changes

• Added find_resources_directory() function that traverses upward to find resources directory
• Updated both init and install commands to validate they operate within resources directory
• Enhanced error handling with descriptive messages when resources directory not found
• Improved user feedback with clear success/status messages

How It Works

The commands now work from:

• ✅ Within resources directory
• ✅ Subdirectories of resources (traverses upward)
• ✅ Parent directories containing resources (finds subdirectory)
• ❌ Unrelated directories (shows error and exits)

This ensures modules.json is always created in the correct resources directory regardless of where the user runs the command.

[itschip]

this is an mcp test

[Copilot]

Pull Request Overview

This PR adds automatic detection and validation of the resources directory for the init and install commands, ensuring that modules.json is always placed under the correct directory.

• Introduces find_resources_directory() to locate the nearest resources folder
• Updates CLI flow in main.rs to call validation before running init or install
• Adds user feedback prints in installer::init_fxpkg

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
src/main.rs	New helper to find resources dir and updated command logic
src/installer/mod.rs	Added success message print after creating modules.json

Comments suppressed due to low confidence (1)

src/main.rs:71

• No tests cover the failure path of find_resources_directory; consider adding unit tests to verify both success and error scenarios.

Err("Could not find 'resources' directory. Please run 'fxpkg init' from within or above a 'resources' directory.".to_string())

[Copilot]

Consider returning a PathBuf instead of String to preserve path semantics and avoid unnecessary string conversions.

Suggested change

	fn find_resources_directory(current_path: &Path) -> Result<String, String> {
	let mut path = current_path.to_path_buf();
	// Check if current directory is already "resources"
	if path.file_name().and_then(|n| n.to_str()) == Some("resources") {
	return Ok(path.to_string_lossy().to_string());
	}
	// Traverse upwards to find "resources" directory
	loop {
	let resources_path = path.join("resources");
	if resources_path.exists() && resources_path.is_dir() {
	return Ok(resources_path.to_string_lossy().to_string());
	fn find_resources_directory(current_path: &Path) -> Result<PathBuf, String> {
	let mut path = current_path.to_path_buf();
	// Check if current directory is already "resources"
	if path.file_name().and_then(|n| n.to_str()) == Some("resources") {
	return Ok(path);
	}
	// Traverse upwards to find "resources" directory
	loop {
	let resources_path = path.join("resources");
	if resources_path.exists() && resources_path.is_dir() {
	return Ok(resources_path);

[Copilot]

Add a doc comment explaining the lookup strategy and error cases for find_resources_directory to improve readability and maintainability.

Suggested change

	/// Locates the "resources" directory starting from the given path.
	///
	/// This function first checks if the current directory is named "resources".
	/// If not, it traverses upwards through parent directories to find a directory
	/// named "resources". If the directory is found, its path is returned as a `String`.
	///
	/// # Errors
	/// Returns an `Err` with a descriptive message if the "resources" directory
	/// cannot be found. This typically happens if the function is called from a
	/// location that is not within or above a "resources" directory.

[Copilot]

The error handling logic for both commands is duplicated; extract the match block into a helper to reduce repetition.

[itschip]

mcp test