Fix test structure: move forEach outside it block for proper test isolation

[Copilot]

Addresses test antipattern where forEach loop was nested inside a single it block, causing all assertions to run in one test case.

Changes

• Moved forEach loop outside it block in GMT Correlation (584285) Validation test suite
• Each correlation data point now generates its own it test case with descriptive name

Before/After

Before: Single test with loop inside

it('should validate direct source correlations using GMT constant', () => {
  directData.slice(0, 5).forEach(correlation => {
    // assertions here
  });
});

After: Individual test cases per data point

directData.slice(0, 5).forEach(correlation => {
  it(`should validate ${correlation.maya_long_count} ${correlation.event} using GMT constant`, () => {
    // assertions here
  });
});

This provides proper test isolation, clearer failure reporting, and ensures all correlations are tested even if one fails.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

Note

Refactors GMT correlation tests for proper isolation and clearer failures.

• In correlation-validation.spec.ts, move setup (directData, lcFactory, gmtCorr) to suite scope
• Replace a single it with a forEach by generating individual it cases for the first five direct-source correlations
• Each test validates the parsed Long Count against GMT, asserting year presence for Gregorian outputs

^{Written by Cursor Bugbot for commit 84d4fb4. This will update automatically on new commits. Configure here.}