fix: handle duplicate OAuth scope enum variants (unblocks script API)

[l1n]

Summary

This PR fixes a code generation bug that caused duplicate Rust enum variants when OAuth scope URLs share the same final path segment. This unblocks generation of the google-script1 crate.

Problem

The Apps Script API has two OAuth scopes:

• https://www.google.com/calendar/feeds
• https://www.google.com/m8/feeds

The generator extracts the last path segment (feeds) and converts it to a CamelCase enum variant (Feed). Since both URLs have the same final segment, this created duplicate enum variants:

pub enum Scope {
    Feed,  // calendar/feeds
    Feed,  // m8/feeds - DUPLICATE!
}

This caused compilation to fail with E0428: the name 'Feed' is defined multiple times.

Solution

1. Removed script from the blacklist in etc/api/shared.yaml

   • The original comment said "redefinition of type (Feed)" but this was misleading — it's about scope variants, not schema types

2. Added deduplication logic to src/generator/templates/api/lib/lib.mako

   • Pre-processes all scope URLs to detect duplicate variant names
   • For duplicates, uses more of the URL path to create unique names

Result

The generated code now has unique variant names:

pub enum Scope {
    CalendarFeeds,  // https://www.google.com/calendar/feeds
    M8Feeds,        // https://www.google.com/m8/feeds
    // ...
}

Testing

• Generated google-script1 successfully
• cargo check passes on the generated crate

---

🤖 Generated with Claude Code

[Byron]

Thanks a lot, much appreciated!

Please note that I regenerated the script1 crate myself to avoid having to review 7k lines of code 😅.