@troylar/sightline 0.0.0-stage → 1.120.2

package/CONTRIBUTING.md

@@ -0,0 +1,67 @@
+# Contribute to Sightline
+
+Start with [vision.md](vision.md), the product charter, then [AGENTS.md](AGENTS.md) and [CLAUDE.md](CLAUDE.md).
+The app stays one self-contained HTML file, with separate plan files and optional trusted helpers.
+
+## Build and verify
+
+You need Node.js 18+, Python 3.10+, Bash and `timeout` on PATH. On macOS, GNU coreutils can provide the timeout command;
+on Windows use a Bash environment with those commands available.
+
+```sh
+npm ci
+./build.sh
+./test/run.sh
+```
+
+Edit **src/sightline.template.html**, never generated **dist/** files. Build before testing: harnesses execute
+the built HTML. See AGENTS.md for focused checks, deterministic dates and the exact runner requirements.
+
+## Keep contributions reviewable
+
+State whether the change touches Jira facts, the plan, viewer preferences or values computed from both.
+For behavior changes add regression coverage in the relevant harness, and prove a fix's check fails on the old
+build. Keep unrelated refactors out. User-visible changes need an entry in **src/releases.json**; the build
+generates the changelog. The npm version must match the newest release.
+
+Every feature that lets people create, edit or delete something must be doable by external assistants too. In the
+same change, add the matching assistant actions (stable ids, preconditions, how Sightline detects they're done, and a
+review level), export the data in the assistant context, update the companion skill and the protocol docs, and test
+it at each assistant level.
+
+Use `type(scope): description` commits. Describe the problem, resulting behavior and validation in the PR.
+Report local tests, CI, deployment and real-world validation separately.
+
+## Every example is invented
+
+Never commit real plans, Jira output, credentials, employer/client identifiers, private screenshots or personal
+filesystem paths. Generate synthetic examples with `python3 tools/make-docs-demo.py`. Review the intended diff
+and run `./tools/check-private.sh` after staging. A missing external private-terms file means that scan skipped;
+it doesn't prove the contribution is safe.
+
+## Maintain the visual guide
+
+Screenshots in **docs/images/** are captured from the built app using the invented Northstar plan. Keep the light
+and dark versions paired, show actual UI and describe any prepared proposals as examples. Never fabricate a live
+AI reply or imply a screenshot verifies cloud sync. [Screenshot capture notes](docs/screenshots.md).
+
+## Prepare a release
+
+Run the build and full suite, inspect `npm pack --dry-run`, then test the real packed tarball in a disposable
+folder. Keep npm's runtime dependencies empty. The package should contain the built HTML, CLI, six skills,
+trusted helpers, synthetic example and documentation, with no local credentials or generated mailbox files.
+Git tags and release assets must match the tested source commit and package version. Publication is a separate,
+deliberate action after validation.
+
+## Keep the first-session promise
+
+The README starts with a working source-build path. Before advertising npm or a release asset, run the
+[public availability checks](docs/availability.md#before-changing-the-advertised-download-route); a dry run
+or changelog entry is not publication evidence.
+
+Keep the [prepared brain-dump session](docs/getting-started.md) reproducible. Its notes, proposal file and
+before/after table must agree. Validate proposals against the invented Northstar plan and inspect the rendered
+storyboard in light/dark and narrow/wide layouts. Keep its prepared-example label visible.
+
+Keep newer capabilities version-labeled until their matching source or artifact is public. Documentation-only
+updates do not need an application version bump.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Troy Larson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,154 @@
-# Temporary Holding Version
+# Sightline
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+<picture>
+  <source media="(max-width: 640px) and (prefers-color-scheme: dark)" srcset="docs/images/roadmap-map-mobile-dark.svg">
+  <source media="(max-width: 640px)" srcset="docs/images/roadmap-map-mobile-light.svg">
+  <source media="(prefers-color-scheme: dark)" srcset="docs/images/roadmap-map-dark.svg">
+  <img src="docs/images/roadmap-map-light.svg" alt="A big roadmap. A clearer way through. An illustrative planning map connects meeting notes, Jira work, and requests to workstreams, shared dependencies, and decisions about scope and capacity." width="1280">
+</picture>
+
+**Sightline is a shared planning workspace for teams managing a large, changing roadmap—with their own AI assistant.**
+
+You have requests in meeting notes, work in Jira, and several teams depending on one another. Everyone knows
+part of the plan. Sightline connects the outcomes, delivery work, people, and decisions so you can work through
+the whole picture together. Your assistant helps organize the complexity; you decide what changes.
+
+<p align="center">
+  <a href="docs/roadmap-planning-example.md"><b>See a planning session</b></a> &nbsp; / &nbsp;
+  <a href="docs/getting-started.md"><b>Try the example</b></a> &nbsp; / &nbsp;
+  <a href="docs/assistant-workflow.md"><b>Bring your AI</b></a>
+</p>
+
+## 1. Get the whole roadmap into view
+
+What are we trying to deliver? What is agreed, and what is still an idea? Start with outcomes across quarters
+and workstreams. Keep later work recoverable without turning every rough request into a dated commitment.
+
+<a href="https://raw.githubusercontent.com/troylar/sightline-planner/main/docs/images/roadmap-light.png" aria-label="Open full-size roadmap screenshot"><picture><source media="(prefers-color-scheme: dark)" srcset="docs/images/roadmap-dark.png"><img src="docs/images/roadmap-light.png" alt="Actual Sightline Roadmap: customer outcomes across four quarters and workstreams, with later work counted outside the window." width="1440"></picture></a>
+
+*Actual app, invented Northstar plan. A target quarter expresses intent; it does not prove capacity.*
+
+## 2. Connect the roadmap to the work behind it
+
+Move from the quarter-level discussion to initiatives, tasks, milestones, and dependencies. Keep work
+**From Jira** alongside work **Added here**. Use saved views to focus on a team or workstream while keeping
+hidden work findable.
+
+<a href="https://raw.githubusercontent.com/troylar/sightline-planner/main/docs/images/timeline-light.png" aria-label="Open full-size timeline screenshot"><picture><source media="(prefers-color-scheme: dark)" srcset="docs/images/timeline-dark.png"><img src="docs/images/timeline-light.png" alt="Actual Sightline Timeline: initiatives and tasks across workstreams, with Jira context and plan work together." width="1440"></picture></a>
+
+*Jira owns issue facts. Sightline owns the plan around them. Arranging work here does not update Jira.*
+
+Roadmap uses the whole plan; Timeline and Capacity retain their own views and filters.
+[Understand views and scope](docs/workspaces.md).
+
+## 3. Use AI to work through the complexity
+
+Bring the messy version: requests, constraints, meeting notes, or a brain dump. Your external AI coding tool
+reads the supplied planning context, reconciles the input against existing work, and helps you think through choices.
+
+> Account for every request. Match it to existing work, flag a possible duplicate, retain it as an idea, or
+> identify a decision. Suggest an arrangement around outcomes. Keep commitments separate from suggestions.
+> Show what we need to know about capacity before deciding what fits. Do not change the plan yet.
+
+<picture>
+  <source media="(max-width: 640px) and (prefers-color-scheme: dark)" srcset="docs/images/planning-decisions-mobile-dark.svg">
+  <source media="(max-width: 640px)" srcset="docs/images/planning-decisions-mobile-light.svg">
+  <source media="(prefers-color-scheme: dark)" srcset="docs/images/planning-decisions-dark.svg">
+  <img src="docs/images/planning-decisions-light.svg" alt="Illustrative planning exercise: ten rough notes become three decisions. Clarify overlapping launch scope; resolve a shared specialist and migration dependency; complete demand evidence when 8 scheduled points exceed 6 configured points and five issues are unestimated." width="1280">
+</picture>
+
+*An invented exercise, not a screenshot or captured AI response. [Follow all ten source notes through the planning session](docs/roadmap-planning-example.md).*
+
+Compare scope, sequencing, and workload options in the conversation. Then ask for proposals for the changes
+you choose. Sightline does not provide an automatic scenario simulator.
+
+**Capacity needs evidence.** Known load, availability, missing estimates, and dependencies matter. An outcome
+count alone cannot tell you what fits. Automatic export of capacity, dependencies, risks, and decisions requires
+**1.96.0+**; public **1.94.0** has narrower roadmap context, so supply additional evidence deliberately. Even the
+richer export covers known scheduled Jira points and configured availability, not every form of demand.
+[Capacity reasoning](docs/large-roadmaps.md#3-ask-what-actually-constrains-delivery) · [Build availability](docs/availability.md).
+
+## 4. Review changes before they become the plan
+
+See before/after values. Apply, edit, or skip each proposal. Use Undo for a just-applied plan edit. Your
+assistant's conversation and proposal file do not silently change the shared plan.
+
+<a href="https://raw.githubusercontent.com/troylar/sightline-planner/main/docs/images/review-light.png" aria-label="Open full-size review screenshot"><picture><source media="(prefers-color-scheme: dark)" srcset="docs/images/review-dark.png"><img src="docs/images/review-light.png" alt="Actual Sightline proposal review: two prepared wording changes, their before and after values, and Apply, Skip, and Edit controls." width="1440"></picture></a>
+
+*Actual review of prepared Northstar wording changes. With an external coding tool, your conversation stays
+in that tool; the nearby in-app chat controls are optional.*
+
+[Try a prepared review yourself](docs/getting-started.md#review-two-changes): move one outcome to an earlier
+quarter and capture another as an unscheduled idea. No AI account needed.
+
+## 5. Keep the plan useful between meetings
+
+Find attention items in **Today**, current work in **Sprint**, and the delivery conversation in **Status update**.
+Use **Customer release notes** for customer wording. Return to Roadmap for the broader direction.
+
+<a href="https://raw.githubusercontent.com/troylar/sightline-planner/main/docs/images/today-light.png" aria-label="Open full-size today screenshot"><picture><source media="(prefers-color-scheme: dark)" srcset="docs/images/today-dark.png"><img src="docs/images/today-light.png" alt="Actual Sightline Today view: team attention and upcoming work, with Jira freshness and coverage." width="1440"></picture></a>
+
+*The same invented plan, viewed for daily attention. Check scope and freshness before relying on the summary.*
+
+Have your assistant prepare a review, turn meeting notes into proposed updates, or draft an explanation of what
+changed from supplied evidence. [Run a team planning session](docs/team-planning.md) · [Explore the six planning skills](docs/skills.md).
+
+## How it works
+
+**One HTML app. A separate plan file. Your own AI tool.**
+
+- Open Sightline in desktop Chrome or Edge. Your plan is JSON or YAML; share it through your team's file service.
+- Connect a private assistant folder. Sightline writes context; your file-capable assistant writes proposals; you review them here. Your tool supplies the model connection.
+- Optionally add the read-only Jira Data Center helper. The page reads its local outputs and never contacts Jira.
+
+There is no planning server or account to set up. Shared files need coordinated editing and handoffs: locks are
+advisory, author names are not verified identities, and a local save does not prove cloud delivery. Use file-service
+permissions for access. The page makes no network requests: its font is embedded too.
+
+[Assistant setup](docs/assistant-workflow.md) · [Jira setup](docs/jira.md) · [Sharing and recovery](docs/onedrive.md).
+
+## Install
+
+Sightline is one HTML file you open in Chrome or Edge, plus optional planning skills for your AI assistant and an
+optional read-only Jira helper. It never writes to Jira. With Node.js 18 or later:
+
+```sh
+npx @troylar/sightline install my-sightline
+```
+
+That creates **my-sightline/** with **sightline.html**, the planning skills in **.sightline/skills/**, and an invented
+example plan in **example/**. Open **my-sightline/sightline.html** and choose **File → Open shared plan…** to open
+**example/plan.json**, or start your own plan. It never replaces a file that's already there; to update, install into
+a new folder and open your plan from the new app. `npx @troylar/sightline helpers` prints the folder that holds the
+Python helpers (the Jira sync and the assistant tools), which need Python 3.10 or later.
+
+## Try it with an invented team plan
+
+To build from source instead, you need Git, Node.js 18+, Python 3.10+, and Bash:
+
+```sh
+git clone https://github.com/troylar/sightline-planner.git sightline
+cd sightline
+npm ci
+./build.sh
+```
+
+Open **dist/sightline.html** in Chrome or Edge. Choose **File → Open shared plan…** and select
+**examples/northstar/plan.json**. [Follow the first-session walkthrough](docs/getting-started.md).
+
+Or give your coding assistant the repository link and ask:
+
+> Clone Sightline into a new folder, read its project instructions, install its development dependencies,
+> and build the HTML. Tell me where to open it and the Northstar example. Preserve any existing checkout.
+
+[Check which version each install route gives you](docs/availability.md).
+
+## Documentation
+
+| Plan | Connect | Operate |
+| --- | --- | --- |
+| [Worked planning session](docs/roadmap-planning-example.md) | [Your AI assistant](docs/assistant-workflow.md) | [Team planning](docs/team-planning.md) |
+| [Large roadmaps and capacity](docs/large-roadmaps.md) | [Jira Data Center](docs/jira.md) | [Views and scope](docs/workspaces.md) |
+| [First session](docs/getting-started.md) | [Planning skills](docs/skills.md) | [Shared-file recovery](docs/onedrive.md) |
+
+[Contributing](CONTRIBUTING.md) · [Release history](CHANGELOG.md) · [MIT license](LICENSE) · [Third-party notices](THIRD-PARTY-NOTICES.md).

package/THIRD-PARTY-NOTICES.md

@@ -0,0 +1,121 @@
+# Third-party notices
+
+The built HTML includes [js-yaml 4.1.0](https://github.com/nodeca/js-yaml),
+Copyright (C) 2011-2015 by Vitaly Puzrin, under the MIT License:
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+The built HTML embeds the [Instrument Sans](https://github.com/Instrument/instrument-sans) font (Latin and Latin
+Extended), Copyright 2022 The Instrument Sans Project Authors, under the SIL Open Font License, Version 1.1:
+
+```
+Copyright 2022 The Instrument Sans Project Authors (https://github.com/Instrument/instrument-sans)
+
+This Font Software is licensed under the SIL Open Font License, Version 1.1.
+This license is copied below, and is also available with a FAQ at:
+https://scripts.sil.org/OFL
+
+
+-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded, 
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.
+```

package/bin/sightline.js

@@ -0,0 +1,78 @@
+#!/usr/bin/env node
+'use strict';
+// Install trusted package assets only. Existing, different files are never replaced.
+const fs = require('node:fs');
+const path = require('node:path');
+const root = path.resolve(__dirname, '..');
+const pkg = require('../package.json');
+
+function filesUnder(dir, prefix = '') {
+  return fs.readdirSync(dir, {withFileTypes:true}).flatMap(entry => {
+    if (entry.isSymbolicLink()) throw new Error('Package assets cannot contain symbolic links.');
+    const rel = path.join(prefix, entry.name);
+    return entry.isDirectory() ? filesUnder(path.join(dir, entry.name), rel) : [rel];
+  });
+}
+function checkPath(target) {
+  const full = path.resolve(target), parts = full.slice(path.parse(full).root.length).split(path.sep);
+  let at = path.parse(full).root;
+  for (const part of parts) {
+    at = path.join(at, part);
+    if (fs.existsSync(at) || (()=>{try { return fs.lstatSync(at).isSymbolicLink(); } catch { return false; }})()) {
+      if (fs.lstatSync(at).isSymbolicLink()) throw new Error('Choose a destination without symbolic links.');
+      if (at !== full && !fs.statSync(at).isDirectory()) throw new Error('A destination parent is a file. Your files were kept.');
+    }
+  }
+}
+function install(target, skillsOnly) {
+  const dest = path.resolve(target);
+  const assets = filesUnder(path.join(root, 'skills')).map(rel => ({
+    from:path.join(root, 'skills', rel), to:path.join(dest, skillsOnly ? '' : '.sightline/skills', rel)
+  }));
+  if (!skillsOnly) {
+    assets.unshift({from:path.join(root, 'dist/sightline.html'), to:path.join(dest, 'sightline.html')});
+    assets.push(...filesUnder(path.join(root, 'examples/northstar')).map(rel => ({
+      from:path.join(root, 'examples/northstar', rel), to:path.join(dest, 'example', rel)
+    })));
+  }
+  // Check the whole batch before writing, including existing links and edited skills.
+  for (const asset of assets) {
+    checkPath(asset.to);
+    if (fs.existsSync(asset.to) && (!fs.statSync(asset.to).isFile() || !fs.readFileSync(asset.to).equals(fs.readFileSync(asset.from)))) {
+      throw new Error('A destination file already differs. Your files were kept. Install into a new folder to update.');
+    }
+  }
+  let written = 0;
+  for (const asset of assets) {
+    if (fs.existsSync(asset.to)) continue;
+    fs.mkdirSync(path.dirname(asset.to), {recursive:true});
+    // Exclusive creation also refuses a file that appeared after the checks above.
+    fs.writeFileSync(asset.to, fs.readFileSync(asset.from), {flag:'wx'}); written++;
+  }
+  console.log(skillsOnly ? `Skills ready in ${dest}` : `Open ${path.join(dest, 'sightline.html')} in Chrome or Edge.`);
+  console.log(`${written} files installed. Existing identical files were kept.`);
+  if (!skillsOnly) console.log('Planning skills: .sightline/skills. Try the invented plan in example/plan.json. Your own plans are kept separate.');
+}
+function main(args) {
+  if (!args.length || ['--help','-h','help'].includes(args[0])) {
+    console.log(`Sightline ${pkg.version} — your team's work, in plain sight.
+
+  sightline install [folder]     Install the HTML app and planning skills
+  sightline skills --to <folder> Install only the planning skills
+  sightline helpers              Print the trusted Python helper directory
+  sightline --version            Show the package version
+
+Install defaults to ./sightline. Existing different files are never overwritten.
+Use a new folder for an update, then open your existing plan from the new app.
+Docs: https://github.com/troylar/sightline-planner#readme`);
+    return;
+  }
+  if (args[0] === '--version' && args.length === 1) return console.log(pkg.version);
+  if (args[0] === 'helpers' && args.length === 1) return console.log(path.join(root, 'dist'));   // the helpers stamped with this app's version
+  if (args[0] === 'install' && args.length <= 2 && (!args[1] || !args[1].startsWith('-'))) return install(args[1] || 'sightline', false);
+  if (args[0] === 'skills' && args.length === 3 && args[1] === '--to' && !args[2].startsWith('-')) return install(args[2], true);
+  throw new Error('Unknown command or argument. Run sightline --help.');
+}
+try { main(process.argv.slice(2)); } catch (error) {
+  console.error('Sightline: ' + error.message); process.exitCode = 1;
+}