Add test coverage and documentation for org/repo-scoped fuzzy schedule scattering

[Copilot]

The fuzzy scheduling scattering algorithm already includes org/repo in the hash seed when available, but this behavior was not tested or documented. This ensures workflows with identical names across different repositories get different execution times, preventing org-wide load spikes.

Changes

Test coverage (pkg/workflow/schedule_preprocessing_test.go):

• Added TestFuzzyScheduleScatteringWithRepositorySlug - verifies different org/repo combinations produce different schedules
• Added TestFuzzyScheduleScatteringAcrossOrganization - verifies same workflow name across multiple repos scatter properly
• Added TestFuzzyScheduleScatteringWarningWithoutRepoSlug - verifies warning is shown when repository slug is not available

Documentation (docs/src/content/docs/reference/schedule-syntax.md):

• Added "Organization-Wide Scattering" section explaining cross-repository distribution
• Documented seed format: owner/repo/workflow-path

Code changes (pkg/workflow/schedule_preprocessing.go):

• Clarified that org/repo inclusion prevents same-named workflows from colliding across repositories
• Added warning when repository context is not available: "Fuzzy schedule scattering without repository context. Workflows with the same name in different repositories may collide. Ensure you are in a git repository with a configured remote."

How it works

Seed construction already includes repository context:

seed := c.workflowIdentifier
if c.repositorySlug != "" {
    seed = c.repositorySlug + "/" + c.workflowIdentifier
} else {
    // Warn if repository slug is not available
    c.IncrementWarningCount()
    c.addScheduleWarning("Fuzzy schedule scattering without repository context...")
}

Test results confirm distribution:

• githubnext/repo-1/ci.md → 22 10 * * *
• githubnext/repo-2/ci.md → 51 7 * * *
• githubnext/repo-3/ci.md → 12 2 * * *
• other-org/repo-1/ci.md → 53 13 * * *

Original prompt

Ensure the the fuzzy scheduling scattering algorithm includes org/repo in the hash computation to scatter accross an entire org as well.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[pelikhan]

@copilot show warning if the organization repo is not known

[Copilot]

@copilot show warning if the organization repo is not known

Added warning when repository context is not available during fuzzy schedule scattering. The warning message informs users that workflows with the same name in different repositories may collide without the org/repo context. Commit: 84efbf9