feat(backend/sdoc_source_code): Support merging sdoc nodes with soure nodes

[haxtibal]

This allows to have a (maybe incomplete) definition of a requirement anywhere in the static document tree which is then merged with content from annotated source code at runtime. Previously, StrictDoc would always have auto-generated a new node in an auto-determined document position.

Match criterion is currently the UID. This should be enhanced to MID in an upcoming change.

If the grammar element of sdoc and source code node are different, an error will be raised.

There are two use cases:

• Control the position (document, section) of a generated source node, as opposed to letting the node generator use an auto generated section.
• Support "side-car" files where parts of a requirement are defined in *.sdoc, while other parts of the same requirement are inlined with source code. This is a concept from the Linux kernel requirement template proposal.

The PR includes two related changes as groundwork. Let me know if you prefer separate pull requests.

• Bugfix to make source node file matching work on Windows. The issue existed for long, but went unnoticed since our tests didn't check field values in the rendered docs.
• Introduce GraphDatabase API to check for presence of a particular link nodeA <-> nodeB.

[stanislaw]

The change looks good. Just one cosmetic comment.

[stanislaw]

The change looks good. Just one cosmetic comment.

Regarding the requirements work, feel free to leave it to me, so that merging of this technical work is not blocked. We can polish the L1/L2 missing requirements separately and later.

[haxtibal]

Test fails on Windows, but works on Linux? My spontaneous idea is that this has something to do with the UID from file path construction. Maybe some drive letter or backslash has made it into the UID. Do you have a Windows machine to verify? I sadly don't... The expected UID in my test is SRC-NODES-BASE/src/example/example.c/example_1.

[stanislaw]

Test fails on Windows, but works on Linux? My spontaneous idea is that this has something to do with the UID from file path construction. Maybe some drive letter or backslash has made it into the UID. Do you have a Windows machine to verify? I sadly don't... The expected UID in my test is SRC-NODES-BASE/src/example/example.c/example_1.

I have a Windows machine but I usually avoid opening it 😄

Let me take a look, most of the time it is backward slashes that must be converted to forward slashes.

[stanislaw]

Test fails on Windows, but works on Linux? My spontaneous idea is that this has something to do with the UID from file path construction. Maybe some drive letter or backslash has made it into the UID. Do you have a Windows machine to verify? I sadly don't... The expected UID in my test is SRC-NODES-BASE/src/example/example.c/example_1.

I have a Windows machine but I usually avoid opening it 😄

Let me take a look, most of the time it is backward slashes that must be converted to forward slashes.

I pushed some basic first WIP/DEBUG checks here to not interfere with your branch: https://github.com/strictdoc-project/strictdoc/actions/runs/18953531691/job/54124265424?pr=2540.

[stanislaw]

Test fails on Windows, but works on Linux? My spontaneous idea is that this has something to do with the UID from file path construction. Maybe some drive letter or backslash has made it into the UID. Do you have a Windows machine to verify? I sadly don't... The expected UID in my test is SRC-NODES-BASE/src/example/example.c/example_1.

I have a Windows machine but I usually avoid opening it 😄
Let me take a look, most of the time it is backward slashes that must be converted to forward slashes.

I pushed some basic first WIP/DEBUG checks here to not interfere with your branch: https://github.com/strictdoc-project/strictdoc/actions/runs/18953531691/job/54124265424?pr=2540.

Basic debugging doesn't show anything useful 🤔 I will turn on the Windows machine hopefully today still.

[haxtibal]

Test fails on Windows, but works on Linux? My spontaneous idea is that this has something to do with the UID from file path construction. Maybe some drive letter or backslash has made it into the UID. Do you have a Windows machine to verify? I sadly don't... The expected UID in my test is SRC-NODES-BASE/src/example/example.c/example_1.

I have a Windows machine but I usually avoid opening it 😄
Let me take a look, most of the time it is backward slashes that must be converted to forward slashes.

I pushed some basic first WIP/DEBUG checks here to not interfere with your branch: https://github.com/strictdoc-project/strictdoc/actions/runs/18953531691/job/54124265424?pr=2540.

Basic debugging doesn't show anything useful 🤔 I will turn on the Windows machine hopefully today still.

Thanks!

I've also just added a Debug commit on top to run only the failing test, with print debug added, and stdout/stderr from strictdoc visible.

EDIT1: ... and it doesn't fail 🤔 I've rebased this on top of the has_link change, but that shouldn't change anything. Debug output shows

SRC-NODES-BASE/src/example/example.c/example_1 found in docs, merging with source node from src/example/example.c

so not a file name issue.

...

EDIT 4: Getting closer. The SourceNode passed to merge_sdoc_node_with_source_node has good metadata, but it has no fields. How can that be?

SourceNode(..., fields={}, ...)

EDIT 5: Fixed with 86a4951.