@mriekki/project-forge 4.15.1 → 4.15.2
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/assets/components.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": 2,
|
|
3
3
|
"package": "@mriekki/project-forge",
|
|
4
|
-
"version": "4.15.
|
|
4
|
+
"version": "4.15.2",
|
|
5
5
|
"defaultProfile": "greenfield-project",
|
|
6
6
|
"profiles": {
|
|
7
7
|
"greenfield-project": {
|
|
@@ -13,7 +13,7 @@
|
|
|
13
13
|
},
|
|
14
14
|
"components": {
|
|
15
15
|
"core": {
|
|
16
|
-
"revision": "
|
|
16
|
+
"revision": "4c74c1801b82d3aa438447d392024d32ca5697b0",
|
|
17
17
|
"version": "4.0.0",
|
|
18
18
|
"distribution": "greenfield-workspace",
|
|
19
19
|
"descriptor": "assets/core/distribution.json",
|
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": 2,
|
|
3
3
|
"package": "@mriekki/project-forge",
|
|
4
|
-
"version": "4.15.
|
|
4
|
+
"version": "4.15.2",
|
|
5
5
|
"components": {
|
|
6
6
|
"core": {
|
|
7
|
-
"revision": "
|
|
7
|
+
"revision": "4c74c1801b82d3aa438447d392024d32ca5697b0",
|
|
8
8
|
"version": "4.0.0",
|
|
9
9
|
"distribution": "greenfield-workspace",
|
|
10
10
|
"files": [
|
|
@@ -56,7 +56,7 @@
|
|
|
56
56
|
{
|
|
57
57
|
"source": "core/skills/setup/SKILL.md",
|
|
58
58
|
"destination": ".github/skills/setup/SKILL.md",
|
|
59
|
-
"sha256": "
|
|
59
|
+
"sha256": "0e08797b2f7d7e3e3f825cbb22bdad509255a4a0b875878d4ec1d9eecd23cad2"
|
|
60
60
|
},
|
|
61
61
|
{
|
|
62
62
|
"source": "core/skills/build/SKILL.md",
|
|
@@ -46,7 +46,7 @@ From the repository root inspect only what is needed:
|
|
|
46
46
|
- `PROJECT_BOOTSTRAP.json` as generation/provenance and initial topology fallback;
|
|
47
47
|
- `SCAFFOLD_PLAN.json` when present;
|
|
48
48
|
- `.github/project-forge-workspace.json` and Project Forge/component baselines when present;
|
|
49
|
-
- `scripts/setup.ps1` on Windows or `scripts/setup.sh` on macOS;
|
|
49
|
+
- `scripts/setup.ps1` on Windows or `scripts/setup.sh` on macOS/Linux; WSL2 is the supported generated Linux setup path;
|
|
50
50
|
- `tools/project-forge-vscode/work-item-status/install.py` and `docs/work-items` when present;
|
|
51
51
|
- current Git branch/status/upstream evidence so setup does not overwrite unrelated work;
|
|
52
52
|
- workstation-local setup/readiness evidence when present;
|
|
@@ -104,8 +104,9 @@ Do not silently repair state during `status`.
|
|
|
104
104
|
Select the launcher for the actual workstation OS:
|
|
105
105
|
|
|
106
106
|
```text
|
|
107
|
-
Windows
|
|
108
|
-
macOS
|
|
107
|
+
Windows -> .\scripts\setup.ps1
|
|
108
|
+
macOS -> ./scripts/setup.sh
|
|
109
|
+
Linux/WSL2 -> ./scripts/setup.sh
|
|
109
110
|
```
|
|
110
111
|
|
|
111
112
|
For normal setup, run the launcher with repository restore enabled when supported:
|
|
@@ -147,7 +148,6 @@ python tools/project-forge-vscode/work-item-status/install.py install --json
|
|
|
147
148
|
```
|
|
148
149
|
|
|
149
150
|
This installation is already authorized by `/setup` as routine workstation preparation; do not require a second `/work-item-status enable` confirmation. The installer may replace older versions of this same Project Forge extension only and must not install unrelated extensions, alter Project files, or change Git/GitHub state.
|
|
150
|
-
|
|
151
151
|
If the result has `reloadRequired: true`, tell the developer to reload VS Code once after setup. Do not repeatedly reinstall an already-ready version merely because the editor has not yet been reloaded.
|
|
152
152
|
|
|
153
153
|
If a Project has local `docs/work-items` but the package-managed installer is absent, report:
|
|
@@ -447,7 +447,6 @@ Never silently edit `sshd`, widen account/source policy, disable host verificati
|
|
|
447
447
|
A verified workstation-to-target access relationship may be reused by multiple Projects/environments that bind to the same logical target. Environment proof remains specific to the Project + named environment + target + adapter/isolation contract.
|
|
448
448
|
|
|
449
449
|
When Staging and Production share one physical target, explicitly surface the shared failure domain and verify that their Project/environment-owned runtime identity, compose project, route/port allocation, persistence paths, and locking cannot collide. Staging evidence does not become Production evidence merely because the host is shared.
|
|
450
|
-
|
|
451
450
|
## 8. Prove supported remote mechanics with a disposable Project Forge probe
|
|
452
451
|
|
|
453
452
|
When the installed Deployment Kit exposes environment proof operations, a selected remote environment should normally be taken through an end-to-end **environment proof deployment** during setup.
|