Support Markdown Architectural Decision Records

[Arimals]

What problem does this solve?

Currently, only a single source of truth is supported for ADR, you cannot maintain a structure and have multiple records.

Proposed solution

1. Support multiple ADR record(s) by assigning a numeric value to each record and specify keywords/phrases that can be picked up in MCP queries.
2. Follow MADR specifications: https://adr.github.io/madr/decisions/0013-use-yaml-front-matter-for-meta-data.html
3. Allow records to be queried based on direct ADR tool calls and or query/searches for code that may be a result of an ADR record.

Alternatives considered

Reference MADR or individual ADR records already present in the repository. The lack of true MADR and metadata tracking limits the exposure and potential of current ADR support implementation. Doing code queries or ADR queries will not yield the desired ADR record leveraged in context searches but rather make the agent have to go and query each record mentioned in the main ADR of the indexed project.

Confirmations

• I searched existing issues and this is not a duplicate.

[DeusData]

Great addition, will check as soon as there is capacity

[DeusData]

Linking #504 here — "import existing ADR docs already present in the repo" is a subset of this MADR proposal and should be covered by the same work. Consolidating the two so they're tracked together.