@tryinget/pi-designmd-foundry 0.1.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/LICENSE +78 -0
- package/README.md +193 -0
- package/docs/adr/.gitkeep +0 -0
- package/docs/engineering.local.md +68 -0
- package/docs/org/operating_model.md +34 -0
- package/docs/project/contributing.md +51 -0
- package/docs/project/extension-sop.md +47 -0
- package/docs/project/foundation.md +31 -0
- package/docs/project/incentives.md +17 -0
- package/docs/project/integration-contract.md +74 -0
- package/docs/project/resources.md +23 -0
- package/docs/project/trusted-publishing.md +47 -0
- package/docs/project/vision.md +18 -0
- package/examples/.gitkeep +0 -0
- package/extensions/designmd.ts +1576 -0
- package/package.json +97 -0
- package/policy/engineering-lane.json +36 -0
- package/policy/security-policy.json +10 -0
- package/prompts/pi-designmd-foundry-implementation-planning.md +21 -0
- package/prompts/pi-designmd-foundry-security-review.md +21 -0
- package/skills/designmd-foundry/SKILL.md +112 -0
- package/src/.gitkeep +0 -0
- package/src/toolboxBundle.ts +67 -0
|
@@ -0,0 +1,47 @@
|
|
|
1
|
+
---
|
|
2
|
+
summary: "Trusted publishing notes for monorepo package components."
|
|
3
|
+
read_when:
|
|
4
|
+
- "Configuring npm OIDC trusted publishing for monorepo package releases."
|
|
5
|
+
- "Debugging release-please or publish workflow failures in monorepo CI."
|
|
6
|
+
system4d:
|
|
7
|
+
container: "Monorepo release automation reliability notes."
|
|
8
|
+
compass: "Use OIDC safely with component-aware release behavior."
|
|
9
|
+
engine: "Configure root workflows -> validate package metadata -> release -> verify."
|
|
10
|
+
fog: "Most failures come from root workflow policy mismatch or component map drift."
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
# Trusted publishing runbook (monorepo package mode)
|
|
14
|
+
|
|
15
|
+
## Baseline assumptions
|
|
16
|
+
|
|
17
|
+
- Release automation lives at monorepo root.
|
|
18
|
+
- Package release is component-scoped (release-please component mode or equivalent).
|
|
19
|
+
- Publish workflow uses npm OIDC trusted publishing (no long-lived npm token in CI).
|
|
20
|
+
|
|
21
|
+
## Package-level requirements
|
|
22
|
+
|
|
23
|
+
- `package.json.repository.url` must point to monorepo git URL.
|
|
24
|
+
- `package.json.repository.directory` must match package workspace path.
|
|
25
|
+
- `x-pi-template` metadata should align with root component mapping:
|
|
26
|
+
- `workspacePath`
|
|
27
|
+
- `releaseComponent`
|
|
28
|
+
- `releaseConfigMode`
|
|
29
|
+
|
|
30
|
+
## Root workflow expectations
|
|
31
|
+
|
|
32
|
+
- Root `release-please` workflow must keep component map aligned with package metadata.
|
|
33
|
+
- Publish workflow should run npm >= 11.5.1 for trusted publishing compatibility.
|
|
34
|
+
- Actions policy + permissions at repo level must allow release/publish workflows.
|
|
35
|
+
|
|
36
|
+
## Common failure modes
|
|
37
|
+
|
|
38
|
+
1. Component key drift between package metadata and root release config.
|
|
39
|
+
2. Wrong `repository.directory` causing provenance verification failures.
|
|
40
|
+
3. Workflow permissions set to read-only in monorepo settings.
|
|
41
|
+
4. Missing npm trusted publisher binding for monorepo repository/workflow.
|
|
42
|
+
|
|
43
|
+
## Verification checklist
|
|
44
|
+
|
|
45
|
+
- Package passes `npm run release:check:quick` in workspace.
|
|
46
|
+
- Root release workflow can produce/update component release PR.
|
|
47
|
+
- Publish workflow completes with `npm publish --provenance --access public` for package.
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
---
|
|
2
|
+
summary: "Product and technical vision for pi-designmd-foundry."
|
|
3
|
+
read_when:
|
|
4
|
+
- "Defining or revisiting project direction."
|
|
5
|
+
system4d:
|
|
6
|
+
container: "Project north-star statement."
|
|
7
|
+
compass: "Build a reliable pi extension package with low maintenance overhead."
|
|
8
|
+
engine: "Translate goals into concrete implementation slices."
|
|
9
|
+
fog: "Real user workflows may reshape priorities."
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
# Vision
|
|
13
|
+
|
|
14
|
+
Deliver a dependable extension package that is easy to understand, validate, and evolve.
|
|
15
|
+
|
|
16
|
+
Project purpose for this repository is scoped to extension delivery and maintenance.
|
|
17
|
+
It aligns with, but is distinct from, organization purpose documented in [Organization operating model](../org/operating_model.md).
|
|
18
|
+
For the project-level concept map, see [Project foundation model](foundation.md).
|
|
File without changes
|