)]}'
{"doc/source/images/train/nova-cyborg-interaction.seqdiag":[{"robot_id":"zuul","robot_run_id":"c72550750128465da3534a6570dade84","url":"https://zuul.teim.app/t/main/buildset/c72550750128465da3534a6570dade84","author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"576980330ea5823aa4ed4c2c49ce7bdfc9d47c82","patch_set":1,"id":"944aa08f_e6628aff","line":1,"updated":"2026-02-26 12:09:09.000000000","message":"Consider adding a README or comment in the images directory explaining the presence of .seqdiag files\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Future maintainers will understand why .seqdiag source files are kept alongside the pre-generated SVG files, and whether they should be regenerated if changes are needed\n\n**Recommendation**:\nAdd a README.md file in doc/source/images/ (or individual train/ussuri subdirectories) explaining that .seqdiag files are retained for reference but are not actively built due to the sphinxcontrib.seqdiag dependency removal. Include instructions on how to regenerate SVGs if needed (e.g., using an alternative tool or manually).","commit_id":"9433e61f01f432f049afc13479c978604790f7c8"},{"robot_id":"zuul","robot_run_id":"c72550750128465da3534a6570dade84","url":"https://zuul.teim.app/t/main/buildset/c72550750128465da3534a6570dade84","author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"576980330ea5823aa4ed4c2c49ce7bdfc9d47c82","patch_set":1,"id":"fd6629ca_104e154e","line":1,"updated":"2026-02-26 12:09:09.000000000","message":"Consider adding a git attributes entry to mark .seqdiag files as linguist-generated or similar\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: This helps GitHub and other tools understand that .seqdiag files are documentation source rather than active code, potentially improving language statistics and file recognition\n\n**Recommendation**:\nCreate a .gitattributes file with an entry like: \u0027**/*.seqdiag linguist-documentation\u0027 to properly categorize these files. This is optional and cosmetic, but helps with repository organization.","commit_id":"9433e61f01f432f049afc13479c978604790f7c8"},{"robot_id":"zuul","robot_run_id":"8a649b84141d484cbe1ae67780644198","url":"https://zuul.teim.app/t/main/buildset/8a649b84141d484cbe1ae67780644198","author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"c299f5fe1682bf440f453e3990379a8b51d66205","patch_set":2,"id":"f42101e6_a24d44b6","line":1,"updated":"2026-02-26 13:01:50.000000000","message":"The seqdiag source files (.seqdiag) were added as new files, but it would be helpful to add a comment in each file explaining they are source files for the SVGs and how to regenerate if needed\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Improves maintainability by providing context for future developers who may need to update the diagrams\n\n**Recommendation**:\nAdd a header comment to each .seqdiag file indicating: \u0027This is the source seqdiag file for the corresponding SVG. To regenerate, install sphinxcontrib-seqdiag and run seqdiag command.\u0027","commit_id":"9edd8e7c861b5f9e59e4f0e38a99d6374fb7d5b7"}]}