servicemap 0.1.44 → 0.1.45

package/README.md

@@ -93,12 +93,12 @@ Use `--no-deploy` to skip the prompt.
 
 ## Contents
 
-- `servicemap/`: installable skill folder
+- `SKILL.md`: installable Servicemap skill entrypoint
 - `bin/servicemap.mjs`: npm CLI entrypoint
-- `servicemap/scripts/scan-project.mjs`: scans a project for service evidence
-- `servicemap/scripts/generate-page.mjs`: creates website routes
-- `servicemap/scripts/generate-desktop-app.mjs`: creates the desktop fallback
-- `servicemap/assets/service-logo-database.json`: 1,000 service logo records
+- `scripts/scan-project.mjs`: scans a project for service evidence
+- `scripts/generate-page.mjs`: creates website routes
+- `scripts/generate-desktop-app.mjs`: creates the desktop fallback
+- `assets/service-logo-database.json`: 1,000 service logo records
 
 ## Validation
 
@@ -109,5 +109,5 @@ node bin/servicemap.mjs --dry-run
 node bin/servicemap.mjs install-skill --agent all --dry-run
 node bin/servicemap.mjs install-skill --targets universal,claude,grok --dry-run
 node bin/servicemap.mjs skills install --agent claude --dry-run
-python3 /Users/dougie/.codex/skills/.system/skill-creator/scripts/quick_validate.py servicemap
+python3 /Users/dougie/.codex/skills/.system/skill-creator/scripts/quick_validate.py .
 ```

package/{servicemap/SKILL.md → SKILL.md}

@@ -34,6 +34,10 @@ If no website can be found, create a desktop app fallback at `servicemap-desktop
     Do not deploy unless the user explicitly says yes.
     If they approve, use the project's existing deployment path, preferring `npm run deploy` when present, then provider-specific project configuration such as Vercel or Netlify.
 11. Report the page or desktop app path, service count, validation run, any services marked low or medium confidence, whether requested email access was enforced, and whether deployment was skipped or completed.
+12. If a desktop app was created and the chat client supports Codex inline follow-ups, end the final response with this button, replacing `<absolute-desktop-app-path>` with the generated app's actual absolute path:
+    `- :codex-followup[Launch Service Map]{prompt="Open a terminal in <absolute-desktop-app-path>, run npm run tauri dev, keep the process running, and tell me when the desktop app opens."}`
+    The button sends a follow-up request to Codex; do not claim that it executes the command directly.
+    If inline follow-ups are unavailable, report the absolute app path and the equivalent `npm run tauri dev` command instead.
 
 ## Safety Rules
 

package/bin/servicemap.mjs

@@ -11,12 +11,22 @@ import { fileURLToPath } from 'node:url';
 const packageRoot = resolve(dirname(fileURLToPath(import.meta.url)), '..');
 const repositoryUrl = 'https://github.com/douglasbrown11/servicemap.git';
 const stableSourceRoot = () => resolve(homedir(), '.servicemap/source');
-const scanScript = resolve(packageRoot, 'servicemap/scripts/scan-project.mjs');
-const pageScript = resolve(packageRoot, 'servicemap/scripts/generate-page.mjs');
-const desktopScript = resolve(packageRoot, 'servicemap/scripts/generate-desktop-app.mjs');
+const skillRoot = packageRoot;
+const scanScript = resolve(skillRoot, 'scripts/scan-project.mjs');
+const pageScript = resolve(skillRoot, 'scripts/generate-page.mjs');
+const desktopScript = resolve(skillRoot, 'scripts/generate-desktop-app.mjs');
 
 const universalRoot = () => resolve(homedir(), '.agents/skills');
 
