Filesystem naming

[benjaminapetersen]

Just looking at the filesystem, currently naming is:

# Cards and lane names retain spaces and some special characters
# in UI and on-disk, such as `&` and `!` but do not allow others in UI or on-disk
├── tasks
│   ├── Lane Name 1
│   │   ├── Card Name 1.md
│   │   ├── Card Name 2.md
│   │   ├── Card Name 3.md
│   ├── Lane Name 2
│   │   ├── Card Name 4.md
│   │   ├── Card Name 5.md
│   │   ├── Card Name 6.md

For practical sorting reasons, it could be handy to have a terse naming convention map, such as:

# add the Creation Timestamp as a terse prefix.  Year Month Date only should be sufficient.
├── tasks
│   ├── lane_name_1
│   │   ├── 2024-12-03.card_name_1.md
│   │   ├── 2025-01-03.card_name_2.md
│   │   ├── 2025-01-04.card_name_3.md
│   ├── lane_name_2
│   │   ├── 2024-11-05.card_name_1.md
│   │   ├── 2024-12-09.card_name_2.md
│   │   ├── 2025-01-01.card_name_3.md

For those who do also utilize the on-desk Markdown editing feature from time to time, this provides benefits such as:

# example, ordering of "done" tasks:
# would allow easy review at later times.
# in addition, if this folder becomes excessively large, gives the 
# user a meaningful way to purge or archive later.
│   ├── done
│   │   ├── 2024-11-05.card_name_1.md
│   │   ├── 2024-12-09.card_name_2.md
│   │   ├── 2025-01-01.card_name_3.md

Which is handy for reporting, etc.