A developer has used one Claude Code session all day. The morning's work, fixing a CSS bug, is finished. They now start a database migration, a task that is unrelated to the CSS bug, and expect it to need many more turns. Later, partway through the migration, Claude Code warns that the context is getting full, but the migration's current schema decisions and failing test output must be kept. Which approach handles both situations best?