chore: remove dead rettime mock, fix license header typo

- Delete test/__mocks__/rettime.cjs — never loaded (wrong directory for
  auto-mocking, no moduleNameMapper, msw CJS doesn't require rettime directly)
- Fix Apache 2.0 header in utils.test.mjs: 'LICENSE' → 'License'

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: sirugh

.claude/settings.local.json

@@ -0,0 +1,8 @@
+{
+  "permissions": {
+    "allow": [
+      "mcp__adobe-slack__slack_get_thread_replies",
+      "mcp__adobe-slack__slack_reply_to_thread"
+    ]
+  }
+}

911GhostwhiteSheep-3655614-Stage.json

@@ -0,0 +1,33 @@
+{
+  "project": {
+    "id": "4566206088345479983",
+    "name": "911GhostwhiteSheep",
+    "title": "Storefront Prerenderer PDP and PLP",
+    "org": {
+      "id": "3655614",
+      "name": "Adobe Commerce Optimizer Internal",
+      "ims_org_id": "77C920686809469C0A495FE5@AdobeOrg"
+    },
+    "workspace": {
+      "id": "4566206088345506001",
+      "name": "Stage",
+      "title": "Stage",
+      "action_url": "https://3655614-911ghostwhitesheep-stage.adobeioruntime.net",
+      "app_url": "https://3655614-911ghostwhitesheep-stage.adobeio-static.net",
+      "details": {
+        "credentials": [],
+        "services": [],
+        "runtime": {
+          "namespaces": [
+            {
+              "name": "3655614-911ghostwhitesheep-stage",
+              "auth": "92f9ac16-885e-4364-93cc-930399f71043:kPANXAtLi2wNmF6Ps58v41Xsf4gHKl2W3bu5WppB22QbIH37085J1dxDrMqod4bh"
+            }
+          ]
+        },
+        "events": { "registrations": [] },
+        "mesh": {}
+      }
+    }
+  }
+}

KT Questions.md

@@ -0,0 +1,72 @@
+# KT Questions
+
+## Existing
+
+1. What is the use case for the setup wizard?
+1. What is the difference between the wizard and bin/setup/index.js?
+
+one is ui, one is api but there may be overlap - please call out in issues
+
+1. Why is the roles defined in setup/index.js different than the roles defined in setup-wizard.js?
+
+only need publish
+
+1. https://prerender.aem-storefront.com/ - what is this?
+
+- repo in adobe-rnd: https://github.com/adobe-rnd/aem-commerce-prerender-ui
+- gets url of overlay where markup is stored, automatically used by wizard but before wizard, you had to manually set it
+- form submit at end of wizard to prerender.aem-storefront.com with creds to create context in local storage for interface
+
+1. What is content url, products template, and commerce store url and why do they need defined in the setup wizard?
+
+They should prepopulate from org/site - if they did not it is a bug.
+Only relevant if merchant has different paths.
+path format likely needs to be changed.
+Template depends on locales or not.
+
+1. Is there any code that needs removed or refactored?
+
+github issues reference relevant.
+do not consider low priority issues (see label)
+others, recommend to start working
+generic code cleanup issue would be good
+for prerender setup, and "prerender"
+
+1. What do you wish could be done before you return from PTO
+
+p0:
+
+- Alberto is mostly worried about existing customer support.
+- In JIRA, priority tickets such as to fix DKV.
+
+p1: next/generic ssg issues, cleanup, etc.
+
+In reference impl, we do not show anything more than the markup.
+The rest of the pdp page loads as usual. Up to customer to embed further information.
+
+1. How can I view, assess, and regenerate the index file?
+
+1. How can I refresh products?
+
+
+
+
+## New Features
+
+1. If I wanted to add a new fetcher for categories, where do I put that? actions/fetch-all-categories/index.js?
+
+1. Could we obtain more "dynamic" things, such as the graphql operations, templates, etc, from a service? Queries can change, and we have hardcoded them here.
+1. Since product details query are prerendered, what happens if customer has custom query? For example, if they want to extend or override certain fields?
+
+	Yes - make issue. It is ref impl, but maybe ways to make more generic/customizable rather than having to change code files directly.
+
+1. Is there a reason we did not use a multi-tenant approach?
+
+* catalog service public events were not yet available when this was built.
+* all events trigger change, so would be too noisy - would have to keep a cache/etc to reduce
+* poller allows customer to be in control of what/when they want to trigger
+* rendering process is heavily customized
+
+1. Would you be interested in moving UI flows to storefront-tools?
+
+Yes - shared with Alberto

test/__mocks__/rettime.cjs

@@ -5,7 +5,7 @@ you may not use this file except in compliance with the License. You may obtain
 of the License at http://www.apache.org/licenses/LICENSE-2.0
 
 Unless required by applicable law or agreed to in writing, software distributed under
-the LICENSE is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR REPRESENTATIONS
+the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR REPRESENTATIONS
 OF ANY KIND, either express or implied. See the License for the specific language
 governing permissions and limitations under the License.
 */