Fix hardcoded working-directory: code; add working_dir input

[eliran-ops]

Summary

• Drop hardcoded working-directory: code from the resolve step. Auto-detect prefers ./code, falls back to .. New working_dir input for explicit override.
• Harden yq queries via strenv(); add services[].path as the dockerfile fallback (existing test asserted it; implementation was missing).
• Fix stale test-skyhook-config-overrides-inputs — asserted the reversed contract since PR Fix input contract: user-provided context/dockerfile override service_name resolution #5; renamed and flipped.
• Add 3 integration tests + fixture (test/fixtures/code-checkout/) covering auto-detect, explicit working_dir, trailing-slash tolerance.

Why

CI on main has been red since PR #5 (5 days). Every service_name test fails with bash: working directory '.../code' not found. The action's own repo doesn't check into code/, and neither does any non-Skyhook consumer. @v1 floating tag inherits the breakage.

No Linear issue — this is an in-session ad-hoc fix off origin/main.

Where to start reading

• action.yml:14-17 — new working_dir input.
• action.yml:199-305 — rewritten resolve step (auto-detect + normalize_path / join_path helpers + strenv()).
• .github/workflows/test.yml:269-339 — three new jobs covering the new code paths.

Risky vs mechanical

Risky — eyes here:

• Auto-detect order: code first, then .. A consumer with both ./code/.skyhook/skyhook.yaml and ./.skyhook/skyhook.yaml silently picks code/. test-skyhook-autodetect-code exercises exactly this scenario and verifies the choice.
• Behavior change: previously the action probed only code/.skyhook/skyhook.yaml. Now non-Skyhook consumers (yaml at workspace root) succeed. If anyone relied on the action failing in that case, they'll see a behavior change.
• services[].path dockerfile fallback: existing test-skyhook-path-fallback asserted this but main never implemented it (test was passing under prior different bug). This PR actually makes it work — anyone whose Dockerfile lived elsewhere and depended on the silent Dockerfile workspace-root fallback could see a diff.

Mechanical:

• yq strenv() switch (caller inputs no longer interpolated into bash via ${{ }}).
• README rows for service_name and working_dir.
• Stale test rename + assertion flip (now matches PR Fix input contract: user-provided context/dockerfile override service_name resolution #5's "inputs win" contract).
• Path normalization helpers (leading ./, multiple trailing /).

Notes

• After approval, recommend retagging @v1 (currently 1fdb7ba) so existing consumers pick the fix.
• 6 commits split logically. Squash-on-merge if preferred — no --amend per CLAUDE.md.

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes how the action locates and resolves .skyhook/skyhook.yaml and derived context/dockerfile, which can affect builds for repos with multiple candidate config locations or relying on previous fallback behavior.

Overview
Fixes service_name config resolution by removing the hardcoded working-directory: code and adding a new working_dir input; when unset, the resolver now auto-detects .skyhook/skyhook.yaml by preferring ./code and falling back to ..

Tightens and extends resolution behavior: yq lookups now use strenv() for safer querying, path joining/normalization is centralized, and services[].path is implemented as an additional Dockerfile fallback when buildTool.docker.* isn’t set.

Updates tests and docs: flips/renames the workflow test to enforce the “explicit context/dockerfile inputs override config” contract, adds three integration jobs covering auto-detect and working_dir (including trailing slashes), and documents service_name/working_dir behavior in README.md.

^{Reviewed by Cursor Bugbot for commit e94945f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[eliran-ops]

@hisco i can merge, but i'd like a review

[hisco]

This input is the only concept that should stay... the rest of the changes are not relvant.