🎨 kettle-dev v1.1.20 re-template

Author: pboling

.env.local.example

@@ -10,7 +10,7 @@ export FLOSS_FUNDING_DEBUG=false # extra logging to help diagnose issues (overri
 export AUTOGEN_FIXTURE_CLEANUP=false # autogenerated gem fixture cleanup after every RSpec run
 export GIT_HOOK_FOOTER_APPEND=false
 export GIT_HOOK_FOOTER_APPEND_DEBUG=false
-export GIT_HOOK_FOOTER_SENTINEL="⚡️ A message from a fellow meat-based-AI ⚡️"
+export GIT_HOOK_FOOTER_SENTINEL="⚡️ A message from a fellow meat-based-AI"
 
 # Tokens used by ci:act and CI helpers for reading workflow/pipeline status via APIs
 # GitHub (either GITHUB_TOKEN or GH_TOKEN will be used; fine-grained recommended)

.junie/guidelines.md

@@ -90,10 +90,13 @@ This document captures project-specific knowledge to streamline setup, testing,
   - If your code relies on environment variables that drive activation (see "Activation env vars" below), prefer using rspec-stubbed_env:
     - it does not support stubbing with blocks, but it does automatically clean up after itself.
     - outside the example:
+      ```ruby
       include_context 'with stubbed env'
+      ```
     - in a before hook, or in an example:
+      ```ruby
       stub_env("FLOSS_FUNDING_MY_NS" => "Free-as-in-beer")
-      # example code continues
+      ```
   - If your spec needs to assert on console output, tag it with :check_output. By default, STDOUT is silenced.
   - Use Timecop for deterministic time-sensitive behavior as needed (require config/timecop is already done by spec_helper).