docs: update logs command bugs plan with Issue 1 completion and Issue 2 investigation

Issue 1 (--tail flag in follow mode):
- Marked as completed with test results
- Documented fix in commit 7361e9d

Issue 2 (double timestamps):
- Completed investigation
- Root cause: Parser expects different format than zap logger produces
- Parser expects: "2025-01-20 15:04:05 [LEVEL] message"
- Actual format: "2025-11-21T15:05:42.725-05:00 | INFO | file:line | message | {json}"
- Parse failure causes fallback to time.Now() + full line as message
- Result: Double timestamp (CLI-added + original in message)
- Fix needed: Update parseLogLine() to handle actual zap log format

Next steps: Implement proper parser for ISO8601 timestamps with pipe separators

Author: technicalpickles