[DO NOT MERGE] GHCP — Crawl: Ex15 Resilience and Failure Tests

[nikhil2611]

Summary

Added error-mapping rescue block to knife status#run so HTTP 5xx and network failures produce a clear fatal message + exit 1 instead of a raw stack trace. Added 2 failure tests proving both paths.

Evidence

bundle exec rspec spec/unit/knife/status_spec.rb
23 examples, 0 failures

bundle exec cookstyle --chefstyle -c .rubocop.yml
376 files inspected, no offenses detected

Failure tests:

• when the Chef Server returns an HTTP error → ui.fatal + exit 1 ✅
• when the network is unreachable (SocketError) → ui.fatal + exit 1 ✅

Review Focus

• lib/chef/knife/status.rb lines 76–90 — begin/rescue block wrapping search; verify two rescue clauses
• spec/unit/knife/status_spec.rb — "resilience: error mapping" context (last 20 lines)
• ai-track-docs/resilience.md — documents failure modes, code location, and why error mapping over retry

Verification Steps

bundle exec rspec spec/unit/knife/status_spec.rb -e "resilience"
# Expect: 2 examples, 0 failures

bundle exec rspec spec/unit/knife/status_spec.rb
# Expect: 23 examples, 0 failures

Risk

Low — rescue clauses only trigger on exception; happy path is unchanged. Scoped to knife status.

Rollback

git revert HEAD