[4i7]

Summary

Preserve clock timestamps in sanitized report text while retaining validated IPv6 masking.

Motivation

The IPv6 fallback regular expression treated clock values such as 04:17:42 as IPv6-like text. In exported reports this produced broken Next steps such as <REDACTED_IP>.912.

Changes

• Remove the redundant unvalidated IPv6 regular expression.
• Keep the existing Node isIP validation path for real IPv6 addresses.
• Add direct clock-time regression cases and an end-to-end Japanese Next steps report assertion.

Validation

• Targeted Vitest regression: 2 passed
• npm.cmd ci
• npm.cmd test (39 passed, 1 skipped)
• npm.cmd run build
• npm.cmd pack --dry-run
• npm.cmd audit --omit=dev (0 vulnerabilities)
• Built runtime check: clock timestamp preserved; compressed IPv6 redacted
• git diff --check

Risks and compatibility

No public API, MCP schema, CLI, collector, fixture, dependency, storage, or version change. Real IPv6 masking remains covered by the existing compressed-IPv6 regression.