chore: enforce jido_shell guardrails in generator/script workflows

[mikehostetler]

Context

jido_shell guardrails are implemented and wired into mix quality, but generator/script-driven code paths can still bypass early enforcement if they do not invoke guardrails during generation workflows.

Goal

Ensure code generation and script workflows run mix jido_shell.guardrails automatically so namespace/layout regressions are blocked before review.

Scope

• Identify generator/script entry points used in this repo.
• Add guardrail invocation to those workflows (or shared wrapper task).
• Document the expected workflow for contributors.

Out of Scope

• Changes to guardrail rule semantics.
• Broad CI pipeline redesign.

Acceptance Criteria

• Generator/script workflows trigger guardrail checks.
• A failing guardrail case is detectable from generation flow.
• Contributor docs describe guardrail expectations.
• mix test and mix quality remain green.

References

• specs/refactor-plans/jido_shell.md (Residual Risks and Next Trigger)

[mikehostetler]

Implemented in #17.\n\nThis adds jido_shell guardrails: ok, wires guardrails into jido_shell guardrails: ok
Checking 93 source files (this might take a while) ...

Please report incorrect results: https://github.com/rrrene/credo/issues

Analysis took 0.02 seconds (0.02s to load, 0.00s running 0 checks on 93 files)
656 mods/funs, found no issues.

Showing priority issues: ↑ ↗ → (use mix credo explain to explain issues, mix credo --help for options).
Finding suitable PLTs
Checking PLT...
[:asn1, :certifi, :compiler, :cowlib, :crypto, :eex, :elixir, :eternal, :ex_aws, :ex_aws_s3, :excoveralls, :finch, :git_cli, :glob_ex, :gun, :hackney, :hpax, :httpoison, :idna, :igniter, :inets, :jason, :jido_shell, :jido_vfs, :kernel, :logger, :metrics, :mime, :mimerl, :mint, :nimble_options, :nimble_pool, :owl, :parse_trans, :phx_new, :public_key, :req, :rewrite, :sourceror, :spitfire, :splode, :sprites, :ssl, :ssl_verify_fun, :stdlib, :stream_data, :sweet_xml, :syntax_tools, :telemetry, :tentacat, :text_diff, :tools, :unicode_util_compat, :uniq, :xmerl, :zoi]
PLT is up to date!
ignore_warnings: .dialyzer_ignore.exs

Starting Dialyzer
[
check_plt: false,
init_plt: ~c"priv/plts/project.plt/dialyxir_erlang-28.3.2_elixir-1.19.5_deps-dev.plt",
files: [~c"/Users/mhostetler/Source/Jido/jido_shell/_build/dev/lib/jido_shell/ebin/Elixir.Jido.Shell.Backend.beam",
~c"/Users/mhostetler/Source/Jido/jido_shell/_build/dev/lib/jido_shell/ebin/Elixir.Jido.Shell.SessionServer.beam",
~c"/Users/mhostetler/Source/Jido/jido_shell/_build/dev/lib/jido_shell/ebin/Elixir.Jido.Shell.Command.Ls.beam",
~c"/Users/mhostetler/Source/Jido/jido_shell/_build/dev/lib/jido_shell/ebin/Elixir.Jido.Shell.Session.State.beam",
~c"/Users/mhostetler/Source/Jido/jido_shell/_build/dev/lib/jido_shell/ebin/Elixir.Jido.Shell.Command.Parser.beam",
...],
...
]
Total errors: 11, Skipped: 11, Unnecessary Skips: 0
done in 0m3.29s
done (passed successfully) and CI workflow entry points, and adds rule/task coverage to catch namespace/layout regressions early.