Skip to content

ginee v0.25.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 27 May 07:35
· 7 commits to main since this release
v0.25.0
aac428b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

  • Filed issues, sub-issues, and PR descriptions now read cold to a human. A new 5-item audience check on ginee-file-* skills enforces user-facing titles + 2-4 sentence Summary + framework-internal sections after the human summary. The opaque [6:qa-engineer] Overlap-invariants regression spec — permanent CI gate (#83 framework hygiene) voice no longer ships; contractors, new team members, and you-six-months-later can pick up tickets without loading framework jargon (#175).
  • User-facing Phase-8 reports + delivery handoffs have a real schema. New core/templates/user-response.md — ## Result · ## What changed · ## Verification · ## Next · optional ## Notes ≤ 150 words + auto-mode addenda (## Delivery state · ## Accept / Feedback / Reject). No more 30-line walls-of-prose at the end of a task (#170).
  • Dispatches to cardinals never ship as freeform paragraphs. Self-lint on core/protocols/dispatch-prompt-schema.md graduated from advisory to a binding pre-send gate — non-compliant payloads restructure inline before send. Tighter dispatches = lower per-task token cost.
  • Non-compliant cardinal returns auto-fire carry-forward. Threshold-driven (≥ 2 missing required sections OR forbidden-pattern hit) → next dispatch to the same cardinal carries the rule forward automatically. Bounded second carve-out catches drifting cardinals (one format-only re-retry per task).
  • CI regression guards extended for the Tier 2 + Tier 3 compliance hooks (#179) and the new adapter-binding rule in CLAUDE.md (#180) — every new framework rule now classifies enforcement per adapter at author time.

Adopter migration

No action required — purely additive. Existing dispatches on closed tasks unaffected (forward-only). The next ginee-authored issue / sub-issue / dispatch / Phase-8 response runs the new gates automatically.

Adopters writing custom issue templates under local/ SHOULD adopt the same audience binding — not required, but produces sub-issues humans can pick up cold.

Notes

  • No local/framework.config.yaml changes. No new opt-out keys — the discipline is LLM self-review against the schema, same machinery as the existing doc-authoring protocol.
  • Existing open issues / sub-issues NOT retroactively rewritten (D14 reporter-content forbidden upheld; forward-only convention).
  • Full spec: migrations/schema-enforcement-and-human-audience.md.
Assets 5
Loading