themes: Add candidate theme from issue #382

[github-actions]

Candidate theme submission

Generated from #382.

Closes #382.

• Title: Smoked
• Slug: smoked
• Repository: https://github.com/theelderemo/Smoked
• Submitted by: @theelderemo
• Submitter role: author
• Status: candidate
• Tags: dark, minimal, oneline
• Screenshots: 2

Reviewer checklist:

• Confirm the repository is the original project or an appropriate maintained fork.
• Confirm screenshots are safe to redistribute in this catalog.
• Edit title, description, tags, and screenshot alt text if needed.
• Keep status: "candidate" until the theme is ready to appear publicly.

[theelderemo]

@BeyondMagic Hey! This PR was merged, but the entry landed on main still as a candidate, so Smoked isn't rendering on the site.

It looks like the merge happened without a formal "Approve" review being submitted, so publish-approved-theme-submission.yml never happened. the workflow's run history has no run for #383. The entry on main still shows:

• "status": "candidate"
• "catalogIndex": 100382 the 100000 + issue number placeholder, confirming the publish script never ran

Since the branch is deleted, the review-trigger path can't be replayed. Could you manually flip src/content/themes/smoked.json to "status": "published" and assign the next available catalogIndex (or re-run the publish script against it)?

Thanks, and if by chance I misunderstand the flow, and I'm jumping to conclusions, I apologize!

[BeyondMagic]

Yeah, that's right, thanks for catching it!

[theelderemo]

that was supposed to say "if i'm jumping to conclusions" lol, but thank you!