Files
2dc0da40ff chore: refresh Truthmark to 2.2.0 (#15)
* Split Truthmark product and engineering truth lanes

* chore: align truthmark docs and runtime with lane updates

* chore: bump package version to 2.2.0

* chore: refresh truthmark surfaces for 2.2.0 and document release

* chore: migrate legacy truth docs to engineering legacy path

* chore: remove legacy docs/truth legacy docs from repository

* chore: trim document command prompts to adapter stubs

* chore: customize truth root README guidance per lane

* chore: make doc reviewer guidance lane-specific and helper-rendered

* fix: remove duplicate check lane-classification render in evidence gate

* fix: make realize doc example lane-agnostic to product and engineering

* feat: separate product and engineering truth lanes

* test: restore workflow surface coverage

* Fix workflow lane prompt boundaries

* test: guard read-only generated surface wording

* Fix manual Realize lane guidance

* fix: harden route relationship diagnostics

Validate reciprocal product and engineering route links, gate missing product-link review diagnostics on product evidence, and reject duplicate route entries with divergent relationship metadata.

* fix: merge duplicate route relationships

Allow repeated route entries for the same truth document, kind, and lane to contribute additive relationship metadata. Keep hard validation errors for kind and lane conflicts and emit merged relationships in RouteMap output.

* fix: make route relationships local

Treat realized_by and realizes metadata as route-local navigation edges. Validate target existence and lane compatibility without requiring reciprocal declarations, and document the chosen semantics.

---------

Co-authored-by: MerlinH <merlinh221@gmail.com>
2026-06-16 00:54:46 +10:00

41 lines
1.2 KiB
YAML

name: Feature request
description: Propose a Truthmark behavior, workflow, or documentation improvement
title: "feat: "
labels: [enhancement]
body:
- type: markdown
attributes:
value: |
Please keep proposals aligned with Truthmark's local-first, Git-reviewable repository-truth boundary.
- type: textarea
id: problem
attributes:
label: Problem
description: What user, maintainer, reviewer, or agent workflow problem would this solve?
validations:
required: true
- type: textarea
id: proposal
attributes:
label: Proposed change
description: Describe the smallest useful change.
validations:
required: true
- type: textarea
id: boundary
attributes:
label: Product-boundary check
description: Explain how this stays local-first, host-native, branch-scoped, and Git-reviewable.
validations:
required: true
- type: textarea
id: alternatives
attributes:
label: Alternatives considered
description: Optional; include workarounds or rejected designs.
- type: textarea
id: verification
attributes:
label: Verification idea
description: What test, fixture, generated diff, or validation command would prove this works?