Pin Interface and Endpoint to the model that defines them

Both names were pinned twice, to itc-land and to itc-net. InfoTechCanon's
name-resolution check (INFO-WP-0028) reports that ITC-LAND section 13.2 lists
Interface, Endpoint and API as pointers into the software and solution domain
without defining them, while the Network Model defines and owns both. The
itc-land pins are dropped; itc-net already carried them.

This is a citation fix, not a change of position. The accepted boundary already
treats the Landscape Interface seed and the Network attachment-point Interface as
contextual mappings rather than universal exact aliases, and the mapping tables
that cite ITC-LAND section 13.2 as a related seed stay as they are.

SoftwareSystem and SoftwareComponent keep their itc-land pins and now resolve:
InfoTechCanon declared them under INFO-WP-0027-T04 after finding they sat in a
seed-concept list its extraction could not read.

All 23 declared imports now resolve to the artifact they are pinned to.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 3588@bnt-lap001
Assistant-Session: 24b80f66-e5a7-4e61-99fe-2d422e6d17da

infospace/models/interface/imports.json

@@ -9,11 +9,10 @@
       "path": "infospace/models/landscape/InfoTechCanonLandscapeModel.md",
       "sha256": "4190b044fbd5e3eecf7b28e08608e99c7de3af5dd5f3a7554edee02423967fb1",
       "concepts": [
-        "Interface",
-        "Endpoint",
         "SoftwareSystem",
         "SoftwareComponent"
-      ]
+      ],
+      "note": "Interface and Endpoint were pinned here and to itc-net. ITC-LAND section 13.2 lists them as pointers; the Network Model defines and owns them, so they are pinned to itc-net alone. Corrected 2026-09-20 after InfoTechCanon INFO-WP-0028 name resolution."
     },
     {
       "model": "itc-ident",