Fix typo in conf.py

[felix91gr]

The subset and defect tags had their descriptions swapped with one another. Now they're all good :)

[netlify]

✅ Deploy Preview for scrc-coding-guidelines ready!

Name	Link
🔨 Latest commit	1fedd04
🔍 Latest deploy log	https://app.netlify.com/projects/scrc-coding-guidelines/deploys/689561ea8866c80007bd981d
😎 Deploy Preview	https://deploy-preview-170--scrc-coding-guidelines.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[felix91gr]

:o help, what did I do wrong?

[PLeVasseur]

Nothing you did wrong haha

Spec lock file is out of date

Could you issue another PR checking what changed and updating the lock file?

[felix91gr]

Sure! Brb

[felix91gr]

Took me a while haha, had to dust off some things with rustup and then compile uv. The compiler optimizations at the end took a good 5-10 minutes XD

(Also, uv looks pretty slick!)

[PLeVasseur]

Hey @felix91gr -- could you have the spec lock file update be its own PR for traceability purposes?

Sorry for the additional hurdle 🙏

[felix91gr]

@PLeVasseur okay, now I've made this one a descendant of #171's commit, so after 171 gets merged, this one's own commit should follow seamlessly

[felix91gr]

It seems that maneuver made github a little dizzy. I wonder if it's got to do with a cache not being invalidated...

@PLeVasseur does it look like this PR has 2 commits instead of one to you too?

[felix91gr]

I mean... no worries, I can totally just do this again XD

[felix91gr]

I sent it clean once again. Now, it seems like github understood that the other commit was already in main

[PLeVasseur]

Weird, it still shows as two commits when viewing on GitHub.

Hmm, did a rebase not fix this?

[felix91gr]

Argh, dang it. One sec. Brb.

[felix91gr]

Okay, did a clean 100% new everything from the current main. This should work x'D

[felix91gr]

⛵