[WIP] Fix failing GitHub Actions workflow lint-go

[Copilot]

• Investigate CI failure details from GitHub Actions run 24575058718 (job 71858092536)
• Identify root cause from lint-go logs
• Reproduce current repository validation state locally before making changes
• Apply minimal fix for testifylint expected/actual assertion order in affected test
• Run targeted tests/lint plus required full pre-commit validation (make agent-finish)
• Run parallel validation and report final status

[Copilot]

Pull request overview

Fixes the failing lint-go GitHub Actions workflow by addressing testifylint assertion ordering in Go tests.

Changes:

• Updated assert.Equal argument ordering in pkg/constants/spec_test.go for formatting constant assertions.

Show a summary per file

File	Description
pkg/constants/spec_test.go	Adjusts assertion argument ordering for documented constant-value checks (currently reversed vs Testify’s expected, actual signature).

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comments suppressed due to low confidence (1)

pkg/constants/spec_test.go:198

• Same issue as above: assert.Equal arguments are reversed. Please use assert.Equal(t, expected, actual, ...) so constants.LineLength(100) is the expected value and constants.ExpressionBreakThreshold is the actual value (consistent with other tests like pkg/constants/spec_test.go:235 and pkg/workflow/mcp_gateway_config_test.go:32).

	assert.Equal(t, constants.ExpressionBreakThreshold, constants.LineLength(100),
		"ExpressionBreakThreshold should be 100 as documented")

• Files reviewed: 1/1 changed files
• Comments generated: 1