docs(openspec): archive delivered CI and flow changes

[terry90918]

Summary

• archive the completed Drone CI migration and synchronize the ci-platform main spec
• archive the completed jt-flow authorization change and synchronize the jt-flow-authorization main spec
• record post-merge Drone build evidence for PRs ci: migrate jurislm-tools to Drone #173 and feat(jt-flow): streamline authorization checkpoints #171

Validation

• npm run validate (53/53)
• npm run validate:drone
• claude plugin validate .
• openspec validate --all --strict (9/9)

Follow-up archive for #172 and #170.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b3a8edc6-74c9-4200-bdb6-d9524ba31d17

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/archive-delivered-jt-flow-changes

---

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 99f409f22c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Fill in the generated purposes before archiving

Both newly created main specifications were committed with OpenSpec's generated TBD placeholder—the same placeholder also appears in openspec/specs/jt-flow-authorization/spec.md:4. Because these are now the canonical specs after the changes were archived, readers cannot determine either capability's intended scope from its Purpose section; replace both placeholders with durable summaries as the generated text explicitly requests.

Useful? React with 👍 / 👎.