@juangcarmona/lighthouse 0.1.0 → 0.3.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.
- package/README.md +37 -7
- package/assets/guardrails/catalog.json +46 -0
- package/assets/schemas/guardrails.schema.json +41 -0
- package/assets/schemas/lighthouse-manifest.schema.json +23 -2
- package/assets/schemas/lighthouse-upgrade.schema.json +35 -0
- package/package.json +13 -2
- package/src/guardrails.mjs +140 -0
- package/src/lighthouse.mjs +831 -39
- package/upgrades/0.3.0.md +26 -0
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
# Lighthouse 0.3.0 upgrade guide
|
|
2
|
+
|
|
3
|
+
## Prerequisites
|
|
4
|
+
|
|
5
|
+
- The repository has a valid `lighthouse.json`.
|
|
6
|
+
- The working tree is clean or the update is isolated in a reviewable branch.
|
|
7
|
+
- `.lighthouse/upgrade.json` exists and records the managed projection hashes.
|
|
8
|
+
- Node.js 22 or newer is available.
|
|
9
|
+
|
|
10
|
+
If `.lighthouse/upgrade.json` is missing, run `lighthouse reconcile --dry-run`, review the plan and then run `lighthouse reconcile --apply` to establish ownership evidence. Resolve any reported conflicts first.
|
|
11
|
+
|
|
12
|
+
## Plan the update
|
|
13
|
+
|
|
14
|
+
Run `lighthouse upgrade` to preview all Lighthouse-owned scopes. Use `lighthouse upgrade --scope harness` for `LIGHTHOUSE.md`, hooks, the guard script and the repository workflow, or use `lighthouse upgrade --scope sdlc` for the SDLC control-plane projection.
|
|
15
|
+
|
|
16
|
+
The plan reports the installed package and baseline, the selected scopes, prerequisites, file classifications, preserved content, verification command and recovery action. `lighthouse upgrade --format json` produces the same plan for a review tool or CI job.
|
|
17
|
+
|
|
18
|
+
## Apply the update
|
|
19
|
+
|
|
20
|
+
Review the plan and run `lighthouse upgrade --apply` with the same scope. Lighthouse writes only missing or provably managed projections, records the new ownership hashes and preserves customized files for review.
|
|
21
|
+
|
|
22
|
+
Run `lighthouse verify` after the update. A preserved customized projection may still report drift; resolve it through the normal repository change route before making the verification gate required.
|
|
23
|
+
|
|
24
|
+
## Recovery
|
|
25
|
+
|
|
26
|
+
If the update stops, keep the plan output and resolve the stated ownership or prerequisite issue. If a write fails, Lighthouse restores the files changed by that attempt; restore the branch or rerun the plan after correcting the reported condition.
|