Open a scene framed, and thin out two inspector sections (#295)

Three small things asked for in one issue. A scene came up wherever
the view happened to stand, and the inspector carried a button and a
list that are better reached somewhere else.

- A scene comes up framed as if Fit had been clicked: after a
  project is loaded and when another scene is opened. From then on
  the view belongs to the user.
- An empty scene has nothing to frame and stands at the origin, one
  pixel per unit. A scene the running game loads is not framed anew.
- The Container tab is left out. It keeps the view of each container
  as before (#171).
- The Unpack button and the two lines under it are gone from the
  inspector of a placed container. Unpack container stays in the
  right-click menu of the hierarchy and of the scene view.
- The corners of a polygon collider are no row in the inspector any
  more. They are edited on the outline in the scene view. The new
  schema option noRow keeps a property out of the inspector while it
  stays a property.

Tests:
- Gate on melektaus-atx: 219 files, 3401 tests, CHECK EXIT 0.
- One new unit test in tests/core/polygon.test.ts: the corners are
  a property of the collider and no row.
- Three new e2e checks: a loaded project is framed like Fit (module
  03), an opened scene is (04), and after a real reload a click on
  Fit moves nothing (09).
- Module 09 unpacks through the right-click menu now and checks that
  the inspector offers no button.
- Full suite on melektaus-atx: 1695 checks, all pass. Smokes 24, 19
  and 21, all pass.
- No counter-probe evaluated, and nothing looked at after the build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/core/properties/PropertySchema.ts

@@ -132,6 +132,7 @@ export function initialOf(def: PropertyDef): PropertyValue {
 
 /** Whether the inspector shows the row, given the values of the bag it is on. */
 export function isRowShown(def: PropertyDef, values: PropertyBag): boolean {
+  if ('noRow' in def && def.noRow) return false;
   if (
     'shownFor' in def &&
     def.shownFor &&
@@ -197,8 +198,9 @@ export type PropertyDef =
    * A list declares nothing about its items: each one carries its own kind (see `listItems.ts`),
    * and the graph types a list as a list, so one `list` port fits them all. An `itemType` makes
    * every item a struct of that Struct asset (#254), each marked with it (`ITEM_TYPE_KEY`).
+   * `noRow` keeps it out of the inspector: its items are edited somewhere else (#295).
    */
-  | { key: string; label: string; kind: 'list'; default: ListValue; itemType?: string }
+  | { key: string; label: string; kind: 'list'; default: ListValue; itemType?: string; noRow?: boolean }
   /**
    * `fields` is the declaration; the value carries exactly those keys, which is what lets a struct
    * keep its shape while single fields are written (`mergeStruct`). With a `structType` the fields
@@ -605,11 +607,13 @@ const ASSET_SCHEMAS: Record<AssetType, PropertySchema> = {
     { key: 'width', label: 'Width', kind: 'number', default: 100, min: 1, step: 1 },
     { key: 'height', label: 'Height', kind: 'number', default: 100, min: 1, step: 1 },
     { key: 'radius', label: 'Radius', kind: 'number', default: 50, min: 1, step: 1 },
-    // A polygon's corners in the collider's own units, edited on the outline in the scene (#151).
+    // A polygon's corners in the collider's own units, edited on the outline in the scene (#151) –
+    // and only there: the inspector does not list them (#295).
     {
       key: 'points',
       label: 'Points',
       kind: 'list',
+      noRow: true,
       default: [
         { x: 0, y: -50 },
         { x: 50, y: 50 },