Skip to content

v0.17.0: Ticket flow, observability lens and public lens runs

Choose a tag to compare

@a-lottes a-lottes released this 29 Oct 07:47
· 23 commits to main since this release
7920845

What's new

Added

  • Observability lens for api projects: a Review lens for logs, metrics, traces and health checks (#89).
  • Companion install offer: /charter and a fresh /spark offer aspark-graph and aspark-guard once and record the answer in the constitution (#45).
  • Template version marker: every template carries <!-- aspark-template: aspark/0.1.0 -->, so consumers can check the version instead of guessing from structure (#44).
  • Ticket triage in /next-steps: reads open tickets, finds gaps, and puts a foundation slice first on new projects (#110).
  • Follow-up tickets: /peer-review, /demo-day and /go-live propose a ticket for each finding left open (#113).
  • Public lens runs as checkable worked examples: api lens on spring-petclinic-rest (#91), observability lens (#94), website lens on eleventy-base-blog, runs 1 and 2 (#96, #105).

Changed

  • /backlog checks open and closed issues before filing and marks items already covered or done (#114).
  • /story-time posts the spec-gate question to the ticket and accepts an answer there from someone with write access (#115).
  • /go-live adds a closing keyword to the release PR and states the outcome in the ticket comment (#112).

Known limitations

  • /next-steps ticket triage: in QA the agent once proposed a new foundation slice instead of reusing an open foundation ticket, which can lead to a duplicate ticket.
  • The template marker is not read by aspark-graph or aspark-guard yet. It is an inert comment until they do.
  • aSPARK is prompt material: its checks are best effort, not guarantees.

Full record: .spark/release-0.17.0/release.md · PRs #122, #123