+function resolveSkillSource(root) {
+  if (existsSync(resolve(root, 'SKILL.md'))) return root;
+
+  const legacyNestedSource = resolve(root, 'servicemap');
+  if (existsSync(resolve(legacyNestedSource, 'SKILL.md'))) return legacyNestedSource;
+
+  return root;
+}
+
 const universalAgents = [
   'Amp',
   'Antigravity',
@@ -633,7 +643,7 @@ async function prepareStableSource(options) {
   const sourceRoot = stableSourceRoot();
   if (options.dryRun) {
     timelineStep(`Would prepare stable source at ${sourceRoot}`);
-    return resolve(sourceRoot, 'servicemap');
+    return resolveSkillSource(sourceRoot);
   }
 
   timelineStep(`Source: ${repositoryUrl}`);
@@ -657,7 +667,7 @@ async function prepareStableSource(options) {
     timelineStep('Repository unavailable; copied packaged source');
   }
 
-  return resolve(sourceRoot, 'servicemap');
+  return resolveSkillSource(sourceRoot);
 }
 
 async function updateStableSource(options) {
@@ -687,11 +697,11 @@ async function installIntoRoot(root, source, method, options) {
 }
 
 async function installSkill(options) {
-  let source = resolve(packageRoot, 'servicemap');
+  let source = resolveSkillSource(skillRoot);
   const method = options.installMethod ?? 'symlink';
 
-  if (!existsSync(source)) {
-    throw new Error(`Bundled skill folder not found: ${source}`);
+  if (!existsSync(resolve(source, 'SKILL.md'))) {
+    throw new Error(`Bundled skill source not found: ${source}`);
   }
 
   if (!['copy', 'symlink'].includes(method)) {
@@ -700,7 +710,7 @@ async function installSkill(options) {
 
   if (method === 'symlink') {
     source = await prepareStableSource(options);
-    if (!existsSync(source) && !options.dryRun) {
+    if (!existsSync(resolve(source, 'SKILL.md')) && !options.dryRun) {
       throw new Error(`Stable skill source not found: ${source}`);
     }
   }

package/package.json

@@ -1,19 +1,23 @@
 {
   "name": "servicemap",
-  "version": "0.1.44",
+  "version": "0.1.45",
   "description": "Generate an internal service map page or desktop app for a software project.",
   "type": "module",
   "bin": {
     "servicemap": "bin/servicemap.mjs"
   },
   "files": [
+    "agents",
+    "assets",
     "bin",
-    "servicemap",
+    "references",
+    "scripts",
+    "SKILL.md",
     "README.md"
   ],
   "scripts": {
     "test": "node bin/servicemap.mjs generate --root demo-project --allow-emails founder@example.com,ops@example.com --dry-run && node bin/servicemap.mjs --root no-website-demo --dry-run && node bin/servicemap.mjs --dry-run && HOME=\"$(mktemp -d)\" node bin/servicemap.mjs && node bin/servicemap.mjs install-skill --agent all --dry-run && node bin/servicemap.mjs install-skill --targets universal,claude,grok --dry-run && node bin/servicemap.mjs install-skill --targets codex,chatgpt,gpt-6-astra --dry-run && node bin/servicemap.mjs skills install --agent claude --dry-run",
-    "validate:skill": "python3 /Users/dougie/.codex/skills/.system/skill-creator/scripts/quick_validate.py servicemap"
+    "validate:skill": "python3 /Users/dougie/.codex/skills/.system/skill-creator/scripts/quick_validate.py ."
   },
   "keywords": [
     "ai-skill",

package/references/website-access-options.md

@@ -0,0 +1,47 @@
+# Website access options for Servicemap
+
+These are proposed ways to deliver a service map to a product's website. They are not all implemented today.
+
+Scan the product's source repositories independently of the destination. Each destination adapter should consume the same service graph.
+
+## 1. Website in the same repository
+
+Find the website application or folder within the product repository. Detect its framework and generate the service map route there.
+
+## 2. Separate local website repository
+
+Use a user-supplied local path, or locate a related checkout in the workspace. Scan the product repository and generate the page in the website checkout.
+
+## 3. Website repository on GitHub or another Git host
+
+Use an authorized Git connection and an explicit repository URL, or resolve a related repository from available evidence. Clone or open the website repository, generate the page, validate it, and propose the change through a pull request or the user's requested workflow.
+
+## 4. Hosting provider connection
+
+Use a provider connection, such as Vercel or Netlify, to identify the hosting project associated with the supplied website domain. Where available, inspect the linked source repository and use it as the page destination. A hosting connection does not necessarily provide access to modify that repository.
+
+## 5. Website builder or CMS
+
+Use the website builder's or CMS's authorized API or plugin to add a page, custom code, or an embedded map, where supported. Adapt the output to the platform's capabilities rather than assuming it accepts a framework route.
+
+## 6. Independently hosted service map
+
+If the main website cannot accept a page, offer a separately hosted map that can be linked from or embedded in the website. Confirm this destination with the user before choosing it as a fallback.
+
+## Shared resolution behavior
+
+- Prefer explicit local paths and repository identifiers over inferred matches.
+- Treat a website URL as a discovery clue, not as write access.
+- Use domain references and hosting configuration to find candidate destinations; ask the user to choose when the evidence is ambiguous.
+- Save the confirmed source-to-destination mapping for subsequent runs from either repository.
+- Validate the generated page using the destination project's build and routing conventions.
+- Follow existing access protection for internal pages and the user's deployment instructions.
+- If destination access is missing, preserve the scan results and explain what access is needed. Do not silently substitute a desktop app for a requested website page.
+
+## Lunifer example
+
+Source: `douglasbrown11/Lunifer`, the product's Xcode app repository.
+
+Website destination: `douglasbrown11/luniferWebsite`, the separate Next.js website repository.
+
+Scan the product repository, then use its service graph to generate `/internalservicemap` in the website repository. The website's own dependencies must not replace the product's service inventory.