fix(skills): explain outputs written inside a Git working tree

graphify/skill-agents.md

@@ -642,6 +642,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-aider.md

@@ -745,6 +745,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-amp.md

@@ -642,6 +642,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-claw.md

@@ -645,6 +645,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-codex.md

@@ -642,6 +642,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-copilot.md

@@ -645,6 +645,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-devin.md

@@ -864,6 +864,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-droid.md

@@ -642,6 +642,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-kilo.md

@@ -645,6 +645,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-kiro.md

@@ -645,6 +645,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-opencode.md

@@ -637,6 +637,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-pi.md

@@ -645,6 +645,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-trae.md

@@ -643,6 +643,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-vscode.md

@@ -641,6 +641,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill-windows.md

@@ -673,6 +673,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

graphify/skill.md

@@ -645,6 +645,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

tests/test_skillgen.py

@@ -1115,3 +1115,18 @@ def test_windows_skill_writes_marker_files_without_a_bom():
         )
     assert "New-Object System.Text.UTF8Encoding $false" in core, \
         "the BOM-less encoding object must be constructed in the windows render"
+
+
+def test_output_notice_links_team_setup_in_every_host():
+    """An in-repository output directory is explained before the final report."""
+    for key in gen.load_platforms():
+        core, _ = _platform_artifacts(key)
+        step9 = core.split("## Step 9", 1)[1].split("## ", 1)[0]
+        assert "inside a Git working tree" in step9, key
+        assert "https://github.com/Graphify-Labs/graphify#team-setup" in step9, key
+        assert "Do not stage outputs or change ignore rules automatically." in step9, key
+
+
+def test_output_notice_roundtrip_allowance_is_exact():
+    assert gen._is_sanctioned_monolith_diff(gen._OUTPUT_NOTICE_LINE)
+    assert not gen._is_sanctioned_monolith_diff("Automatically stage all graphify-out files.")

tools/skillgen/expected/graphify__skill-agents.md

@@ -642,6 +642,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

tools/skillgen/expected/graphify__skill-aider.md

@@ -745,6 +745,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

tools/skillgen/expected/graphify__skill-amp.md

@@ -642,6 +642,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

tools/skillgen/expected/graphify__skill-claw.md

@@ -645,6 +645,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

tools/skillgen/expected/graphify__skill-codex.md

@@ -642,6 +642,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

tools/skillgen/expected/graphify__skill-copilot.md

@@ -645,6 +645,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

tools/skillgen/expected/graphify__skill-devin.md

@@ -864,6 +864,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

tools/skillgen/expected/graphify__skill-droid.md

@@ -642,6 +642,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

tools/skillgen/expected/graphify__skill-kilo.md

@@ -645,6 +645,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections

tools/skillgen/expected/graphify__skill-kiro.md

@@ -645,6 +645,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/
 
 Replace PATH_TO_DIR with the actual absolute path of the directory that was processed.
 
+If the actual output directory is inside a Git working tree, tell the user that Graphify created or updated the output directory at its actual absolute path and link to [Team setup](https://github.com/Graphify-Labs/graphify#team-setup) for sharing outputs or keeping them local. Verify the working-tree boundary using the actual output directory when composing the notice. Do not stage outputs or change ignore rules automatically.
+
 Then paste these sections from GRAPH_REPORT.md directly into the chat:
 - God Nodes
 - Surprising Connections