Skip to content

feat(guardrails): enforce guardrails in workflow entry points#17

Closed
mikehostetler wants to merge 1 commit intomainfrom
feature/guardrails-workflow-enforcement
Closed

feat(guardrails): enforce guardrails in workflow entry points#17
mikehostetler wants to merge 1 commit intomainfrom
feature/guardrails-workflow-enforcement

Conversation

@mikehostetler
Copy link
Contributor

Summary

  • add mix jido_shell.guardrails as a first-class namespace/layout validation task
  • introduce guardrail rules for legacy path detection, required session module layout, and namespace prefix consistency
  • enforce guardrails in scripted workflows via:
    • mix quality alias
    • CI guardrails job
  • document contributor guardrail expectations
  • add dedicated tests for rule behavior and mix-task failure surfacing

Validation

  • mix test test/jido/shell/guardrails_test.exs test/mix/tasks/jido_shell.guardrails_test.exs --seed 0
  • mix test --seed 0
  • mix quality
  • mix jido_shell.guardrails

Closes #15

@mikehostetler
Copy link
Contributor Author

Superseded by #19.

main moved (layout migration + guardrail refactor), which left this branch in a dirty merge state. The replacement PR lands the remaining guardrail workflow/extension work cleanly on top of current main.

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.

chore: enforce jido_shell guardrails in generator/script workflows

1 participant