@numericoach/gskills-admin-cli 0.1.30 → 0.1.32
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 +53 -4
- package/dist/gskills-admin.js +22904 -756
- package/package.json +25 -24
- package/skills/gskills-admin-cli/SKILL.md +226 -260
- package/skills/gskills-admin-cli/references/content-platform-tables.md +1647 -0
- package/skills/gskills-admin-cli/references/content-platform.md +146 -0
- package/skills/gskills-content-sync-cache-ops/SKILL.md +36 -89
- package/skills/gskills-customer-playbooks/SKILL.md +18 -19
- package/skills/gskills-ops-db-audit/SKILL.md +5 -5
- package/skills/gskills-page-content-blocks/SKILL.md +40 -47
- package/skills/gskills-source-id-repair/SKILL.md +11 -30
|
@@ -1,41 +1,22 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: gskills-source-id-repair
|
|
3
|
-
description: Use when a GSkills
|
|
3
|
+
description: Use when a GSkills ticket looks like the old sync source-link corruption (missing or duplicated sourceItemId, sourceGroupId, sourceKnowledgeId, page crossInstanceID). Since the content migration the sync repair is retired; this skill routes to canonical checks and admin operations and keeps the Legacy history.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# GSkills Source ID Repair
|
|
7
7
|
|
|
8
|
-
|
|
8
|
+
## Since the content migration (Sept 2026)
|
|
9
9
|
|
|
10
|
-
|
|
10
|
+
This repair is retired. Every content family is canonical-primary: shared content is stored once and inherited by every instance, so there are no customer copies, no source links to backfill and no sync to fail. `sync run` and `sync repair-source-links` are refused with `LEGACY_CONTENT_WRITE_RETIRED`. Follow the refusal's `nextAction`; never work around it with direct DB, Prisma, SQL or a script, and never recreate customer copies or retired projections.
|
|
11
11
|
|
|
12
|
-
|
|
13
|
-
gskills-admin sync repair-source-links --target <instanceId> --dry-run --output json
|
|
14
|
-
gskills-admin sync repair-source-links --target <instanceId> --yes --output json
|
|
15
|
-
```
|
|
12
|
+
What to do instead when a ticket looks like this class:
|
|
16
13
|
|
|
17
|
-
|
|
14
|
+
1. Confirm the real instance id (never trust a random id from a feedback URL; on April 9 2026 `cmm1tyno3000004l4lg6cx1hw` was `NICKEL BANQUE`, the real `AIR LIQUIDE` was `cmfwilgzb000404kzmfrkuifm`).
|
|
15
|
+
2. Resolve old ids to canonical identities with `content-id-aliases` and `page-route-aliases`.
|
|
16
|
+
3. Check what the customer actually sees: `gskills-admin admin run catalogue.list --data '{"instanceId":"<id>"}' --yes --output json`, and `page-authoring editor` for pages.
|
|
17
|
+
4. Learning path structure problems (duplicate, stale or missing items): read the path, then send the corrected COMPLETE item and group list with `gskills-admin admin run learning-paths.update` (`admin describe learning-paths.update` first, `--dry-run`, then `--yes` after approval, then re-read). Check completions before retiring items.
|
|
18
|
+
5. Inspect migration evidence (`content-migration-issues`, `content-reconciliation-ledgers`) when the problem comes from the migration itself, and report it rather than patching rows.
|
|
18
19
|
|
|
19
|
-
##
|
|
20
|
+
## Legacy history
|
|
20
21
|
|
|
21
|
-
|
|
22
|
-
- Fix the data, not just the app fallback.
|
|
23
|
-
- Prefer the sync engine over ad hoc SQL when it can reconcile structure.
|
|
24
|
-
- Only consider manual cleanup after checking completions and source structure in code.
|
|
25
|
-
- If this becomes recurring, add another CLI route or extend `sync repair-source-links`.
|
|
26
|
-
|
|
27
|
-
## Triage
|
|
28
|
-
|
|
29
|
-
```bash
|
|
30
|
-
gskills-admin sync logs --target <instanceId> --take 10 --output json
|
|
31
|
-
gskills-admin sync repair-source-links --target <instanceId> --dry-run --output json
|
|
32
|
-
```
|
|
33
|
-
|
|
34
|
-
If the dry-run shows missing links, run the same command with `--yes` after approval, then dry-run again.
|
|
35
|
-
|
|
36
|
-
## Done Criteria
|
|
37
|
-
|
|
38
|
-
- CLI dry-run shows the expected before counts.
|
|
39
|
-
- Real repair ran with `--yes` only after approval.
|
|
40
|
-
- Follow-up dry-run shows no remaining repairable source-link gap.
|
|
41
|
-
- A fresh sync no longer fails on the source-id bug.
|
|
22
|
+
The Legacy command was `sync repair-source-links` (now refused). The notes below explain old logs and tickets only; do not replay them.
|