Generated fasteners for FRC and FTC, part sets, and the Onshape workflow

.github/workflows/checks.yml

@@ -0,0 +1,18 @@
+# Tests, FeatureScript checks, and release files, before anything reaches Onshape (no API calls)
+name: Checks
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+jobs:
+  checks:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+      - run: uv sync --locked
+      - run: uv run pytest -q
+      - run: uv run fs check
+      - run: uv run fs releases

.github/workflows/onshape.yml

@@ -0,0 +1,53 @@
+# Lands main in the backend's main workspace by merging, makes the releases it asks for in releases/, and deletes the
+# workspaces of branches gone from origin (see docs/fs-cli.md#branches). Spends the API allocation of the account whose
+# keys are in the ONSHAPE_ACCESS_KEY and ONSHAPE_SECRET_KEY secrets.
+name: Onshape
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+# One at a time, so two merges can't both version a document
+concurrency:
+  group: onshape
+  cancel-in-progress: false
+
+permissions:
+  # To commit what releases record, and push their tags
+  contents: write
+  # To find the pull request a commit merged
+  pull-requests: read
+
+jobs:
+  onshape:
+    runs-on: ubuntu-latest
+    env:
+      API_ACCESS_KEY: ${{ secrets.ONSHAPE_ACCESS_KEY }}
+      API_SECRET_KEY: ${{ secrets.ONSHAPE_SECRET_KEY }}
+      FS_BRANCH: main
+      GH_TOKEN: ${{ github.token }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          # fs recognizes Onshape's code in git history
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@v6
+      - run: uv sync --locked
+      - run: uv run pytest -q
+      - run: uv run fs check
+      - name: Configure git
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+      - name: Land main in Onshape
+        run: |
+          # The pull request this commit merged, whose branch's workspace is landed; none for a direct push
+          branch=$(gh pr list --state merged --search "${{ github.sha }}" --json headRefName --jq '.[0].headRefName // empty')
+          uv run fs sync-main ${branch:+--branch "$branch"}
+      - name: Make the releases asked for
+        run: uv run fs run-releases
+      - name: Push what landing and releasing committed
+        run: git push origin HEAD:main
+      - name: Delete the workspaces of branches gone from origin
+        run: uv run fs branches --prune --yes

.gitignore

@@ -197,7 +197,7 @@ poetry.toml
 creds.json
 
 # fs CLI sync state (per machine)
-.fs-state.json
+.fs-state*.json
 .fs.lock
 
 # VS Code extension build output

AGENTS.md

@@ -3,6 +3,17 @@
 See `docs/fs-cli.md` for how the `fs` CLI works, and `docs/featurescript-style.md` for how to write
 FeatureScript here (including selections, editing logic, and manipulator change functions).
 
+## Onshape API calls
+
+Ask before anything that calls Onshape, and run it only once the user says yes, every time: the Onshape FeatureScript
+MCP's tools, and every `fs` command that talks to Onshape (`push`, `pull`, `sync`, `release`, `parts`, `configuration`,
+`deprecate`, `sync-versions`, `release-tags`, `sync-main`, `run-releases`, `branches`, `features`, `pull-std`,
+`update-std`, `released --detect`, and the
+rest). Each call spends the
+user's Onshape API allocation, and a write to a released or library document can't be undone. Offline work needs no
+asking: `fs gen`, `check`, `format`, `audit`, `ui`, `eval`, `table`, and `pytest`, which run against fakes. When the
+user runs a command themselves, say exactly what to run.
+
 `README.md` is for users: an overview of the repo, setup, and links. How the tools work, and anything else written for
 agents, goes in `docs/`, a skill, or here.
 
@@ -30,6 +41,13 @@ before stating how FeatureScript or Onshape behaves, or adding a rule here or to
 For FeatureScript names, `fs doc NAME` shows a std or project symbol's signature and documentation, `fs refs NAME`
 where it's used, and `fs rename NAME NEW` renames it everywhere; `fs check --fix` fixes problems with one right answer.
 
+FeatureScript-backed parts (FRCDesign's fasteners) are part sets, tried and released by `fs parts`, never `fs release`;
+see `docs/parts.md`.
+
+Each git branch pushes to a backend workspace of its own; main reaches the main workspace only by `fs sync-main`, which
+the Onshape workflow runs on merge, and releases are asked for in `releases/` files rather than run from a branch (see
+`docs/fs-cli.md#branches`).
+
 A "top level option" means a horizontal enum at the top of the feature (see `docs/featurescript-style.md`'s
 "Horizontal enums go at the top").
 
@@ -50,5 +68,9 @@ Never rename a released feature's constant (the name `defineFeature` is exported
 documents store it as the feature's type, and lose the feature if it changes. Rename its Feature Type Name and its file
 instead (see `docs/featurescript-style.md`'s "Released feature constants").
 
+FRCDesign's library fasteners' configured Part Studios are an exception too: FRCDesign inserts them with configurations of their
+option ids, and recognizes the fasteners already in assemblies by them, so never rename or remove a released option
+id (see `featurescripts/fasteners/fastenerTables.py`); add new ones.
+
 The other exception is attributes, which other features and documents read back. When an attribute's format changes, either
 handle old attributes or report them as an error; either is fine.

docs/cots-research.md

@@ -12,7 +12,7 @@ FRCDesign's public API (no sign-in, and no Onshape API calls):
 
 ```
 uv run fs cots 'hex shaft'                 # FRC parts matching a regular expression, most used first
-uv run fs cots 'channel|beam' -l ftc       # the FTC library (-l mkcad for MKCad's)
+uv run fs cots 'channel|beam' -l config    # ConfigLib, FTC's library (-l mkcad for MKCad's)
 uv run fs cots 'hex shaft' -d              # also each part's configuration usage, and part numbers with the options they're for
 uv run fs cots --days 90 -n 100            # the top 100 parts over the last 90 days
 ```
@@ -40,7 +40,7 @@ need. These work without signing in; `{date}`s are like `2026-01-31`:
 | `/search-db/library/{library}?v={version}` | The app's search index (a serialized MiniSearch index of part names, groups, and part numbers) |
 
 Others (`/build-status/library/{library}`, `/job-status/library/{library}`, and `/favorites/library/{library}`) need
-signing in to Onshape. Libraries are `frc-design-lib`, `ftc-design-lib`, and `mkcad`. A part's page in the app, like
+signing in to Onshape. Libraries are `frc-design-lib`, `config-lib`, and `mkcad`. A part's page in the app, like
 `https://app.frcdesign.org/app/library/frc-design-lib?part={insertable id}`, shows the options its configuration
 endpoint returns. It rejects Python's `urllib` (by its user agent), so use `requests` or `curl`.