config: default time range template is now absolute localtime + duration #7671
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
It bugged me that only the op log used .ago(), and then I found a situation where I wasn't sure whether "1 day ago" meant 1.1 days ago or 1.9 days ago. IMHO, displaying absolute times should be the default for accuracy, unless the user wishes otherwise.
Grepping uncovered an SVG (and presumably corresponding PNG) that with op log content. I am not sure whether this demo content needs updating, and if so, how.
This probably introduces inconsistencies with webpage content as well?
Checklist
If applicable:
CHANGELOG.mdREADME.md,docs/,demos/)cli/src/config-schema.json)