@mriekki/project-forge 4.11.1 → 4.11.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 +2 -2
- package/assets/generated/ASSEMBLY.json +5 -5
- package/assets/generated/core/core/process/SETUP_ACCEPTANCE_CHECKLIST.md +3 -0
- package/assets/generated/core/core/skills/setup/SKILL.md +41 -6
- package/assets/generated/core/core/skills/work-item-status/SKILL.md +7 -3
- package/package.json +1 -1
package/assets/components.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": 2,
|
|
3
3
|
"package": "@mriekki/project-forge",
|
|
4
|
-
"version": "4.11.
|
|
4
|
+
"version": "4.11.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": "78a3fbe722ea277eaad4d2082d239cd7afd3d064",
|
|
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.11.
|
|
4
|
+
"version": "4.11.2",
|
|
5
5
|
"components": {
|
|
6
6
|
"core": {
|
|
7
|
-
"revision": "
|
|
7
|
+
"revision": "78a3fbe722ea277eaad4d2082d239cd7afd3d064",
|
|
8
8
|
"version": "4.0.0",
|
|
9
9
|
"distribution": "greenfield-workspace",
|
|
10
10
|
"files": [
|
|
@@ -51,7 +51,7 @@
|
|
|
51
51
|
{
|
|
52
52
|
"source": "core/skills/setup/SKILL.md",
|
|
53
53
|
"destination": ".github/skills/setup/SKILL.md",
|
|
54
|
-
"sha256": "
|
|
54
|
+
"sha256": "d1c6e7a0a04a1fb358b136ed8f83495c27bf8959ebd8941a3d42397fa4dcbaf1"
|
|
55
55
|
},
|
|
56
56
|
{
|
|
57
57
|
"source": "core/skills/build/SKILL.md",
|
|
@@ -91,7 +91,7 @@
|
|
|
91
91
|
{
|
|
92
92
|
"source": "core/skills/work-item-status/SKILL.md",
|
|
93
93
|
"destination": ".github/skills/work-item-status/SKILL.md",
|
|
94
|
-
"sha256": "
|
|
94
|
+
"sha256": "ca79843e59e5f50785c3621b6bf8ecb7413307aefce05fec737321589792c3a9"
|
|
95
95
|
},
|
|
96
96
|
{
|
|
97
97
|
"source": "core/skills/cleanup-branches/SKILL.md",
|
|
@@ -221,7 +221,7 @@
|
|
|
221
221
|
{
|
|
222
222
|
"source": "core/process/SETUP_ACCEPTANCE_CHECKLIST.md",
|
|
223
223
|
"destination": "docs/process/SETUP_ACCEPTANCE_CHECKLIST.md",
|
|
224
|
-
"sha256": "
|
|
224
|
+
"sha256": "92174c10920f536c9912719a630e07e11c525fa2a7913d239bd097fb67f193a0"
|
|
225
225
|
},
|
|
226
226
|
{
|
|
227
227
|
"source": "core/process/OPERATION_JOURNAL.md",
|
|
@@ -31,10 +31,13 @@ After opening/reloading the intended editor workspace:
|
|
|
31
31
|
- [ ] `Reviewer` is discoverable.
|
|
32
32
|
- [ ] `Coach` is discoverable when the workspace includes coaching.
|
|
33
33
|
- [ ] expected Project Forge skills are discoverable, including `/start-work`, `/deliver`, and `/wait-what` when included by the distribution/capability set.
|
|
34
|
+
- [ ] when local `docs/work-items` folders exist, the Project Forge Work Item Status extension is installed/updated by setup and its Explorer decoration is available after any requested one-time VS Code reload; otherwise this check is not applicable.
|
|
34
35
|
- [ ] path-specific instructions are present when the workspace declares them.
|
|
35
36
|
- [ ] path-specific instructions are recognized/applied for matching files when the host supports them.
|
|
36
37
|
- [ ] the human controls the routine model/tier; the workspace does not silently pin or upgrade it.
|
|
37
38
|
|
|
39
|
+
The work-item Explorer decoration is an evidence-derived editor view, not a workflow authority. Its installation/readiness is reported separately from application runtime/build readiness.
|
|
40
|
+
|
|
38
41
|
## Copilot CLI + VS Code discovery
|
|
39
42
|
|
|
40
43
|
When GitHub Copilot CLI is an intended execution surface:
|
|
@@ -47,6 +47,7 @@ From the repository root inspect only what is needed:
|
|
|
47
47
|
- `SCAFFOLD_PLAN.json` when present;
|
|
48
48
|
- `.github/project-forge-workspace.json` and Project Forge/component baselines when present;
|
|
49
49
|
- `scripts/setup.ps1` on Windows or `scripts/setup.sh` on macOS;
|
|
50
|
+
- `tools/project-forge-vscode/work-item-status/install.py` and `docs/work-items` when present;
|
|
50
51
|
- current Git branch/status/upstream evidence so setup does not overwrite unrelated work;
|
|
51
52
|
- workstation-local setup/readiness evidence when present;
|
|
52
53
|
- actual workstation OS/platform and machine-local identity needed to describe this workspace instance.
|
|
@@ -84,12 +85,13 @@ Prefer a compact result such as:
|
|
|
84
85
|
```text
|
|
85
86
|
SETUP STATUS
|
|
86
87
|
|
|
87
|
-
Workspace
|
|
88
|
-
Local runtime
|
|
89
|
-
Build/tests
|
|
90
|
-
Local data
|
|
91
|
-
Personal profile
|
|
92
|
-
|
|
88
|
+
Workspace ........... READY / NOT CONFIGURED / BLOCKED
|
|
89
|
+
Local runtime ....... READY / STALE / NOT APPLICABLE
|
|
90
|
+
Build/tests ......... READY / STALE / BLOCKED
|
|
91
|
+
Local data .......... READY / NOT APPLICABLE / BLOCKED
|
|
92
|
+
Personal profile .... READY / DEFERRED / BLOCKED
|
|
93
|
+
Work-item Explorer .. READY / NOT INSTALLED / NOT APPLICABLE / ERROR
|
|
94
|
+
Remote capability ... READY / PARTIAL / NOT CONFIGURED
|
|
93
95
|
|
|
94
96
|
NEXT
|
|
95
97
|
/setup local | /setup remote | /setup <environment> | /next-step
|
|
@@ -126,6 +128,38 @@ A temporary process `PATH` adjustment may prove a diagnosis but does not by itse
|
|
|
126
128
|
|
|
127
129
|
Stop before destructive replacement, unrelated machine mutation, secret disclosure, or repair outside the declared setup contract.
|
|
128
130
|
|
|
131
|
+
### Work-item Explorer decoration
|
|
132
|
+
|
|
133
|
+
When `tools/project-forge-vscode/work-item-status/install.py` exists, treat the Project Forge-owned VS Code work-item status extension as routine workstation setup when local `docs/work-items` folders are present.
|
|
134
|
+
|
|
135
|
+
For `/setup status`, remain read-only. If `docs/work-items` exists, run:
|
|
136
|
+
|
|
137
|
+
```text
|
|
138
|
+
python tools/project-forge-vscode/work-item-status/install.py status --json
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
Report the returned state as the `Work-item Explorer` setup dimension. If `docs/work-items` does not exist, report `NOT APPLICABLE` and do not create a local work-item hierarchy merely to enable badges.
|
|
142
|
+
|
|
143
|
+
For normal `/setup` and `/setup local`, when `docs/work-items` exists, run the bounded Project Forge installer:
|
|
144
|
+
|
|
145
|
+
```text
|
|
146
|
+
python tools/project-forge-vscode/work-item-status/install.py install --json
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
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
|
+
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
|
+
|
|
153
|
+
If a Project has local `docs/work-items` but the package-managed installer is absent, report:
|
|
154
|
+
|
|
155
|
+
```text
|
|
156
|
+
PROJECT FORGE UPDATE NEEDED
|
|
157
|
+
```
|
|
158
|
+
|
|
159
|
+
Route to `/project-forge-update`; do not clone private Project Forge source repositories or download loose extension files as a workaround.
|
|
160
|
+
|
|
161
|
+
A decorator installation error does not erase otherwise valid runtime/build readiness. Report the `Work-item Explorer` dimension as `ACTION NEEDED` or `ERROR`, preserve the other independent setup dimensions, and give the smallest repair/update action.
|
|
162
|
+
|
|
129
163
|
## 4. `/setup local` converges verified local development readiness
|
|
130
164
|
|
|
131
165
|
The first success target is:
|
|
@@ -485,6 +519,7 @@ SETUP RESULT
|
|
|
485
519
|
Local tools/runtime ......... VERIFIED / BLOCKED / NOT APPLICABLE
|
|
486
520
|
Fresh-shell discovery ....... VERIFIED / CAVEAT / BLOCKED
|
|
487
521
|
Build/tests ................. VERIFIED / BLOCKED / NOT RUN
|
|
522
|
+
Work-item Explorer .......... READY / ACTION NEEDED / NOT APPLICABLE
|
|
488
523
|
Remote target access ........ VERIFIED / BLOCKED / NOT CONFIGURED
|
|
489
524
|
Host platform ............... READY / BLOCKED / NOT APPLICABLE
|
|
490
525
|
Deployment path ............. PROVEN / NOT PROVEN / BLOCKED
|
|
@@ -10,6 +10,8 @@ disable-model-invocation: true
|
|
|
10
10
|
|
|
11
11
|
Purpose: make local `docs/work-items/<ID>-...` folders easier to scan in VS Code without changing work-item paths, ticket content, or Project Forge workflow authority.
|
|
12
12
|
|
|
13
|
+
Normal `/setup` owns automatic installation/update of this Project Forge extension when local `docs/work-items` folders are present. This command remains the focused read-only inspection and manual enable/disable surface.
|
|
14
|
+
|
|
13
15
|
Normal use is read-only:
|
|
14
16
|
|
|
15
17
|
```text
|
|
@@ -72,6 +74,8 @@ python tools/project-forge-vscode/work-item-status/install.py status --json
|
|
|
72
74
|
|
|
73
75
|
Also check whether `docs/work-items` exists. If the Project uses an external-only work-item source with no local work-item folders, report the Explorer decoration as not applicable rather than creating a competing local hierarchy.
|
|
74
76
|
|
|
77
|
+
If local work-item folders are present but the package-managed installer is absent, route to `/project-forge-update`; do not clone Project Forge source repositories or download loose extension files as a workaround.
|
|
78
|
+
|
|
75
79
|
A useful result is:
|
|
76
80
|
|
|
77
81
|
```text
|
|
@@ -84,7 +88,7 @@ Project workflow authority . UNCHANGED
|
|
|
84
88
|
|
|
85
89
|
## 4. Enable
|
|
86
90
|
|
|
87
|
-
`/work-item-status enable` is explicit authorization for one bounded local editor change: install/update the Project Forge-owned extension in this developer's VS Code extensions directory.
|
|
91
|
+
Outside `/setup`, `/work-item-status enable` is explicit authorization for one bounded local editor change: install/update the Project Forge-owned extension in this developer's VS Code extensions directory. Normal `/setup` and `/setup local` already authorize the same bounded install when local `docs/work-items` folders are present, so do not ask for a second confirmation in that flow.
|
|
88
92
|
|
|
89
93
|
Run:
|
|
90
94
|
|
|
@@ -102,7 +106,7 @@ Project Forge: Refresh Work Item Status
|
|
|
102
106
|
|
|
103
107
|
through the VS Code Command Palette.
|
|
104
108
|
|
|
105
|
-
Failure to install this
|
|
109
|
+
Failure to install this editor decoration does **not** make Project setup, implementation, review, delivery, or deployment unready. `/setup` reports the editor dimension separately as action-needed/error and gives the smallest repair/update action without erasing otherwise-valid application/runtime readiness.
|
|
106
110
|
|
|
107
111
|
## 5. Disable
|
|
108
112
|
|
|
@@ -124,4 +128,4 @@ Return:
|
|
|
124
128
|
- a reminder that badges are evidence-derived and non-authoritative;
|
|
125
129
|
- the smallest relevant next action.
|
|
126
130
|
|
|
127
|
-
Do not turn this
|
|
131
|
+
Do not turn this editor convenience into a source of Project workflow authority.
|