@juangcarmona/lighthouse-sdlc 0.6.0 → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,41 @@
1
+ ---
2
+ # Owned by @juangcarmona/lighthouse-sdlc. Compile with `gh aw compile`; do not edit the lock file.
3
+ name: Lighthouse SDLC integrate
4
+ description: Execute only the Lighthouse integration stage and return its declared stage result.
5
+ private: true
6
+ runs-on: [self-hosted, linux, lighthouse-sdlc]
7
+ runs-on-slim: ubuntu-24.04
8
+ strict: true
9
+ env:
10
+ LIGHTHOUSE_STAGE: integrate
11
+ LIGHTHOUSE_SKILL: src/packages/sdlc/skills/integrate/SKILL.md
12
+ on:
13
+ workflow_call:
14
+ inputs:
15
+ route:
16
+ description: Lighthouse route selected by the host.
17
+ required: true
18
+ type: string
19
+ run-id:
20
+ description: Stable Lighthouse run identifier.
21
+ required: true
22
+ type: string
23
+ input:
24
+ description: Compact JSON input for this stage.
25
+ required: false
26
+ type: string
27
+ default: '{}'
28
+ previous-stage:
29
+ description: Previous stage artifact name.
30
+ required: false
31
+ type: string
32
+ default: implement
33
+ imports:
34
+ - shared/lighthouse-sdlc-stage.md
35
+ ---
36
+
37
+ # Lighthouse SDLC integrate worker
38
+
39
+ Execute only `integrate` by following `${{ env.LIGHTHOUSE_SKILL }}` and reading the implementation result from `/tmp/gh-aw/agent/previous/stage-result.json` when present; for a supervised run, use the predecessor context in `/tmp/gh-aw/agent/input.json`. Recheck Done evidence, dependencies, branch, pull request and required checks.
40
+
41
+ Prepare the configured merge or stacked-change action and leave protected or human decisions explicit. Do not merge unless the selected route and repository policy authorize it. Write one valid result to `/tmp/gh-aw/agent/stage-result.json` with `stage: integrate`, `gate: done`, the integration record in `output`, and separate evidence arrays. Do not invoke `review`; stop at the configured merge preparation, then call `noop` exactly once.