Add developer documentation and usage examples for DAG resolution and override merging

[Manpreets59]

1. Create a docs/usage.md or update the README.md with:

   What a node looks like (structure, fields)

   How override merging works (with a short diagram or example JSON)

   How to resolve a path using code (basic snippet with resolveNode)

2. Add JSDoc comments to key functions (e.g., resolveNode, mergeOverrides)

3. Optional: Add a demo.ts or examples/basic.ts file that runs a simple DAG resolution

[dysbulic]

1. I've started to document the graph structures. They're very much in flux still as I'm trying to have as little duplication of data as possible.

2. I've started a new workspace in Svelte TypeScript.

3. The Svelte app will currently let you generate a CAR file & import it into a Neo4j structure. It also allows the creation of ordered lists. Also, everything is versioned.

[dysbulic]

This is a screen cap of the current database when two CAR files have been loaded:

@ /mount/test/:

• to-import/
  • test #1/
    • subdirectory/
      • #2.txt
      • #3.txt
      • txt.txt
  • test #2/
    • Same content as ..⁄test #1⁄subdirectory⁄#2.txt.txt
    • Same content as ..⁄test #1⁄subdirectory⁄txt.txt.txt
    • Unique Content.txt
  • test #3/
  • txt.txt

@/mount/test/ & @/mount/test #2/:

• to-import/
  • test #1/
    • changed.txt
    • subdirectory
    • subdirectory/#2.txt
    • subdirectory/txt.txt
  • test #2/
    • Same content as ..⁄test #1⁄subdirectory⁄#2.txt.txt
    • Same content as ..⁄test #1⁄subdirectory⁄txt.txt.txt
  • test #3/
    • js.js
    • txt.txt
  • txt.txt

What I'm working on is the versioning when multiple resources are entered with the same type at the same location.

Unfortunately, the loading is wonky. There are two /mount/test/ paths & there should only be one.

[dysbulic]

I should also include the key: