Running status command after MemoryMigrationSource fails

The failure is:

panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x10 pc=0x40b8b7]

goroutine 1 [running]:
panic(0x8b3bc0, 0xc820010160)
    /usr/local/go/src/runtime/panic.go:464 +0x3e6
main.(*StatusCommand).Run(0xe64ee8, 0xc82000a5d0, 0x0, 0x0, 0x9e0718)
    /home/tim/dev/go/src/github.com/rubenv/sql-migrate/sql-migrate/command_status.go:86 +0xb87
github.com/mitchellh/cli.(*CLI).Run(0xc8203ee000, 0xc820012510, 0x0, 0x0)
    /home/tim/dev/go/src/github.com/mitchellh/cli/cli.go:153 +0x56e
main.realMain(0xc820000180)
    /home/tim/dev/go/src/github.com/rubenv/sql-migrate/sql-migrate/main.go:39 +0x39e
main.main()
    /home/tim/dev/go/src/github.com/rubenv/sql-migrate/sql-migrate/main.go:11 +0x18

Perhaps since those records exist in the database (even though they doen't in the file system) we should just consider then as Migrated = true and add a new row?

Start in command_status.go at line 86 and trace how StatusCommand.Run handles records from MemoryMigrationSource that remain in the database but not the filesystem. Reproduce the status command failure and determine the expected treatment of those records; done means the command no longer panics and reports a consistent migration status.