# PLAN AUDIT: Package List vs Master Schedule Cross-Reference

**Plan file:** `~/.claude/plans/concurrent-jumping-puppy.md`
**Audit date:** 2026-05-16 (Rev 2 — re-audit after plan update)
**Auditor:** Claude (project-auditor skill, manufacturing mode)
**Evidence level:** inspected (source files parsed, no live runtime)

---

## VERDICT: SOUND (with 2 minor fixes needed)

All 9 original findings have been correctly addressed. The plan is now implementation-ready after fixing 2 residual issues found in this re-audit.

---

## Rev 1 Findings — Disposition

| # | Original Severity | Fix Applied | Verified |
|---|---|---|---|
| F-01 | CRITICAL | Auto-detect weight columns by header scan | YES — Step 1b now scans for "Net"+"Weight" keywords |
| F-02 | MAJOR | 435T replaced with verified 358.79T | YES — Data Sources section has correct weights |
| F-03 | MAJOR | Per-group weights removed | YES — "See note" replaces inline weights, note clarifies |
| F-04 | MAJOR | Supplier prefix on container numbers | YES — Steps 1b, 3, and Sheet 2 all use prefixed IDs |
| F-05 | MODERATE | Match by Equipment Name, ignore Item No | YES — Step 1a explicitly says "NOT Item No" |
| F-06 | MODERATE | Auto-build mapping from xlsx bilingual data | YES — Step 1c scrapes Machine PHOTO + DKTIND col D/I |
| F-07 | MODERATE | Two-pass matching documented | YES — Step 1d defines Pass 1 (specific) then Pass 2 (residual) |
| F-08 | LOW | Flat rack detection + crane override | YES — Step 3 checks for "FR"/"FLAT" in container specs |
| F-09 | LOW | 10% threshold for all items including catch-all | YES — Step 2 uses 10% uniformly |

---

## Rev 2 Findings — New Issues

### F-10 | MODERATE | Wrong weight column reference in Step 1a

**Plan says (Step 1a):** "Weight from col 11 (NET tons)"

**Actual master_schedule.tsv columns:**
```
Col 1: Area
Col 2: Line/Section
Col 3: Item No
Col 4: Equipment Name
Col 5: Weight (T)    <-- correct column
Col 6: Arrival
Col 7: Install Deadline
Col 8: Status
```

Weight is **col 5**, not col 11. If the script uses col 11, it will read empty data or the wrong field.

**Fix:** Change "col 11" to "col 5" in Step 1a.

---

### F-11 | LOW | Container count inconsistency within plan

**Line 13:** "~45 unique containers (after dedup)"
**Line 20 (table total):** "~57"

After applying F-04 (supplier prefix), there is no dedup collision — all 57 containers are unique. The "~45" figure is a leftover from the pre-fix audit where unprefixed container numbers collided.

**Fix:** Change line 13 to "57 containers" (remove the dedup note).

---

## Verified Claims (updated)

| Claim | Status | Evidence |
|---|---|---|
| 64 INCLUDED Motor items | VERIFIED | master_schedule.tsv: 57 non-assembly + 7 assembly = 64 |
| 6 xlsx package list files | VERIFIED | 6 files in /project/package_lists/ |
| Motor total 376.19T (358.79 + 17.40) | VERIFIED | Parsed TSV weight column sum |
| Package total ~324T gross | VERIFIED | Parsed all 6 xlsx: 323.6T |
| Motor Assembly items arrive Jun 15 | VERIFIED | TSV lines 59-65 show "2026-06-15" |
| Scope is Motor Line only | VERIFIED | All xlsx files are DKTEC/HWIA (Motor line suppliers) |
| DKTIND: 13 containers, 43 items, ~101T | VERIFIED | 100.7T actual |
| HWIA: 44 containers, 134 items, ~223T | VERIFIED | 222.9T actual (162.2 + 60.7) |
| 20 EXCLUDED items (5만 미포함) | VERIFIED | TSV lines 101-119 |
| Auto-detect columns fixes HWIA-03 shift | VERIFIED | HWIA-03 has NetWt at col 16 (vs 17 in others); header scan handles this |
| Two-pass matching resolves ordering | VERIFIED | Plan defines specific-first, residual-second |

---

## Recommendations

1. **Fix F-10** — change "col 11" to "col 5" in Step 1a (2-second fix)
2. **Fix F-11** — change "~45 unique containers (after dedup)" to "57 containers" on line 13

After these 2 fixes, plan is ready for implementation.

---

## Audit Metadata

| Field | Value |
|---|---|
| Audit cycle | Rev 2 (re-audit after 9-fix update) |
| Files inspected | 7 (1 TSV + 6 xlsx) |
| Evidence level | inspected |
| Prior findings resolved | 9/9 |
| New findings | 2 (1 moderate, 1 low) |
| Confidence | HIGH |
| Next phase | Implementation audit after cross_reference.py is written |