From PR #104: Performance Issue + Name collision handling

[erezh16]

🟡 MEDIUM SEVERITY - Performance Issue

The lookup_by_name() method performs a linear O(n) scan through all UUID directories, reading and parsing each manifest file. This will significantly degrade performance as resources grow.

Recommendation:
Implement a name-to-UUID index/cache:

1. In-memory dictionary maintained by ResourceHandler
2. Separate index file (name -> UUID mapping)
3. Integration with existing Description index system

This would reduce lookups from O(n) to O(1).

🟡 MEDIUM SEVERITY - Name Collision Handling

The lookup_by_name() returns the first match found, but directory iteration order is not guaranteed. This leads to non-deterministic behavior when multiple resources share the same name.

Recommendation:
Either:

1. Enforce unique names at creation time
2. Document that name-based lookup may return arbitrary results for duplicates
3. Return an error when duplicates exist, forcing UUID-based access

[erezh16]

I will merge this with item 3 of issue #116 so that deletions do not become arbitrary again. In other words, name conflicts are resolved through versioning. When creating a new resource (not updating) with the same name of an existing resource of the same type (existing skill / tool / etc), the new resource will have its own UUID, a new version and a pointer to previous version (just like git). Name lookup will always return the latest version - fast O(1) and more sensible.

[github-actions]

🤖 Automatic Labeling

Bob Shell has analyzed this issue and applied the following label(s): bug, enhancement

These labels were selected based on the issue content and available label descriptions. If you believe the labels are incorrect, feel free to modify them manually.