[Feature Request] Ability to "freeze" updates to the TOC

[andrew-m-j]

I'm exploring the Waypoint plugin and would be interested in ways to "freeze" the updating of items in the waypoint list based. I'm thinking of using folders as project containers, but eventually when the project is completed, the notes would be archived and disaggregated. I tested manually doing this by removing the %% Begin Waypoint %% and %% End Waypoint %% comments in the folder note, which leaves the list as is. However, this is a manual solution and I wonder if there are some potential improvements to the process.

• Prevent updates to the waypoint list based on a property/tag on the note. In other words, if the document has an #archive tag, for example, don't update the waypoint. Then, when a project is completed, the folder note could be marked as archived and the waypoint would remain static, even if the folder and files were moved (such as moving a note from this project into the next project). Obsidian would take care of the updating the individual links that change, by default.

• Have include/exclude folders that control whether the waypoints get updated. If I move a folder with a waypoint to a different part of my vault, like an Archived Projects folder, the waypoints no longer get updated. Note: This would be different than #37, which determined which files to include in the waypoint. Here, my idea is to control whether the waypoint gets updated based on the location of the note/folder.