Skip to content

feat(guardrails): enforce workflows and formalize extension path#19

Merged
mikehostetler merged 2 commits intomainfrom
feature/guardrails-mainline-sync
Feb 27, 2026
Merged

feat(guardrails): enforce workflows and formalize extension path#19
mikehostetler merged 2 commits intomainfrom
feature/guardrails-mainline-sync

Conversation

@mikehostetler
Copy link
Contributor

Summary

  • add explicit CI guardrails job to enforce namespace/layout checks in workflow entry points
  • extend Jido.Shell.Guardrails with pluggable rule support (default_rules/0, configured extension rules, explicit rules: option)
  • split built-in checks into rule modules for safer convention evolution
  • add GUARDRAILS.md and wire it into docs/package extras
  • update contributor/agent workflow docs with guardrail expectations and convention-change checklist
  • expand mix-task coverage (including failure path via --root) and add extension-rule tests

Validation

  • mix test test/jido/shell/guardrails_test.exs test/jido/shell/guardrails_extension_test.exs test/mix/tasks/jido_shell.guardrails_test.exs --seed 0
  • mix test --seed 0
  • mix quality
  • mix coveralls (reported total coverage: 73.2% on current mainline baseline)

Closes #15
Closes #16

@mikehostetler mikehostetler merged commit 5fb359d into main Feb 27, 2026
4 of 8 checks passed
@mikehostetler mikehostetler deleted the feature/guardrails-mainline-sync branch February 27, 2026 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs/test: formalize guardrail extension path for future namespace conventions chore: enforce jido_shell guardrails in generator/script workflows

1 participant