fix(resolve): Tracked backfill instruction targets Tech Debt table that has no Tracked column

[dean0x]

Problem

src/assets/commands/resolve.mds instructs setting and backfilling a Tracked value for both FIX_SEPARATE and TECH_DEBT items in at least three places:

• Line 244: "Set Tracked for FIX_SEPARATE and TECH_DEBT items to (pending)"
• Line 353: "backfill Tracked = #{backlog_issue_number} in resolution-summary.md for each FIX_SEPARATE and TECH_DEBT item"
• Line 354: "Tracked stays (pending — TRACEABILITY: DEGRADED ({reason})) for each affected item"

The resolution-summary template defines:

## Fix Separately
| Issue | File:Line | Reason | Tracked |   ← has Tracked column
|-------|-----------|--------|---------|

## Deferred to Tech Debt
| Issue | File:Line | Risk Factor |         ← no Tracked column
|-------|-----------|-------------|

(src/assets/commands/resolve.mds lines 619–628)

There is no Tracked column in ## Deferred to Tech Debt. The instruction to write a Tracked value there is unsatisfiable for half the items it names. This was pre-existing on main but PR #327 restated the FIX_SEPARATE-and-TECH_DEBT pairing in additional places, amplifying the inconsistency.

Evidence

• src/assets/commands/resolve.mds:244 — first pairing instruction
• src/assets/commands/resolve.mds:353–354 — backfill pairing in Phase 9
• src/assets/commands/resolve.mds:619 — ## Fix Separately table (has Tracked)
• src/assets/commands/resolve.mds:625 — ## Deferred to Tech Debt table (no Tracked)

Fix

Two viable options:

1. Add Tracked to the Tech Debt table — | Issue | File:Line | Risk Factor | Tracked |. This matches the manage-debt operation's intent: the Git agent filing a backlog ticket covers both FIX_SEPARATE and TECH_DEBT items, so both should record the ticket number.

2. Narrow the instructions to FIX_SEPARATE only — remove TECH_DEBT from all three pairing sites. Appropriate if the Tech Debt table is consumed by tooling that does not expect the column.

Option 1 is likely correct: manage-debt processes both dispositions and returns a single backlog issue number; the symmetry is intentional. The template omission looks like an oversight.

Found during review of PR #327.