mirror of
https://github.com/merlinhu1/truthmark.git
synced 2026-08-25 07:53:25 +02:00
2dc0da40ff
* 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>
955 B
955 B
Support
Use GitHub issues for support requests, bug reports, documentation problems, and workflow questions.
Before opening an issue:
- Check the README for the normal install and validation flow.
- Check the docs index for detailed behavior and architecture references.
- Run the narrowest relevant command and include its output when possible:
truthmark check --json
truthmark index --json
For source-checkout development, also see CONTRIBUTING.md.
What To Include
- Truthmark version or commit
- Node.js and npm versions
- operating system
- the command or workflow you ran
- relevant snippets from
.truthmark/config.yml, routes, truth docs, or generated surfaces - expected behavior and actual behavior
Do not include secrets, private repository content, tokens, or exploitable security details in public issues. Use SECURITY.md for vulnerability reports.