Migrate UX and Dev research to GitHub Agentic Workflows#26
Merged
codegefluester merged 1 commit intomainfrom Feb 19, 2026
Merged
Migrate UX and Dev research to GitHub Agentic Workflows#26codegefluester merged 1 commit intomainfrom
codegefluester merged 1 commit intomainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request migrates UX and development research workflows to GitHub Agentic Workflows, introducing three new agentic workflow systems for game integration assessment in the GamesDAT project. The changes establish an orchestrated analysis system where multiple specialized agents coordinate to evaluate both technical feasibility and user experience aspects of game integrations.
Changes:
- Added three new workflow definitions (.md files) and their compiled lock files (.lock.yml) for UX assessment, development feasibility assessment, and game analysis orchestration
- Introduced an orchestrator pattern where analyze-game coordinates parallel execution of dev-feasibility and ux-assessment workflows
- Added automated maintenance workflow for managing expired agentic workflow outputs
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 17 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/ux-assessment.md | Workflow definition for assessing end-user setup burden and UX friction for game integrations |
| .github/workflows/ux-assessment.lock.yml | Compiled GitHub Actions workflow for UX assessment with Copilot CLI integration |
| .github/workflows/dev-feasibility.md | Workflow definition for evaluating technical feasibility and implementation complexity |
| .github/workflows/dev-feasibility.lock.yml | Compiled GitHub Actions workflow for development feasibility assessment |
| .github/workflows/analyze-game.md | Orchestrator workflow that coordinates both UX and dev assessments in parallel |
| .github/workflows/analyze-game.lock.yml | Compiled orchestrator workflow with workflow dispatch capabilities |
| .github/workflows/agentics-maintenance.yml | Automated maintenance workflow for closing expired workflow outputs |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+566
to
+573
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | ||
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | ||
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | ||
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | ||
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | ||
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | ||
|
|
||
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. |
There was a problem hiding this comment.
The instruction text incorrectly states the regex as /^aw_[A-Za-z0-9]{3,8}$/i with a range of {3,8}, but the actual JSON schema pattern in line 273 defines it as ^aw_[A-Za-z0-9]{4,8}$ with a range of {4,8}. This discrepancy will confuse users about the actual validation requirements.
Suggested change
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | |
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. | |
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{4,8}$/i | |
| - Format: aw_ prefix followed by 4 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abcd, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 4-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{4,8}$/i. |
Comment on lines
+566
to
+573
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | ||
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | ||
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | ||
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | ||
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | ||
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | ||
|
|
||
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. |
There was a problem hiding this comment.
The final instruction on line 573 states the regex as /^aw_[A-Za-z0-9]{3,8}$/i, which is inconsistent with the actual schema pattern ^aw_[A-Za-z0-9]{4,8}$ defined in line 273. The instruction should match the actual validation pattern to prevent validation errors.
Suggested change
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | |
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. | |
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{4,8}$/i | |
| - Format: aw_ prefix followed by 4 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_abc (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abcd, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 4-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{4,8}$/i. |
Comment on lines
+567
to
+574
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | ||
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | ||
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | ||
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | ||
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | ||
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | ||
|
|
||
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. |
There was a problem hiding this comment.
The VALID example "aw_abc" on line 570 is inconsistent with the actual pattern validation. According to the pattern ^aw_[A-Za-z0-9]{4,8}$ defined in line 273, "aw_abc" (only 3 characters after the prefix) should be INVALID, not VALID.
Suggested change
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | |
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. | |
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{4,8}$/i | |
| - Format: aw_ prefix followed by 4 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_abc (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abcd, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 4-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{4,8}$/i. |
Comment on lines
+566
to
+573
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | ||
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | ||
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | ||
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | ||
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | ||
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | ||
|
|
||
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. |
There was a problem hiding this comment.
The final instruction on line 573 states the regex as /^aw_[A-Za-z0-9]{3,8}$/i, which is inconsistent with the actual schema pattern ^aw_[A-Za-z0-9]{4,8}$ defined in line 273. The instruction should match the actual validation pattern to prevent validation errors.
Suggested change
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | |
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. | |
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{4,8}$/i | |
| - Format: aw_ prefix followed by 4 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_abc (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abcd, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 4-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{4,8}$/i. |
Comment on lines
+567
to
+574
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | ||
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | ||
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | ||
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | ||
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | ||
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | ||
|
|
||
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. |
There was a problem hiding this comment.
The final instruction on line 573 states the regex as /^aw_[A-Za-z0-9]{3,8}$/i, which is inconsistent with the actual schema pattern ^aw_[A-Za-z0-9]{4,8}$ defined in line 273. The instruction should match the actual validation pattern to prevent validation errors.
Suggested change
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | |
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. | |
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{4,8}$/i | |
| - Format: aw_ prefix followed by 4 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_abc (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc1, aw_Test, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 4-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{4,8}$/i. |
Comment on lines
+566
to
+573
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | ||
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | ||
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | ||
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | ||
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | ||
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | ||
|
|
||
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. |
There was a problem hiding this comment.
The example "aw_ab" is marked as INVALID because it's "too short" on line 569, which is inconsistent with the pattern regex ^aw_[A-Za-z0-9]{3,8}$/i mentioned in line 566 that would actually allow 3 characters. The actual pattern in line 273 requires {4,8}, so this example is correct but the stated regex in line 566 is wrong.
Suggested change
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | |
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. | |
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{4,8}$/i | |
| - Format: aw_ prefix followed by 4 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abcd, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 4-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{4,8}$/i. |
Comment on lines
+567
to
+574
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | ||
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | ||
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | ||
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | ||
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | ||
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | ||
|
|
||
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. |
There was a problem hiding this comment.
The example "aw_ab" is marked as INVALID because it's "too short" on line 569, which is inconsistent with the pattern regex ^aw_[A-Za-z0-9]{3,8}$/i mentioned in line 566 that would actually allow 3 characters. The actual pattern in line 273 requires {4,8}, so this example is correct but the stated regex in line 566 is wrong.
Suggested change
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | |
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. | |
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{4,8}$/i | |
| - Format: aw_ prefix followed by 4 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 4-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{4,8}$/i. |
Comment on lines
+567
to
+574
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | ||
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | ||
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | ||
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | ||
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | ||
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | ||
|
|
||
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. |
There was a problem hiding this comment.
The instruction text incorrectly states the regex as /^aw_[A-Za-z0-9]{3,8}$/i with a range of {3,8}, but the actual JSON schema pattern in line 273 defines it as ^aw_[A-Za-z0-9]{4,8}$ with a range of {4,8}. This discrepancy will confuse users about the actual validation requirements.
Suggested change
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | |
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. | |
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: ^aw_[A-Za-z0-9]{4,8}$ | |
| - Format: aw_ prefix followed by 4 to 8 alphanumeric characters (A-Z, a-z, 0-9) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_abc (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abcd, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 4-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against ^aw_[A-Za-z0-9]{4,8}$. |
Comment on lines
+566
to
+573
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | ||
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | ||
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | ||
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | ||
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | ||
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | ||
|
|
||
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. |
There was a problem hiding this comment.
The example "aw_ab" is marked as INVALID because it's "too short" on line 569, which is inconsistent with the pattern regex ^aw_[A-Za-z0-9]{3,8}$/i mentioned in line 566 that would actually allow 3 characters. The actual pattern in line 273 requires {4,8}, so this example is correct but the stated regex in line 566 is wrong.
Suggested change
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | |
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. | |
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{4,8}$/i | |
| - Format: aw_ prefix followed by 4 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 4-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{4,8}$/i. |
Comment on lines
+566
to
+573
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | ||
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | ||
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | ||
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | ||
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | ||
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | ||
|
|
||
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. |
There was a problem hiding this comment.
The VALID example "aw_abc" on line 570 is inconsistent with the actual pattern validation. According to the pattern ^aw_[A-Za-z0-9]{4,8}$ defined in line 273, "aw_abc" (only 3 characters after the prefix) should be INVALID, not VALID.
Suggested change
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i | |
| - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. | |
| - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{4,8}$/i | |
| - Format: aw_ prefix followed by 4 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) | |
| - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| - INVALID examples: aw_ab (too short), aw_abc (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) | |
| - VALID examples: aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 | |
| - To generate valid IDs: use 4-8 random alphanumeric characters or omit the field to let the system auto-generate | |
| Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{4,8}$/i. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.