FBD: add Rθ(J-A)(°C/W) param (template v2, skill v2)

SKILL.md

@@ -118,7 +118,7 @@ Check whether that typeid has a sheet in `assets/template/template.xlsx`.
 
     This appends the column(s) at the end of that typeid's sheet, **bumps that typeid's
     Template Version and Skill Version together** (v1→v2 — see *Per-typeid versioning*),
-    and writes one row to the global changelog `assets/CHANGELOG.xlsx`. Then **ask
+    and writes one row to the global changelog `assets/template/CHANGELOG.xlsx`. Then **ask
     the user before pushing**, and sync the updated skill files + changelog to the skill repo
     with `push-skill` (see *Pushing the skill repo*) — that merges the new changelog row onto
     the one already in Gitea rather than overwriting it.
@@ -218,7 +218,7 @@ reading and writing these numbers.
 ## The changelog
 
 `append_parameter.py` maintains one **global** changelog as an Excel workbook at
-`assets/CHANGELOG.xlsx` (sheet `Changelog`, styled green header). Every time a
+`assets/template/CHANGELOG.xlsx` (sheet `Changelog`, styled green header). Every time a
 typeid's template/version changes, one row is appended with columns
 **Date | Typeid | Skill Version | Template Version | Description** — the version columns hold
 the new versions, and Description is your note (or the parameter(s) added if you gave none).
@@ -278,7 +278,7 @@ plain flat push, but it does not merge the changelog or blank the token, so pref
   `Footprint Ref/Path` and `Manufacturer` sit near the end.
 - `assets/template/Type_ID.xlsx` + `references/taxonomy.md` — Class → Subclass → Type ID.
 - `assets/template/versions.json` — per-typeid `template_version` + `skill_version`.
-- `assets/CHANGELOG.xlsx` — global version/parameter changelog (created on first add;
+- `assets/template/CHANGELOG.xlsx` — global version/parameter changelog (created on first add;
   merged into the skill repo's copy in Gitea by `push-skill`).
 - `scripts/common.py` — taxonomy loader (`load_taxonomy`, `class_folder`), version store
   (`get_versions`, `version_labels`, `bump_versions`), and the tag helper (`part_tag`).

assets/template/versions.json

@@ -156,8 +156,8 @@
     "template_version": 1
   },
   "FBD": {
-    "skill_version": 1,
-    "template_version": 1
+    "skill_version": 2,
+    "template_version": 2
   },
   "FFC": {
     "skill_version": 1,

config/gitea.env

@@ -3,7 +3,7 @@
 # Use a token scoped to these repos (repository: write) and rotate periodically.
 GIT_HOST=gitea.vecmocon.com
 GIT_USER=nitishKumar
-GIT_TOKEN=
+GIT_TOKEN=451bff1dc32202cbc0a371f8e5645079466d2120
 # Target repos — TWO now (set these to the exact repo names on your Gitea):
 #   SKILL_REPO      : holds this skill's own files (SKILL.md, scripts, assets, ...).
 #   COMPONENTS_REPO : holds components, one folder per Class (Diode, IC, ...); inside each,