Skip to content

DevBerth v0.1.5

Choose a tag to compare

@github-actions github-actions released this 21 Jul 21:03
8cc670e

What changed

#18 — docs: make stacked merges and save handoffs composable

What changed

  • Makes one user-requested stacked merge one release unit: a single roll-up PR, one main update, and one version, while lower shard PRs close as incorporated after the release succeeds.
  • Treats save as an actionable, case-insensitive command when used alone, with context, or in combined requests such as save and merge.
  • Keeps discussion, quotations, and rule definitions non-operative unless the user also directs the agent to perform a save.
  • Requires combined commands to follow the user's requested order while keeping every named mutation separately authorized.
  • Records both decisions in durable implementation documentation and updates the documentation index.
  • Executes the broadened save protocol and records byte-identical canonical and archived pre-merge handoffs.

Why

The prior workflow could produce several releases for one requested stack merge, and the previous exact-message save grammar rejected clear operational requests. These rules make both actions match the user's intended unit of work.

Impact

Users can naturally combine the handoff with commit, push, merge, or other explicit actions without weakening the boundary against accidental invocation. A stacked task now publishes one auditable source version instead of one version per implementation shard.

Incorporated PRs

  • #17docs: make stacked merges publish one version
  • #18docs: make stacked merges and save handoffs composable (roll-up)

Validation

  • git diff --check passed.
  • Verified operative and non-operative examples agree between AGENTS.md and the durable workflow decision record.
  • cmp confirmed docs/next-steps/README.md and its timestamped archive are identical.
  • The save snapshot was collected through the production DevBerth MCP and records Git, validation, runtime, services, ports, databases, and credential sources without secret values.
  • PR #17 CI passed (Build and test, 5m46s).
  • PR #18 CI passed (Build and test, 7m49s), including the application build, isolated UI-test target compilation, and unit/safe-integration suite.

Release provenance

This is a source-project release. It does not include a signed or notarized app binary.