Skip to content

Update: adopt SpecSync 5 and Trust 1#14

Draft
0xLeif wants to merge 4 commits into
mainfrom
0xleif/trust-1-org-rollout
Draft

Update: adopt SpecSync 5 and Trust 1#14
0xLeif wants to merge 4 commits into
mainfrom
0xleif/trust-1-org-rollout

Conversation

@0xLeif

@0xLeif 0xLeif commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adopt SpecSync 5.0.1 and Trust 1.0.0 governance for the GitHub plugin.
  • Add an active canonical GitHub specification with stable requirement evidence.
  • Lint and syntax-check every executable and smoke-test offline help for every bin/fledge-github* command.
  • Correct Claude, Cursor, and Gemini SpecSync guidance and expand meaningful-path coverage for committed governance files.

Test Plan

  • fledge lanes run verify — ShellCheck, Bash syntax, and all-executable offline help smoke pass
  • specsync check --strict --force passes at the committed advisory threshold
  • Definition and closing approvals recorded as user:0xLeif
  • All review threads resolved
  • Fresh hosted Trust and CodeQL checks pass on the latest commit
  • Non-vacuous SpecSync file and LOC coverage reaches 100%

Blocker

All six implementation files are extensionless Bash executables. SpecSync 5.0.1 does not discover extensionless files through its supported language extensions, so it reports 0/0 coverage; --require-coverage 100 correctly rejects that vacuous result. The PR remains draft until SpecSync supports shebang/extensionless discovery and the repository can enforce a truthful 100% threshold. No wrapper or product-script rename is included in this migration.

Authenticated GitHub reads and mutations remain independently authorized and are intentionally excluded from the offline migration lane.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adopts SpecSync 5.0.1 and Trust 1.0.0 governance for the GitHub Fledge plugin, introducing canonical specs, companion files, migration change records, task definitions, and IDE skill commands. The review feedback suggests removing redundant empty headings in the skill markdown files, correcting split acceptance criteria in the migration change files, and expanding the smoke test and verification commands to cover all fledge-github sub-executables instead of only the main dispatcher.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread .claude/skills/spec-sync/SKILL.md Outdated
Comment thread .codex/skills/spec-sync/SKILL.md Outdated
Comment thread .cursor/skills/spec-sync/SKILL.md Outdated
Comment thread fledge.toml Outdated
Comment thread .specsync/sdd.json Outdated
@0xLeif 0xLeif marked this pull request as ready for review July 13, 2026 14:54
@0xLeif 0xLeif requested a review from 0xGaspar July 13, 2026 14:54

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f5ee59c46f

ℹ️ 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".

Comment thread .gemini/commands/specsync/create-change.toml Outdated
Comment thread .claude/commands/specsync/create-spec.md Outdated
Comment thread .specsync/sdd.json
@0xLeif 0xLeif marked this pull request as draft July 13, 2026 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant