[scop]

Closes # (issue)

Context

Changes

Note that the folders need to be in the root of the remote repository, and reword to avoid confusing two meanings of the word "scripts".

Confidence Score: 4/5

The PR is safe to merge, though the new wording should describe source_dir as relative to the remote repository root to avoid implying that nested paths are invalid.

The documentation correctly distinguishes the remote repository from the consuming repository, but its location wording is narrower than the implementation’s relative-path behavior.

Files Needing Attention: docs/configuration/remotes.md

_{Reviews (1): Last reviewed commit: "docs: clarify remote script folders" | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Describe the relative path behavior

The implementation resolves source_dir relative to the remote repository root and supports nested paths, while “must also be in the root” implies that only a direct child of the root is valid. Describing the resolution rule directly avoids prompting users to restructure valid remote repositories.

Suggested change

	If you provide [`scripts`](./scripts.md) in a remote config file, the [script `source_dir`](./source_dir.md) must also be in the **root of the remote repository**.
	If you provide [`scripts`](./scripts.md) in a remote config file, the [script `source_dir`](./source_dir.md) path is resolved relative to the **root of the remote repository**.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[mrexox]

Thank you for taking care!