Bts Sync Check

Document Sync Check

Verify all documents are consistent with each other.

Steps

1. Run sync-check via bts binary:

   bts sync-check $ARGUMENTS
   

   This checks manifest.json for unverified drafts, unincorporated debates, unresolved gaps.

2. Additionally, read draft.md and manually check:

   • Do debate conclusions match what's written in the draft?
   • Are simulation-found gaps actually addressed (not just mentioned)?
   • If code exists, does the spec match the code?
   • Are version references consistent (e.g., "see research v1" → does v1 exist?)

3. Report findings:

   ## Sync Check Results
   
   ### Debates
   - debate-001 "OAuth2 vs JWT": ✓ reflected in draft.md
   - debate-002 "Session store": ✗ NOT in draft.md
   
   ### Simulations
   - simulation-001 gap #1: ✓ resolved in draft.md
   - simulation-001 gap #3: ✗ STILL OPEN
   
   ### Verifications
   - draft.md: ✗ NOT VERIFIED (verify was not run after last change)
   
   ### Code (if exists)
   - src/auth/oauth.ts: ✓ matches spec
   - src/auth/session.ts: ✗ spec says Redis but code uses in-memory
   
   Summary: 3 sync issues found