When implementing parent references, consider the Grid children feature (#132) which will need parent-aware behavior.
Grid children will use grid-world pixel coordinates but should be able to…
✅ ISSUE RESOLVED
All labels have been successfully applied using the single-ID workaround:
Issue #128 (Line/Arc Drawing):
- ✅ Major Feature (ID 1)
- ✅ priority:tier2-foundation (ID…
✅ COMPLETE SINGLE-ID MAPPING VERIFIED
After systematic testing, here are the RELIABLE single-ID mappings:
INCONSISTENCY FOUND!
Previous test: [4] alone → "Demo Target"
This test: [4, 5, 6] → (see result above)
If the MCP tool is consistent, we should see "Demo Target" as one of…
Test Results:
[4] → Result: (first result above)
- If array index: Should be "Major Feature" (position 4 in list)
- Earlier test showed: "Alpha Release Requirement"
[16] → Result:…
Test: ID [0]
If array index: Should be "Alpha Release Requirement" (index 0)
If actual ID: Could be anything (ID 0 might not exist)
Result: (see above)
CRITICAL BUG IDENTIFIED!
The MCP tool is using array indices from list_repo_labels output, NOT the actual Gitea label IDs!
Evidence:
When I tested `replace_issue_labels([11, 12,…
BUG DISCOVERED!
Test: replace_issue_labels with ID [18] alone
Expected: system:rendering (based on earlier test showing ID 18 in range 11-22)
Actual: (see result above)
This…
Complete Label ID Mapping
Based on systematic testing with add_issue_labels and replace_issue_labels:
Test 2: replace_issue_labels with ID [2]
Input: [2]
Previous: ID 1 = "Major Feature"
Result: (see labels applied above)
Test 1: add_issue_labels with ID [1]
Input: [1]
Expected: Unknown (testing to discover)
Result: (see labels applied above)
Update: MCP Tool Label Application is Unreliable
Attempted to use replace_issue_labels with the documented IDs, but wrong labels were still applied:
Test Case #128 - Tried to apply…
Complete Label ID Mapping
Tested all labels by adding IDs 1-22 to this issue. Here are the correct mappings: