The get command with --export flag was incorrectly using the full path to generate environment variable names instead of just the final segment. This caused confusing export statements where the variable name included the entire path hierarchy.

Problem

When running:

crumb get /foo/live/DB_DSN --export

The output was:

export FOO_LIVE_DB_DSN="value"

But users expect:

export DB_DSN="value"

Root Cause

The ExtractVarName function in /pkg/storage/storage.go was converting the entire path to an environment variable name by replacing all slashes with underscores, rather than extracting only the final path segment like the existing ConvertPathToEnvVar function used by the export command.

Solution

Modified ExtractVarName to:

1. Split the path by / separators
2. Extract only the last segment (the actual secret name)
3. Apply the same sanitization rules (uppercase, replace dashes with underscores)

This makes the behavior consistent between get --export and the standalone export command.

Testing

• Added comprehensive test coverage for ExtractVarName with various path formats
• Verified both bash and fish shell export formats work correctly
• All existing tests continue to pass
• Manual testing confirms the fix resolves the reported issue

Fixes #6.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.