Change log tracking in metadata block

[benjaminapetersen]

Related to #141 and #144.

Been thinking some more about tracking changes, which may just be:

• Drag across columns

---
created: 8 Jan, 2025
title: Projects We Care About Session x
id: 12346
---

# My Markdown File for Stuff

- foo
- bar
- baz 

<!-- 
HTML comments are not rendered.
This is probably the most reasonable way to track logs.
It can be in the footer and out of the way of the user.
When the file is open, users can see this, and its fine if they 
want to tamper.  But renderers of Markdown will ignore.

metadata:
  # namespace-esque in case users deliberately put their own HTML style blocks
  task.md:
    log:
    - updated: 
      - date: 2025, Jan 8
      - column: backlog
    - updated: 
      - date: 2025, Jan 7
      - column: doing
    - updated: 
      - date: 2025, Jan 3
      - column: done
-->

[BaldissaraMatheus]

It looks good but I think it may scale quickly, maybe we could add an env/docker variable to enable this feature.
Also, not related to this feature, but I was thinking about moving the tags to this headers block

[benjaminapetersen]

Tags in the header definitely make sense!

[benjaminapetersen]

Feature flag for "this is alpha, might change, don't depend on it too much yet?"

[benjaminapetersen]

Logs could get really long... might be good to up front do:

tasks.md (or whatever, to claim a namespace)
  logs:
    created:
    lastUpdated:
    history:
    - limit of 10 or 20 entries so as to keep this from being excessive, 
      or only track migrations across lanes.  prob important to decide 
      what events are useful for a user.  Its a metadata block, but still
      user metadata, not machine metadata.