)]}'
{"doc/source/contributor/index.rst":[{"robot_id":"zuul","robot_run_id":"75bdc347c2e34148b1f6c591d5ab052f","url":"https://zuul.teim.app/t/main/buildset/75bdc347c2e34148b1f6c591d5ab052f","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":"576ff61d202ff168db6409e3b1233eefc73fad8c","patch_set":5,"id":"a3071b27_5b346112","line":19,"updated":"2026-04-10 10:26:51.000000000","message":"The contributor/index.rst now has a visible \u0027Contributing\u0027 section (lines 19-29) that duplicates the heading implicitly created by the toctree inclusion of \u0027contributing\u0027 (which renders as \u0027So You Want to Contribute...\u0027). The new section sits directly above the toctree output, creating two visually adjacent sections with similar scope.\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: The contributor index page will render with a \u0027Contributing\u0027 section containing a bulleted list of links, followed immediately by the toctree-rendered \u0027So You Want to Contribute...\u0027 section. This creates a confusing reading experience with overlapping content.\n\n**Suggestion**:\nConsider using a different section title such as \u0027Development Environment Setup\u0027 or \u0027Getting Started\u0027 for the new bulleted list to distinguish it from the toctree-rendered contributing.rst content. Alternatively, integrate these links into the existing contributing.rst document.","commit_id":"84d75397233587fac646c5886a9801c49d8afd14"}],"doc/source/index.rst":[{"robot_id":"zuul","robot_run_id":"7a05ae6c580945c08dd843d5f1717be6","url":"https://zuul.teim.app/t/main/buildset/7a05ae6c580945c08dd843d5f1717be6","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":"aa8970b458ed6e166e900ac8fd525e34805244ba","patch_set":1,"id":"f69b407a_6d196274","line":1,"updated":"2026-04-01 11:01:08.000000000","message":"Commit subject line \u0027Add user guide for creating instances with accelerators\u0027 is 55 characters, exceeding the OpenStack standard limit of 50 characters.\n\n**Severity**: WARNING | **Confidence**: 0.9\n\n**Impact**: Violates the OpenStack commit message convention. While this is documentation-only and not a functional issue, consistent commit hygiene is expected across all patches.\n\n**Suggestion**:\nShorten the subject to fit within 50 characters. For example: \u0027Add user guide for accelerators\u0027 (31 chars) or \u0027Add accelerator instance guide\u0027 (30 chars). This requires amending the commit.","commit_id":"c4adb6be21b57732c2af2280e23ec8b7582004dd"},{"robot_id":"zuul","robot_run_id":"7a05ae6c580945c08dd843d5f1717be6","url":"https://zuul.teim.app/t/main/buildset/7a05ae6c580945c08dd843d5f1717be6","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":"aa8970b458ed6e166e900ac8fd525e34805244ba","patch_set":1,"id":"9c3b2cf0_509d0b95","line":1,"updated":"2026-04-01 11:01:08.000000000","message":"The commit message body explains WHAT was added but does not clearly explain WHY (the user pain point or motivation). Good OpenStack commit messages should explain the problem being solved.\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Better commit messages help reviewers and future readers understand the motivation and context of changes.\n\n**Recommendation**:\nConsider adding a sentence to the commit body explaining the motivation, e.g., that users previously had no single document showing the end-to-end workflow from device discovery to instance creation with accelerators.","commit_id":"c4adb6be21b57732c2af2280e23ec8b7582004dd"},{"robot_id":"zuul","robot_run_id":"75bdc347c2e34148b1f6c591d5ab052f","url":"https://zuul.teim.app/t/main/buildset/75bdc347c2e34148b1f6c591d5ab052f","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":"576ff61d202ff168db6409e3b1233eefc73fad8c","patch_set":5,"id":"3e1205b4_514f0a8b","line":14,"updated":"2026-04-10 10:26:51.000000000","message":"The new user guide is included in the main index.rst toctree between \u0027architecture\u0027 and \u0027usage\u0027. The existing \u0027usage.rst\u0027 is a placeholder with minimal content (just an import statement). Consider whether using-cyborg.rst should replace or be positioned after usage.rst.\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Better documentation organization by reducing redundancy and providing a clearer content hierarchy for users.\n\n**Recommendation**:\nConsider expanding usage.rst to serve as the general usage overview, or moving its content into using-cyborg.rst. The current placement between architecture and usage may confuse readers about the relationship between the two files.","commit_id":"84d75397233587fac646c5886a9801c49d8afd14"}],"doc/source/user/using-cyborg.rst":[{"robot_id":"zuul","robot_run_id":"7a05ae6c580945c08dd843d5f1717be6","url":"https://zuul.teim.app/t/main/buildset/7a05ae6c580945c08dd843d5f1717be6","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":"aa8970b458ed6e166e900ac8fd525e34805244ba","patch_set":1,"id":"ce48a051_e63aacc1","line":17,"updated":"2026-04-01 11:01:08.000000000","message":"The Prerequisites section links to contributor docs (vm-setup, devstack_setup, nvme-driver) but these are development-focused guides. End users deploying Cyborg in production may benefit from links to the installation and configuration guides instead.\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Better navigation for production users who need installation guidance rather than development setup instructions.\n\n**Recommendation**:\nAdd a separate prerequisite link to the installation guide (install/index) for production deployments, and clarify that the contributor links are specifically for development/testing environments.","commit_id":"c4adb6be21b57732c2af2280e23ec8b7582004dd"},{"robot_id":"zuul","robot_run_id":"7a05ae6c580945c08dd843d5f1717be6","url":"https://zuul.teim.app/t/main/buildset/7a05ae6c580945c08dd843d5f1717be6","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":"aa8970b458ed6e166e900ac8fd525e34805244ba","patch_set":1,"id":"c331e152_a3b19770","line":65,"updated":"2026-04-01 11:01:08.000000000","message":"The device profile name \u0027nvme-profile\u0027 is NVMe-specific, but the guide is titled as a general \u0027Using Cyborg with Your Instance\u0027 guide. Users working with GPU or FPGA devices may be confused about whether they should use nvme-profile or create their own profile with different names.\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: Users following the guide literally may name their profiles \u0027nvme-profile\u0027 even for non-NVMe devices, creating confusing naming conventions in their deployments.\n\n**Suggestion**:\nUse a more generic profile name like \u0027accel-profile\u0027 or \u0027my-accelerator-profile\u0027 in the example, and note that the profile name is user-defined and should reflect the device type being requested. Alternatively, clearly state that \u0027nvme-profile\u0027 is just an example name.","commit_id":"c4adb6be21b57732c2af2280e23ec8b7582004dd"},{"robot_id":"zuul","robot_run_id":"7a05ae6c580945c08dd843d5f1717be6","url":"https://zuul.teim.app/t/main/buildset/7a05ae6c580945c08dd843d5f1717be6","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":"aa8970b458ed6e166e900ac8fd525e34805244ba","patch_set":1,"id":"a21822b3_6834e28c","line":124,"updated":"2026-04-01 11:01:08.000000000","message":"The SSH keypair section presents two nearly identical code blocks for creating a keypair. The first block includes ssh-keygen plus the keypair create command (for users without a key), while the second repeats only the keypair create command (for users who already have a key). The practical distinction is minimal since openstack keypair create --public-key is idempotent.\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: The duplicated code block adds noise without meaningful benefit. Users may wonder why the same command appears twice with slightly different framing.\n\n**Suggestion**:\nMerge the two code blocks into a single concise section that first shows ssh-keygen (with a note that it can be skipped if a key already exists), then shows the openstack keypair create command once.","commit_id":"c4adb6be21b57732c2af2280e23ec8b7582004dd"},{"robot_id":"zuul","robot_run_id":"7a05ae6c580945c08dd843d5f1717be6","url":"https://zuul.teim.app/t/main/buildset/7a05ae6c580945c08dd843d5f1717be6","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":"aa8970b458ed6e166e900ac8fd525e34805244ba","patch_set":1,"id":"2f7c20f7_6ff7d681","line":160,"updated":"2026-04-01 11:01:08.000000000","message":"The guide uses \u0027--network private\u0027 without explaining that the user needs an existing network named \u0027private\u0027. In a fresh DevStack installation this network typically exists, but users on other deployments may need to substitute their actual network name or UUID.\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Prevents instance creation failures for users who do not have a network named \u0027private\u0027 in their OpenStack deployment.\n\n**Recommendation**:\nAdd a brief note before the server create command explaining that \u0027private\u0027 is the default DevStack network name and users should substitute their own network name if different. Consider adding an \u0027openstack network list\u0027 step.","commit_id":"c4adb6be21b57732c2af2280e23ec8b7582004dd"},{"robot_id":"zuul","robot_run_id":"7a05ae6c580945c08dd843d5f1717be6","url":"https://zuul.teim.app/t/main/buildset/7a05ae6c580945c08dd843d5f1717be6","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":"aa8970b458ed6e166e900ac8fd525e34805244ba","patch_set":1,"id":"4c547854_881b0524","line":195,"updated":"2026-04-01 11:01:08.000000000","message":"The document references a non-existent \u0027Troubleshooting section below\u0027 at the end of the Verifying Accelerator Attachment section, but no Troubleshooting section exists anywhere in using-cyborg.rst. This is a broken reference that will confuse users who encounter a BindFailed state and try to follow the instruction.\n\n**Severity**: HIGH | **Confidence**: 1.0\n\n**Risk**: Users encountering BindFailed state will be unable to find the referenced troubleshooting guidance, leading to confusion and inability to resolve accelerator attachment failures.\n\n**Priority**: Before merge\n**Why This Matters**: A dangling reference to non-existent content undermines document reliability and creates a poor user experience when troubleshooting fails.\n\n**Recommendation**:\nEither add a Troubleshooting section to using-cyborg.rst covering common failure states (BindFailed, CreateFailed, etc.) with resolution steps, or remove the reference and replace it with a more general suggestion to check Cyborg service logs (e.g., journalctl -u devstack@cyborg-agent).","commit_id":"c4adb6be21b57732c2af2280e23ec8b7582004dd"},{"robot_id":"zuul","robot_run_id":"a0fb7f954fc14ebfabb1bcff8f82cd86","url":"https://zuul.teim.app/t/main/buildset/a0fb7f954fc14ebfabb1bcff8f82cd86","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":"20c47b68150954e02d147fc68c786f27638f8b4c","patch_set":2,"id":"f730a432_db849bc1","line":17,"updated":"2026-04-10 07:59:53.000000000","message":"The document lists contributor docs (vm-setup, devstack_setup, nvme-driver) as prerequisites. This blurs the line between user and contributor documentation and assumes the reader is setting up a development environment rather than using an existing deployment.\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: A production user with an existing Cyborg deployment may be confused by references to DevStack and VM setup. These links are useful for developers but out of scope for a pure user guide.\n\n**Suggestion**:\nRestructure the Prerequisites section to separate user prerequisites (working deployment, credentials, CLI) from a separate \u0027Setting up a test environment\u0027 callout box or note that links to contributor docs. For example, wrap the contributor links in a \u0027.. note::\u0027 directive clarifying these are for development/testing only.","commit_id":"698cd81b5ab5afc18d791de3b73c9f3a8c145400"},{"robot_id":"zuul","robot_run_id":"a0fb7f954fc14ebfabb1bcff8f82cd86","url":"https://zuul.teim.app/t/main/buildset/a0fb7f954fc14ebfabb1bcff8f82cd86","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":"20c47b68150954e02d147fc68c786f27638f8b4c","patch_set":2,"id":"5e41d2c7_113123ef","line":141,"updated":"2026-04-10 07:59:53.000000000","message":"The wget URL for the Ubuntu cloud image (line 141) is version-pinned to 24.04. This URL may become stale or redirect when newer Ubuntu LTS releases ship.\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Avoiding stale URLs reduces documentation maintenance and prevents user frustration from broken downloads.\n\n**Recommendation**:\nConsider using the Ubuntu \u0027current\u0027 redirect URL (https://cloud-images.ubuntu.com/noble/current/) or add a note that users should check for the latest image version. Alternatively, simply reference the Ubuntu cloud images page and let users choose.","commit_id":"698cd81b5ab5afc18d791de3b73c9f3a8c145400"},{"robot_id":"zuul","robot_run_id":"a0fb7f954fc14ebfabb1bcff8f82cd86","url":"https://zuul.teim.app/t/main/buildset/a0fb7f954fc14ebfabb1bcff8f82cd86","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":"20c47b68150954e02d147fc68c786f27638f8b4c","patch_set":2,"id":"cf6adbef_31e61b2d","line":145,"updated":"2026-04-10 07:59:53.000000000","message":"The guide uses the --public flag when creating the image (line 145) which requires admin privileges. This is not called out and may fail for non-admin users.\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Making privilege requirements explicit prevents errors for non-admin users following the guide.\n\n**Recommendation**:\nAdd a note explaining that --public requires admin privileges, or remove --public and add a note that admin users can add --public to share the image. Example: \u0027--public requires admin credentials; omit this flag for a private image.\u0027","commit_id":"698cd81b5ab5afc18d791de3b73c9f3a8c145400"},{"robot_id":"zuul","robot_run_id":"a0fb7f954fc14ebfabb1bcff8f82cd86","url":"https://zuul.teim.app/t/main/buildset/a0fb7f954fc14ebfabb1bcff8f82cd86","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":"20c47b68150954e02d147fc68c786f27638f8b4c","patch_set":2,"id":"f126808e_8b186f1f","line":195,"updated":"2026-04-10 07:59:53.000000000","message":"Line 195 references a \u0027Troubleshooting section below\u0027 but no such section exists in the document. This is a broken internal reference that will confuse readers.\n\n**Severity**: HIGH | **Confidence**: 1.0\n\n**Risk**: Readers encountering a BindFailed state will look for a Troubleshooting section that does not exist, leaving them without guidance for a common failure scenario.\n\n**Priority**: Before merge\n**Why This Matters**: Broken cross-references undermine documentation credibility and user trust. The guide promises help it does not deliver at the point where users need it most.\n\n**Recommendation**:\nEither add a Troubleshooting section at the end of the document (before or after \u0027Deleting Instances\u0027) covering common failure modes such as BindFailed, Initial state stuck, and device not found errors. Alternatively, change the text to refer to the nvme-driver.rst Troubleshooting section: \u0027see :doc:`/contributor/nvme-driver` for troubleshooting\u0027.","commit_id":"698cd81b5ab5afc18d791de3b73c9f3a8c145400"},{"robot_id":"zuul","robot_run_id":"75bdc347c2e34148b1f6c591d5ab052f","url":"https://zuul.teim.app/t/main/buildset/75bdc347c2e34148b1f6c591d5ab052f","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":"576ff61d202ff168db6409e3b1233eefc73fad8c","patch_set":5,"id":"9caf4853_821cfe81","line":18,"updated":"2026-04-10 10:26:51.000000000","message":"The \u0027Prerequisites\u0027 section links to contributor-only docs (vm-setup, devstack_setup, nvme-driver) which are under doc/source/contributor/. For a user-facing guide, these cross-references may be confusing since the user section is intended for end users.\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Clarifies the intended audience and avoids directing end users to contributor-focused development documentation that may contain irrelevant details.\n\n**Recommendation**:\nAdd a clarifying note before the links, for example: \u0027If you are setting up a development or testing environment from scratch, the following contributor guides may help:\u0027 This sets proper expectations that these links are development-oriented.","commit_id":"84d75397233587fac646c5886a9801c49d8afd14"},{"robot_id":"zuul","robot_run_id":"75bdc347c2e34148b1f6c591d5ab052f","url":"https://zuul.teim.app/t/main/buildset/75bdc347c2e34148b1f6c591d5ab052f","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":"576ff61d202ff168db6409e3b1233eefc73fad8c","patch_set":5,"id":"107d9832_e8be6b09","line":30,"updated":"2026-04-10 10:26:51.000000000","message":"The device list example output uses specific UUIDs and hostnames. Consider adding a note that actual output will differ by deployment to set proper user expectations.\n\n**Severity**: SUGGESTION | **Confidence**: 0.6\n\n**Benefit**: Prevents users from being concerned when their output does not match the examples exactly.\n\n**Recommendation**:\nAdd a brief note before the first CLI example: \u0027The following examples show sample output. Your UUIDs, device types, and hostnames will differ based on your deployment.\u0027","commit_id":"84d75397233587fac646c5886a9801c49d8afd14"},{"robot_id":"zuul","robot_run_id":"75bdc347c2e34148b1f6c591d5ab052f","url":"https://zuul.teim.app/t/main/buildset/75bdc347c2e34148b1f6c591d5ab052f","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":"576ff61d202ff168db6409e3b1233eefc73fad8c","patch_set":5,"id":"385cb738_33443061","line":49,"updated":"2026-04-10 10:26:51.000000000","message":"Device attribute list output shows \u0027traits1\u0027 (plural with \u0027s\u0027) on line 49 while all other trait entries use \u0027trait0\u0027 (singular). This is likely a typo in the sample output and inconsistent with Cyborg\u0027s actual attribute key naming.\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: Users may be confused by inconsistent attribute key naming and may wonder whether the key naming convention varies. This could lead them to file bugs or waste time investigating.\n\n**Suggestion**:\nChange \u0027traits1\u0027 to \u0027trait1\u0027 on line 49 to follow the singular naming convention used by all other trait entries in the same table. Verify against actual Cyborg output to ensure sample data accuracy.","commit_id":"84d75397233587fac646c5886a9801c49d8afd14"},{"robot_id":"zuul","robot_run_id":"75bdc347c2e34148b1f6c591d5ab052f","url":"https://zuul.teim.app/t/main/buildset/75bdc347c2e34148b1f6c591d5ab052f","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":"576ff61d202ff168db6409e3b1233eefc73fad8c","patch_set":5,"id":"d5bfff2b_38e903c8","line":137,"updated":"2026-04-10 10:26:51.000000000","message":"The guide uses Ubuntu 24.04 as the example cloud image but does not mention that any cloud-enabled image would work. Adding a brief note about image requirements would make the guide more broadly applicable.\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Users who prefer other distributions (CentOS, Debian, etc.) will understand they can substitute their preferred image without confusion.\n\n**Recommendation**:\nAdd a brief note after the image create step: \u0027You can use any cloud-init enabled image. Adjust the image name and URL accordingly.\u0027","commit_id":"84d75397233587fac646c5886a9801c49d8afd14"},{"robot_id":"zuul","robot_run_id":"75bdc347c2e34148b1f6c591d5ab052f","url":"https://zuul.teim.app/t/main/buildset/75bdc347c2e34148b1f6c591d5ab052f","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":"576ff61d202ff168db6409e3b1233eefc73fad8c","patch_set":5,"id":"d32bf452_adcdc158","line":141,"updated":"2026-04-10 10:26:51.000000000","message":"The wget command on line 141 exceeds the typical documentation line length of 100 characters (103 chars including the console prompt). While inside a code-block, this may cause horizontal scrolling in rendered HTML output.\n\n**Severity**: WARNING | **Confidence**: 0.7\n\n**Impact**: Long lines in code blocks may cause horizontal scrolling in rendered documentation, degrading readability especially on smaller screens.\n\n**Suggestion**:\nBreak the wget command using shell line continuation or use a shortened URL to keep the line under 100 characters.","commit_id":"84d75397233587fac646c5886a9801c49d8afd14"},{"robot_id":"zuul","robot_run_id":"75bdc347c2e34148b1f6c591d5ab052f","url":"https://zuul.teim.app/t/main/buildset/75bdc347c2e34148b1f6c591d5ab052f","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":"576ff61d202ff168db6409e3b1233eefc73fad8c","patch_set":5,"id":"51cb48c3_896a0124","line":195,"updated":"2026-04-10 10:26:51.000000000","message":"Line 195 references \u0027Troubleshooting section below\u0027 but no Troubleshooting section exists in the document. Readers encountering a BindFailed state have nowhere to go.\n\n**Severity**: HIGH | **Confidence**: 1.0\n\n**Risk**: Users following the guide who hit a BindFailed error will reach a dead-end reference, undermining trust in the documentation.\n\n**Priority**: Before merge\n**Why This Matters**: Broken internal references in documentation are high priority because they represent a promise to the reader that is not fulfilled. This is especially important for a troubleshooting path.\n\n**Recommendation**:\nEither add a Troubleshooting section after \u0027Deleting Instances\u0027 that covers common BindFailed causes (e.g., device already in use, insufficient permissions, conductor not running), or remove the forward reference and instead add a note like \u0027Check Cyborg logs on the conductor host for details\u0027.","commit_id":"84d75397233587fac646c5886a9801c49d8afd14"},{"robot_id":"zuul","robot_run_id":"75bdc347c2e34148b1f6c591d5ab052f","url":"https://zuul.teim.app/t/main/buildset/75bdc347c2e34148b1f6c591d5ab052f","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":"576ff61d202ff168db6409e3b1233eefc73fad8c","patch_set":5,"id":"65ccecdc_badfa567","line":197,"updated":"2026-04-10 10:26:51.000000000","message":"The \u0027Deleting Instances\u0027 section shows verification steps but does not mention what to do if the instance delete fails or if ARQs remain in a non-terminal state after deletion.\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Users will have a clear path forward if cleanup does not complete as expected, reducing support burden.\n\n**Recommendation**:\nAdd a brief note about force-deleting instances and manual ARQ cleanup commands for edge cases, or cross-reference a Troubleshooting section if one is added.","commit_id":"84d75397233587fac646c5886a9801c49d8afd14"}]}