Problem with "--no-duplication" and "--no-clipping"

Hello,

I want to create pbf-tiles in which features are not clipped nor duplicated, i.e. features are allowed to extend beyond the tiles borders and should only be included in one tile.

But I have the feeling the "--no-clipping" flag is not working correctly. I'm quite new to using Tippecanoe, so maybe I'm just doing something wrong. Some examples:

**1. ✅ The "default":**

`tippecanoe -e test1 --no-tile-compression input.geojson` gives:

This is the border between 4 tiles, you can see that the feature in the middle is clipped and distributed over the 4 tiles.

**2. ❌ Using only --no-clipping**

`tippecanoe -e test2 --no-tile-compression --no-clipping input.geojson` gives:

Even though I asked to not clip the features, they still are clipped to the tile borders?

**3. ✅ Using --no-duplication**

`tippecanoe -e test3 --no-tile-compression --no-duplication input.geojson`

So now indeed, the features are not duplicated, but they are still clipped to the tile boundaries. (The pink background is `input.geojson`)

**4. ❌ Using both --no-clipping and --no-duplication**

`tippecanoe -e test4 --no-tile-compression --no-clipping --no-duplication input.geojson`

Again, the features aren't duplicated, but they are still clipped.

The documentation says:

- `-pc` or `--no-clipping`: Don't clip features to the size of the tile. If a feature overlaps the tile's bounds or buffer at all, _it is included completely._ Be careful: this can produce very large tilesets, especially with large polygons.

But in the above examples the features are **not** included completely?

Thanks,
Bert

```
tippecanoe --version
>>> tippecanoe v2.40.0
```

Start by reproducing the four commands with input.geojson and compare the generated tiles with the documented --no-clipping and --no-duplication behavior. Trace the CLI handling for those flags and the clipping or duplication path in Tippecanoe. Done means the observed output matches the documented semantics, with regression coverage or clarified documentation if the behavior is intentional.

Written by the indexing model from the issue text.