@overcrow/mcp 0.1.0 → 0.1.2

package/dist/content/docs/en/manifest.md

@@ -39,7 +39,7 @@ values it fills in. A manifest with permissions and a menu:
 {
   "schemaVersion": 1,
   "apiVersion": 1,
-  "id": "com.example.countdown",
+  "id": "nova.countdown",
   "version": "1.0.0",
   "name": { "en": "Countdown", "fr": "Compte à rebours" },
   "sizing": {
@@ -79,7 +79,7 @@ values it fills in. A manifest with permissions and a menu:
 | --- | --- | --- | --- |
 | `schemaVersion` | integer 1 to 1 | yes | Manifest document version. |
 | `apiVersion` | integer 1 to 1 | yes | Widget API version; selects this schema. |
-| `id` | `widget ID` | yes | Reverse-DNS ID, from 3 bytes to 128 bytes: at least two dot-separated segments of `[a-z0-9-]`, each at most 63 bytes and not starting or ending with `-`. `com.playervox` and `com.playervox.*` are reserved for packages signed by PlayerVox. |
+| `id` | `widget ID` | yes | Widget ID, from 3 bytes to 128 bytes: at least two dot-separated segments of `[a-z0-9-]`, each at most 63 bytes and not starting or ending with `-`; `<handle>.<name>` with the publisher's handle, or a domain the publisher verified, reversed, then a name. `com.playervox` and `com.playervox.*` are reserved for packages signed by PlayerVox. |
 | `version` | `version` | yes | SemVer 2.0.0 `MAJOR.MINOR.PATCH[-PRERELEASE]` in canonical form, at most 64 bytes; build metadata is rejected. |
 | `name` | `WidgetName` | yes | Localized widget name shown by the host. |
 | `sizing` | `Sizing` | yes | Size and fit rules applied by the widget's frame. |
@@ -92,9 +92,13 @@ values it fills in. A manifest with permissions and a menu:
 ### Identity and version
 
 - **`id`** is the widget's identity everywhere: in the catalog, in the
-  user's profile, in its storage. Choose a reverse-DNS ID under a domain you
-  control and keep it. IDs under `com.playervox` are reserved for widgets
-  published by PlayerVox.
+  user's profile, in its storage. It is `<handle>.<name>`, your publisher
+  handle in the OverCrow creator space and a name (`nova.lol-timers`), or,
+  once you verified a domain, that domain reversed and a name
+  (`gg.nova.lol-timers`). An ID is final: it is never given to another
+  widget, even after yours is removed. `nova`, `example`, `yourhandle` and
+  `yourname` are example handles that nobody can publish under, and IDs
+  under `com.playervox` are reserved for widgets published by PlayerVox.
 - **`version`** is a semantic version. A published version never changes:
   any change to a published widget is a new, higher version.
 - **`schemaVersion`** and **`apiVersion`** are both `1`.
@@ -102,7 +106,10 @@ values it fills in. A manifest with permissions and a menu:
 ### Names
 
 `name` gives the name OverCrow shows in its widget list and menus, in
-English and in French. Both are required.
+English and in French. Both are required. A name shows as written: no
+control character and no invisible or text-direction character, such as
+U+200B (zero-width space) or U+202E (right-to-left override). Menu labels
+follow the same rule.
 
 <!-- generated:manifest-name -->
 | Field | Type | Required | Meaning |

package/dist/content/docs/en/mcp.md

@@ -119,7 +119,7 @@ Developer, Edit Config), then restart Claude Desktop.
 ## What it does not do
 
 - It never sends, signs or publishes anything. You send the ZIP and the
-  texts in the OverCrow creator space on overcrow.playervox.com.
+  texts in the OverCrow creator space, at creators.playervox.com.
 - It does not install your widget in OverCrow: trying it in a game is the
   [development channel](dev-channel.md) of the command-line tool.
 - It sends nothing about you: no telemetry, no account.

package/dist/content/docs/en/publish-a-widget.md

@@ -0,0 +1,94 @@
+# Publish a widget
+
+In the creator space of PlayerVox OverCrow, at
+`creators.playervox.com`, a widget reaches players in four steps:
+you send its sources, they are checked automatically, PlayerVox reviews
+them, then the version is published in the catalog. This page covers the
+first two and the screen that sends a version to review; the
+[review](widget-review.md) and the [listing](widget-listing.md) have their
+own pages.
+
+## Before you send
+
+- Your widget's ID is reserved in the creator space
+  ([getting started](creator-space.md)), and `manifest.json` uses it.
+- `overcrow-widget check` passes in the widget's folder.
+- The version in `manifest.json` is newer than the last approved one:
+  `1.2.1` or higher after `1.2.0`.
+
+## Send the sources
+
+Open the widget in **Widgets**, then **Submit a version**.
+
+- On a computer, drop the widget's folder on the page, or choose it. You
+  can also send a `.zip` of the folder.
+- On a phone or a tablet, which cannot pick a folder, choose the `.zip`.
+
+The creator space reads a folder with the same rules as
+`overcrow-widget submit`, on your computer, and sends the same files. It
+leaves out hidden files and folders (`.env`, `.git/`…), `node_modules/`,
+`dist/`, `tests/output/`, `__MACOSX/`, built packages, key files, system
+files and names that are not portable ASCII; the page lists what it left
+out. A `.zip` is sent as it is. The bounds and the refusals are those of
+[source archives](cli.md#source-archives): 32 MiB for the archive, 64 MiB and
+2,000 files once uncompressed, 16 levels of folders, paths of 255 bytes at
+most, no two names that differ only by case.
+
+- A `.zip` made by Windows PowerShell 5.1 (`Compress-Archive`) separates
+  folders with `\` and is refused at once: drop the folder instead.
+- A file or folder name with `\ : * ? " < > |` is refused before anything
+  is sent: Windows cannot use it. Rename it.
+- A browser reads the file a link points to, where the command-line tool
+  leaves the link out. Keep links out of the widget's folder.
+- Your sources stay private: only PlayerVox reviewers read them, and every
+  access shows in the creator space.
+
+A publisher sends at most 20 submissions in 24 hours; the page says when
+the next one is possible. If the page is closed or the connection drops
+while sending, drop the same folder again: the submission resumes, and
+nothing is counted twice.
+
+## The checks
+
+The checks take about a minute: the manifest, the version number, the code,
+the package build, the permissions, the size. You can leave the page: an
+e-mail tells you when they end.
+
+- When a check fails, each problem is shown in your own files, with the
+  line and the correction. Fix it and send again; nothing reaches the
+  reviewers.
+- "Problem on our side" means PlayerVox could not run the checks: your
+  code is not the cause. PlayerVox is told and runs them again.
+
+## Submit for review
+
+When the checks pass, the version page says what changes for players:
+
+- **Permissions.** Explain why the widget needs each new or widened
+  permission, in words players understand. A first version explains all of
+  them.
+- **Privacy policy.** Required as soon as the widget uses the network. The
+  address typed here is saved into the listing too.
+- **Listing.** A first version goes to review with its listing, which needs
+  an English description, a license and a support contact.
+- **Release notes**, shown to players: optional. English comes first;
+  **Add a language** adds others, 16 at most. When you write any, write
+  them in English too.
+- **Message for the review**, read only by PlayerVox: a test account,
+  useful context.
+
+The page also says which review the version gets (quick or full) and what
+changed since the last approved version. **Submit for review** sends it.
+
+## From a terminal or a CI job
+
+`overcrow-widget submit` sends a version with a publish key, and stops at
+the same screen when something is missing: see [`submit`](cli.md#submit) and
+[publish keys and CI](publish-keys.md).
+
+## After the review
+
+An approved version is published within 24 business hours. In the creator
+space you can then withdraw it, or the whole widget (**Settings**): it
+leaves the catalog at the next publication, and installed copies keep
+working.

package/dist/content/docs/en/publish-keys.md

@@ -0,0 +1,95 @@
+# Publish keys and CI
+
+A publish key lets `overcrow-widget submit` send versions of one
+PlayerVox OverCrow widget from a terminal or a CI job, without your
+password. It can do nothing else.
+
+## What a key can do
+
+- Submit versions of **one** widget, and follow their checks. Every version
+  still goes through the review before players get it.
+- It can neither publish, nor change the listing, nor reach your account or
+  your other widgets.
+- It lasts 1 to 365 days (90 by default). We remind you by e-mail and in
+  the creator space 14 days before it expires.
+- PlayerVox keeps only a digest of it: the key is shown **once**, when you
+  create it.
+
+## Create a key
+
+In the creator space, **Publish keys**, **Create a key**:
+
+1. Name it after where it will live (`GitHub Actions`, `Laptop`).
+2. Choose the widget and the lifetime.
+3. Confirm with a fresh code of your authenticator app.
+
+Copy the key at once into your CI's secrets: it starts with `ocw_pub_` and
+will never be shown again. If you lose it, revoke it and create another
+one. A widget has at most ten active keys.
+
+## Use it
+
+`overcrow-widget submit` reads the key from the environment variable
+`OVERCROW_PUBLISH_KEY`, and only there: never put it in a file of your
+project or in a command line.
+
+```sh
+export OVERCROW_PUBLISH_KEY=ocw_pub_…
+overcrow-widget submit
+```
+
+The [submit command](cli.md#submit) checks the version as the creator space
+will, sends it, then follows its checks, about a minute.
+
+## In GitHub Actions
+
+Keep the key as a secret of the repository, `OVERCROW_PUBLISH_KEY`. This
+workflow submits the widget on every version tag:
+
+<!-- source: docs/content/examples/weather/.github/workflows/submit.yml -->
+```yaml
+# Sends the widget to the OverCrow creator space when a version tag is
+# pushed. The publish key is a secret of the repository, and the OverCrow
+# release whose creator tools to use is a variable of the repository.
+name: Submit to OverCrow
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  submit:
+    runs-on: ubuntu-24.04
+    env:
+      OVERCROW_VERSION: ${{ vars.OVERCROW_VERSION }}
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install overcrow-widget
+        run: |
+          tools="overcrow-creator-tools-$OVERCROW_VERSION-linux-x86_64"
+          curl --fail --location --silent --show-error --remote-name \
+            "https://github.com/Valhallab/playervox-overcrow-releases/releases/download/v$OVERCROW_VERSION/$tools.zip"
+          unzip -q "$tools.zip"
+          (cd "$tools" && sha256sum --check --quiet SHA256SUMS)
+          install -D -m 755 "$tools"/overcrow-widget-*-linux-x86_64 "$HOME/.local/bin/overcrow-widget"
+          echo "$HOME/.local/bin" >> "$GITHUB_PATH"
+      - name: Submit to OverCrow
+        run: overcrow-widget submit --submission submission.json
+        env:
+          OVERCROW_PUBLISH_KEY: ${{ secrets.OVERCROW_PUBLISH_KEY }}
+```
+
+The job fails when the checks fail, with each problem on the line of your
+file. A version the creator space already has is not sent again: `submit`
+reports its state, so the same job may also run on every push to your main
+branch.
+
+## Revoke a key
+
+**Revoke** stops the key at once: an upload in progress with it fails.
+Versions it already sent stay, but no longer enter review on their own:
+send them to review from the creator space. Revoke a key as soon as you
+think it leaked, then create a new one.

package/dist/content/docs/en/publishing.md

@@ -1,5 +1,10 @@
 # Publishing and review
 
+> **Pull requests are closed.** Widgets are no longer proposed by pull
+> request: PlayerVox's own widgets already go through the OverCrow creator
+> space, and yours will when it opens. Until then, this page describes the
+> admission, the review and the catalog a widget goes through.
+
 Widgets reach PlayerVox OverCrow users through the signed widget catalog:
 OverCrow installs only what that catalog lists. This page goes from a
 widget's source directory to a listed version. Neither a pull request nor a

package/dist/content/docs/en/testing.md

@@ -376,7 +376,7 @@ are real.
 `overcrow-widget-headless` is OverCrow's own code without a window: it
 validates the package as the overlay does and runs the widget's logic in
 the same sandbox. `overcrow-widget test` runs the version this CLI pins,
-0.6.0-beta.2, and prints its version and SHA-256. Without the operating
+0.7.0-beta.1, and prints its version and SHA-256. Without the operating
 system's sandbox the runtime refuses to run and says so; the test command
 then ends with status 2.
 
@@ -387,8 +387,8 @@ one this CLI pins. The ZIP is not kept. The runtime then stays in the CLI's cach
 
 | Platform | Path |
 | --- | --- |
-| Linux | `~/.cache/overcrow-widget/runtime/0.6.0-beta.2/` (`$XDG_CACHE_HOME` instead of `~/.cache` when set) |
-| Windows | `%LOCALAPPDATA%\overcrow-widget\runtime\0.6.0-beta.2\` |
+| Linux | `~/.cache/overcrow-widget/runtime/0.7.0-beta.1/` (`$XDG_CACHE_HOME` instead of `~/.cache` when set) |
+| Windows | `%LOCALAPPDATA%\overcrow-widget\runtime\0.7.0-beta.1\` |
 
 To work offline, put the runtime of the creator tools ZIP there yourself
 (executable on Linux): `test` finds it and downloads nothing. With

package/dist/content/docs/en/verified-domain.md

@@ -0,0 +1,46 @@
+# Verified domain
+
+Verifying a domain you own puts the **Verified domain** badge next to your
+publisher's name, in the Control Center of PlayerVox OverCrow and on the
+website, and lets your
+widgets' IDs start with that domain reversed: `gg.nova.lol-timers` for
+`nova.gg`.
+
+## Add a domain
+
+In the creator space, **Publisher profile**, **Add a domain**. Write the
+domain alone, without `https://` or `www.`: `nova.gg`. A publisher can hold
+up to eight domains.
+
+The creator space then gives the DNS record to publish at your DNS host: a
+TXT record named `_overcrow.` followed by your domain, whose value is
+`overcrow-verify=` followed by a token.
+
+```text
+_overcrow.nova.gg.  TXT  "overcrow-verify=3f9c1e7a52d04b8e"
+```
+
+## Verification
+
+**Check now** looks for the record at once (once a minute at most). We
+also check on our own every hour for seven days. DNS can take a few minutes
+to spread.
+
+| State | Meaning |
+| --- | --- |
+| Pending | The record is not found yet; checked every hour for seven days. |
+| Verified | The record is found. It is checked again every 30 days. |
+| Lost | The record disappeared. Put it back, then check now. |
+| Expired | Not verified within seven days. Check now to start again. |
+
+Keep the record in place: if it disappears, the badge goes away. The IDs
+of widgets you already created under the domain stay yours.
+
+## Who can claim a domain
+
+- A domain verified once by a publisher is reserved to it, as are the
+  domains under and above it: nobody else can claim them.
+- A domain reading as PlayerVox, OverCrow or Valhallab is refused; write to
+  support if it is yours. IDs under `com.playervox` belong to PlayerVox.
+- Removing a domain never verified forgets it. A domain verified once stays
+  reserved to you, and cannot be removed while widget IDs use it.

package/dist/content/docs/en/widget-listing.md

@@ -0,0 +1,65 @@
+# The listing: best practices
+
+The listing is what players read in the PlayerVox OverCrow catalog before
+they install a widget: its description, its preview, its category, its
+games, its license and its links. You write it in the creator space, in the
+widget's **Listing** tab.
+
+## Saved as you type
+
+The listing is a draft, saved by itself as you type.
+
+- A widget's first listing goes to review with its first version.
+- Later changes go alone to a quick review: **Submit the listing**. They
+  need no new version of the widget. **Cancel the changes** brings the
+  draft back to the published listing.
+- The category is the exception: you change it at any time, without a
+  review, and the change reaches players with the next publication of the
+  catalog.
+
+## Languages
+
+English comes first: it is the default, shown when a player's language has
+no description. **Add a language** adds another one, 16 languages at most.
+The widget's name comes from its manifest (`name.en`, `name.fr`): to change
+it, change the manifest and submit a version. The languages of the widget's
+own interface come from its `locales/` files.
+
+## Description
+
+- 500 characters at most per language. The first two lines show on the
+  catalog card: say what the widget does, plainly.
+- Say when the widget contacts a server, and which one.
+- No advertising and no claim the widget does not keep.
+
+## Preview image
+
+One image, in English, for every language: a PNG in 4:3, from 480 × 360 to
+1,024 × 768 (1,024 × 768 recommended), 256 KiB at most. Show the widget in
+use, without marketing text.
+
+## Category and games
+
+The category places the widget in the catalog. Add up to five games it is
+made for: players filter the catalog by game.
+
+## License and links
+
+- **License**: "Proprietary, all rights reserved", or an SPDX license such
+  as `MIT` or `Apache-2.0`.
+- **Support**: an e-mail address or a web page where players get help.
+  Required.
+- **Privacy policy**: required as soon as the widget uses the network.
+- **Public source code**: optional; a public repository adds the "Public
+  source code" badge.
+
+Type an address as you know it (`example.com/privacy`): `https://` is added
+for you, and a `/` after a bare domain (`example.com` is saved as
+`https://example.com/`). An address in `http://` is refused.
+
+## From listing.json
+
+A version's sources may carry a `listing.json`, as the command-line tool
+reads it (see [`admit`](cli.md#admit)). In the
+**Listing** tab, **Import listing.json** applies its descriptions, license
+and source code address to the draft.

package/dist/content/docs/en/widget-review.md

@@ -0,0 +1,57 @@
+# Review: types, delays, appeals
+
+Every version of a PlayerVox OverCrow widget, and every change of its
+listing, is read by a person at PlayerVox before players get it. This page
+covers the two kinds of review, their delays, the review thread and the
+appeal. To send a version, see [publish a widget](publish-a-widget.md).
+
+## Quick or full
+
+| Review | When | Longest delay |
+| --- | --- | --- |
+| Full | The first publication, or an update that adds a permission, a network route or a capability | 5 business days |
+| Quick | Any other update, or a change of the listing alone | 2 business days |
+| Appeal | Once per decision, within six months | 7 days |
+| Publication | After the approval | 24 business hours |
+
+Business days run Monday to Friday, except French public holidays. The delay
+is paused while the review waits for your reply or a corrected version.
+A quick review reads the lines that changed since the last approved
+version; a full review reads the whole widget.
+
+## The review thread
+
+Each version in review has a thread in the creator space:
+
+- A **remark** points to a file and a line, quotes the code the reviewer
+  read and cites a numbered rule of the publication rules.
+- You can **reply** to the reviewer. Your reply sends the review back to
+  the reviewer when it was waiting for you.
+- A **corrected version** continues the same thread: send it from
+  **Submit a version**, with a newer version number.
+- The **decision** is approval, changes requested or a refusal, always
+  with its reasons.
+
+Reviewers are shown as "PlayerVox reviewer", never by name. Every time a
+reviewer opens your sources, the creator space shows when, which version
+and why, under **Access to your sources**.
+
+## Appeal
+
+You can contest a refusal or a suspension once per decision, within six
+months, with **Contest the decision**. PlayerVox re-examines the decision
+entirely and answers within 7 days, with its reasons. You can always send a
+new version instead.
+
+## Suspension
+
+When players are at risk (malicious code, a leaked key, a data leak),
+PlayerVox can suspend a widget or a version at once: installed copies are
+turned off. The creator space gives the reason and the rule, and the
+appeal stays open.
+
+## Withdrawal
+
+You can withdraw a version or the whole widget at any time: it leaves the
+catalog at the next publication, and installed copies keep working. A
+version in review or approved but not published yet is withdrawn at once.

package/dist/content/docs/en/widget-statistics.md

@@ -0,0 +1,134 @@
+# Statistics: definitions
+
+The **Statistics** tab of a widget, in the creator space, shows how players
+use it: installs, daily active players, errors and the players' rating.
+PlayerVox OverCrow sends these figures anonymously. They are trends, not
+exact counts: this page says what each figure counts and what it leaves out.
+
+## Where the figures come from
+
+Once a day at most, at a random time, OverCrow sends one anonymous signal
+for each widget installed from the catalog: the widget, its version, the
+day, the system (Windows or Linux), the version of OverCrow, whether the
+widget was shown, installed or uninstalled that day, and its errors (kind,
+place in the code, a rounded count).
+
+- **No identifier**: nothing names the player or the computer, and nothing
+  links the widgets of one player, each widget being sent apart.
+- **No error message**: only the kind of an error and its place in your
+  code. A message may hold personal data.
+- **On by default**: players can turn **Share anonymous statistics** off in
+  OverCrow; nothing is sent after that, and they are no longer counted.
+
+The figures are added up as the signals arrive. **Updated** gives the time
+of the last one counted.
+
+## The figures
+
+| Figure | What it counts |
+| --- | --- |
+| Daily active players | The players who showed the widget at least once that day. The tile gives the mean per day over the period. |
+| Active installs | Installs minus uninstalls, added up since the first signal, never below zero. |
+| Installs · uninstalls | The installs and the uninstalls of the period, and their balance. An update is neither. |
+| Errors | The sum of the errors reported over the period. |
+
+Each tile compares its figure with the period just before, of the same
+length: green when it moves the good way (fewer errors, more players), amber
+the other way, grey when it moves by less than 1 %. **First period** means
+there is nothing before to compare with.
+
+## Periods and filters
+
+- **Period**: 7 days, 28 days, 90 days or 12 months. Over 12 months, the
+  installs and uninstalls chart adds up each week.
+- **Version**: one of your published versions. Active installs show "—"
+  with a version: an installation changes version at every update, so that
+  figure only makes sense for all versions. **Version adoption** compares
+  the versions and does not follow this filter.
+- **System**: Windows or Linux. **Where your widget runs** compares the
+  systems and does not follow this filter.
+- The rating follows no filter.
+
+Every chart has **View as table**, with the same figures day by day.
+
+## Version adoption and where your widget runs
+
+- **Version adoption**: the share of the daily active players on each
+  version. The three newest versions keep their colour; the others add up as
+  **Older**.
+- **Where your widget runs**: the share of active players on Windows and on
+  Linux, and on each version of OverCrow (the two most used, then
+  **Others**).
+
+## Errors
+
+The errors are grouped by kind and by place in your code: the same kind at
+the same line of the same function is one group, whatever the version. The
+table shows the 50 most frequent groups of the period, with their versions,
+their count and their trend; **Export CSV** saves them.
+
+OverCrow reports where an error happened in the package's `logic.js`. The
+creator space traces that position back to your sources (file, line and
+function) with a map of your code built with the package and never
+published.
+
+- **Being traced**: the position is shown as `logic.js:line:column` until it
+  is traced.
+- **Not traced**: the version has no map, or the position is not in it; the
+  raw position stays.
+- **No position in the code**: the widget stopped as a whole (budget
+  exceeded, no answer); see its kind.
+- **SDK**: the error happened inside `@overcrow/sdk`, called from your code.
+
+| Kind | Meaning |
+| --- | --- |
+| `Error` | Error thrown |
+| `TypeError` | Value of an unexpected type |
+| `RangeError` | Value out of range |
+| `ReferenceError` | Unknown name |
+| `SyntaxError` | Invalid syntax |
+| `URIError` | Invalid address encoding |
+| `EvalError` | Code evaluation refused |
+| `AggregateError` | Several errors at once |
+| `InternalError` | Engine limit reached |
+| Thrown value | A value that is not an error was thrown |
+| Memory or processing budget exceeded | The widget was restarted |
+| Stopped responding | The widget was restarted |
+| Failed to load | The code or the view could not load |
+| Widget process stopped | Without reporting a fault |
+| Network request refused | Address not declared in the manifest |
+| Other error | Of a kind the creator space does not know yet |
+
+The kind of an error is the built-in type it was created from, never the
+`name` your code may give it.
+
+## Player rating
+
+Players rate a widget from 0 to 100 in the OverCrow Control Center, with
+their PlayerVox account: one rating per account and per widget, which they
+can change or remove.
+
+- **Score**: the mean of the ratings, rounded, with its rank: S+ from 90,
+  S from 80, A from 70, B from 60, C from 40, D from 20, then F.
+- **From 5 ratings**: below that, the creator space says **Not enough
+  ratings yet** and gives the number of ratings; the catalog shows nothing.
+- **Spread by rank**: the number of ratings in each rank, shown only in
+  the creator space. Nobody sees who rated.
+- **Since the latest version**: the points gained or lost since your latest
+  version was published, when 5 ratings existed before it.
+- The members of your publisher cannot rate its widgets.
+
+Players see the score, the rank and the number of ratings in the catalog
+and on the website.
+
+## Trends, not exact counts
+
+- Only the players who share their anonymous statistics are counted.
+- OverCrow rounds each error count to a step before sending it, and sends
+  at most 10 places in the code per widget and day: the error figures give
+  orders of magnitude.
+- A day is the player's own date.
+- A player who clears OverCrow's data, then installs the widget again,
+  counts as two installs.
+- Signals that look broken or inflated are set aside before they are
+  counted.