nt8-sdk/BUILD_WARNINGS_REFERENCE.md

Build Warnings - Quick Fix Guide

Date: February 15, 2026
Build Status: ✅ SUCCESS (with warnings)

---

Current Warnings Summary

CS1998: Async method without await (12 occurrences)

Location:

• OrderManager.cs (7 warnings)
• OrderManagerTests.cs (2 warnings)

Issue: Methods marked as async but don't use await

Fix Options:

Option 1: Remove async if not needed

// BEFORE (Warning)
public async Task<string> MethodName()
{
    return "result";
}

// AFTER (Fixed)
public Task<string> MethodName()
{
    return Task.FromResult("result");
}

Option 2: Add await if async operation exists

// If you have async operations
public async Task<string> MethodName()
{
    await SomeAsyncOperation();
    return "result";
}

---

CS0169/CS0414: Unused fields (5 occurrences)

Location: SimpleORBNT8Wrapper.cs

Issue: Fields declared but never used

Fields:

• _rangeSize
• _openingRangeHigh
• _openingRangeStart
• _openingRangeLow
• _openingRangeCalculated

Fix Options:

Option 1: Remove if truly unused

// Remove these lines if not needed:
private double _openingRangeHigh;
private double _openingRangeLow;

Option 2: Use the fields

// If you plan to use them, implement the logic
private double _openingRangeHigh = 0;

void CalculateRange()
{
    _openingRangeHigh = High[0]; // Use the field
}

Option 3: Suppress if placeholder for future

#pragma warning disable CS0169
private double _openingRangeHigh; // Will be used in Phase 2
#pragma warning restore CS0169

---

Action Items

Priority 1: Critical for OMS

❌ None - OMS implementation hasn't started yet

Priority 2: Existing Code Cleanup

These warnings are in existing code (not OMS):

• OrderManager.cs - 7 async warnings
• SimpleORBNT8Wrapper.cs - 5 unused field warnings
• OrderManagerTests.cs - 2 async warnings

Recommendation: Fix these after OMS implementation to avoid modifying existing code.

---

For Kilocode: Warning Rules

✅ ALLOWED: Warnings in existing code

Kilocode can ignore warnings in:

• src/NT8.Adapters/** (existing wrapper)
• Existing OrderManager.cs (if it exists before OMS work)
• Existing test files

❌ FORBIDDEN: Warnings in new OMS code

Kilocode MUST NOT introduce warnings in new code:

• New src/NT8.Core/OMS/** files
• New tests/NT8.Core.Tests/OMS/** files

Rule for Kilocode:

When creating new OMS files:
- NO CS1998 warnings (remove async or add await)
- NO CS0169/CS0414 warnings (use all declared fields)
- Build with ZERO warnings for new code

---

Build Verification

Current Status

Build: ✅ SUCCESS
Warnings: 17 total
- 12 × CS1998 (async without await)
- 5 × CS0169/CS0414 (unused fields)

All warnings in EXISTING code (not OMS)

Target for OMS

Build: ✅ SUCCESS
New OMS files: ZERO warnings
Existing warnings: Can remain (cleanup later)

---

Quick Fix Script (Optional)

If you want to clean up existing warnings before OMS work:

# Fix unused fields in SimpleORBNT8Wrapper.cs
# Option 1: Comment out unused fields
# Option 2: Implement ORB calculation logic
# Option 3: Add #pragma warning disable

# Fix async warnings in OrderManager.cs
# Review each method and either:
# - Remove async keyword + return Task.FromResult()
# - Add await operations
# - Keep as-is if async needed for interface

---

Summary

For OMS Implementation:

• ✅ Build is working correctly
• ✅ Existing warnings are acceptable
• ✅ Kilocode should NOT modify existing code
• ✅ New OMS code must have ZERO warnings

After OMS Complete:

• Clean up existing warnings
• Review async patterns
• Remove unused fields or implement them

---

Build status: Ready for OMS implementation! 🚀

The warnings are in existing code, not a blocker for starting OMS work.