superdev-cli 0.1.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,33 @@
+{
+  "name": "superdev",
+  "owner": {
+    "name": "Rahul Retnan"
+  },
+  "metadata": {
+    "description": "Superdev - tell it what you want to build, and it keeps the product map, documentation, decisions and status in step while specialist providers do the specialist work.",
+    "version": "0.1.0",
+    "homepage": "https://github.com/superdev-ai/superdev"
+  },
+  "plugins": [
+    {
+      "name": "superdev",
+      "source": "./",
+      "description": "Describe a product in ordinary language and get a living map of goals, features, workflows, tasks, integrations, UI surfaces, decisions and evidence - plus a self-contained visual dashboard. Routes specialist work to external providers and reports their readiness truthfully.",
+      "version": "0.1.0",
+      "author": {
+        "name": "Rahul Retnan"
+      },
+      "keywords": [
+        "product-map",
+        "project-status",
+        "dashboard",
+        "decisions",
+        "documentation-sync",
+        "evidence-based-completion",
+        "orchestration"
+      ],
+      "category": "developer-tools",
+      "homepage": "https://github.com/superdev-ai/superdev"
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,21 @@
+{
+  "name": "superdev",
+  "version": "0.1.0",
+  "description": "Describe a product in ordinary language and get a living map of goals, features, workflows, tasks, integrations, UI surfaces, decisions and evidence, plus a self-contained visual dashboard. Routes specialist work to external providers and reports their readiness truthfully.",
+  "author": {
+    "name": "Rahul Retnan"
+  },
+  "keywords": [
+    "orchestration",
+    "project-record",
+    "specifications",
+    "decisions",
+    "documentation-sync",
+    "verification"
+  ],
+  "homepage": "https://github.com/superdev-ai/superdev",
+  "repository": "https://github.com/superdev-ai/superdev",
+  "requires": {
+    "cli": "0.1.0"
+  }
+}

package/.codex-plugin/plugin.json

@@ -0,0 +1,27 @@
+{
+  "name": "superdev",
+  "version": "0.1.0",
+  "description": "Describe a product in ordinary language and get a living map of goals, features, workflows, tasks, integrations, UI surfaces, decisions and evidence, plus a self-contained visual dashboard.",
+  "author": {
+    "name": "Rahul Retnan"
+  },
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "Superdev",
+    "shortDescription": "Turn a plain-language product idea into a tracked, verified, visible project.",
+    "longDescription": "Tell Superdev what you want to build. It asks the few questions that change the product, then maintains a living map of goals, features, workflows, tasks, integrations, technologies, UI surfaces, decisions, blockers and evidence as human-readable records in your repository. Progress is counted from declared deliverables and attached verification, never asserted, and a feature cannot be complete while a criterion lacks evidence. Work that drifts from the goal, such as an unmapped task, a feature supporting no goal, or a request contradicting an accepted decision, becomes a visible warning rather than a silent change. Specialist work is routed to external providers, whose readiness is reported for the harness you are actually in. A self-contained HTML dashboard shows the whole project, including a pannable product canvas, the critical path, plan versus actual, and timeline playback. On Codex, lifecycle hooks require explicit per-hook trust; until trusted, ask for project status directly ,  it reconciles from the canonical records either way.",
+    "developerName": "Rahul Retnan",
+    "category": "developer-tools",
+    "capabilities": [
+      "Interactive",
+      "Read",
+      "Write"
+    ],
+    "defaultPrompt": "Show me this project's status, or tell me what you want to build."
+  },
+  "homepage": "https://github.com/superdev-ai/superdev",
+  "repository": "https://github.com/superdev-ai/superdev",
+  "requires": {
+    "cli": "0.1.0"
+  }
+}

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,109 @@
+# Contributor covenant code of conduct
+
+## Standing of this document
+
+This applies to the issues, pull requests and discussions on
+https://github.com/superdev-ai/superdev, and to anywhere somebody is
+representing the project. It was adopted before the first outside contributor
+arrived rather than written in reaction to an incident, which is the only good
+time to write one.
+
+## Our pledge
+
+We as members, contributors and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, colour, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive and healthy community.
+
+## Our standards
+
+Examples of behaviour that contributes to a positive environment:
+
+- Demonstrating empathy and kindness toward other people.
+- Being respectful of differing opinions, viewpoints and experiences.
+- Giving and gracefully accepting constructive feedback.
+- Accepting responsibility, apologising to those affected by our mistakes, and
+  learning from the experience.
+- Focusing on what is best for the community, not only for us as individuals.
+
+Examples of unacceptable behaviour:
+
+- The use of sexualised language or imagery, and sexual attention or advances of
+  any kind.
+- Trolling, insulting or derogatory comments, and personal or political attacks.
+- Public or private harassment.
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission.
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting.
+
+## Enforcement responsibilities
+
+The maintainer is responsible for clarifying and enforcing these standards, and
+will take fair corrective action in response to behaviour that is inappropriate,
+threatening, offensive or harmful.
+
+That includes removing, editing or rejecting comments, commits, code, issues and
+other contributions that do not align with this code of conduct, with the reason
+given when it is appropriate to give one.
+
+## Scope
+
+This code of conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Report a concern privately through GitHub, either by opening a private security
+advisory at
+https://github.com/superdev-ai/superdev/security/advisories/new, which is a
+private channel to the maintainer and works for conduct reports as well, or by
+contacting the maintainer through their GitHub profile.
+
+**Do not report a conduct concern in a public issue.** Naming somebody publicly
+before anything has been established is unfair to them and to you.
+
+Every report is read and answered. The reporter's identity is not disclosed to
+the person reported about, or to anyone else, without the reporter's agreement.
+
+This project is maintained by one person, so no response time is promised and
+there is no panel to appeal to. That is a real limit and it is better stated than
+implied: if a concern involves the maintainer, GitHub's own reporting mechanisms
+sit outside this project and are available to you.
+
+## Enforcement guidelines
+
+These guidelines determine the consequences of an action found to be in
+violation of this code of conduct.
+
+1. **Correction.** For inappropriate language or other behaviour deemed
+   unprofessional or unwelcome: a private, written warning
+   providing clarity around the nature of the violation and an
+   explanation of why the behaviour was inappropriate. A public apology may be
+   requested.
+2. **Warning.** For a violation through a single incident or series of actions:
+   a warning with consequences for continued behaviour, including no interaction
+   with the people involved for a specified period. Violating these terms may
+   lead to a temporary or permanent ban.
+3. **Temporary ban.** For a serious violation of community standards, including
+   sustained inappropriate behaviour: a temporary ban from any sort of
+   interaction or public communication with the community for a specified
+   period.
+4. **Permanent ban.** For demonstrating a pattern of violation of community
+   standards, including sustained inappropriate behaviour, harassment of an
+   individual, or aggression toward or disparagement of classes of individuals:
+   a permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This code of conduct is adapted from the Contributor Covenant, version 2.1,
+available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+
+Community impact guidelines were inspired by Mozilla's code of conduct
+enforcement ladder.

package/CONTRIBUTING.md

@@ -0,0 +1,205 @@
+# Contributing to Superdev
+
+Read this before writing anything. This repository rejects work in ways you
+cannot guess from looking at it, and the rules that explain the rejection live
+in four different files. This page collects them.
+
+Issues and pull requests are welcome at
+https://github.com/superdev-ai/superdev. Open an issue before a large change, so
+you do not spend an evening on something that will be refused by a rule you had
+no way to know about.
+
+## What will reject your change
+
+Each of these is enforced by a program, not by a reviewer.
+
+- **No em dash and no emoji.** Anywhere in project-owned text, including code
+  comments. `scripts/validate/style.mjs` fails the run. It shares its emoji rule
+  with `src/model/screening.mjs`, the storage boundary, so a file and a database
+  record are judged by the same test. Use a comma, colon, semicolon, parentheses
+  or a plain hyphen.
+- **Tests only on pure functions, and only in one shape.**
+  `scripts/validate/no-tests.mjs` permits a `<source>.test.mjs` beside the source
+  it tests, under `src/` or `scripts/`, run by `node --test`. It fails on any
+  `tests/`, `test/`, `__tests__/`, `spec/` or `fixtures/` tree, on any other test
+  file shape, on a third-party framework in a script or a dependency, and on a
+  test naming a source that does not exist. See
+  `docs/adr/0021-unit-tests-on-pure-functions.md` for why the line is there, and
+  `docs/adr/0019-validators-are-not-tests.md` for what it is protecting.
+
+  Completion is never claimed from a passing count. A task completes on recorded
+  evidence about the real product, and a green suite is not that.
+- **No new imports.** Every `.mjs` and `.js` module under `src/` and `scripts/`
+  may import only `node:` builtins, relative paths, and
+  `@tursodatabase/database`. Only `src/db/connect.mjs` may import that one, so
+  replacing the engine stays a one-file change.
+  `scripts/validate/imports.mjs` enforces it.
+- **No new dependencies.** `scripts/validate/dependencies.mjs` is a named
+  allowlist. It fails on anything else, on an unpinned version, and on an
+  `engines.node` value naming a major other than 20. These rules read the root
+  `package.json` only; they do not reach into `ui/`.
+- **No raw SQL for mutations.** Records are written through `create`, `patch`
+  and `setStatus` in `src/db/store.mjs`, so screening, status history and the
+  activity event cannot be skipped. Every mutation is one transaction that
+  writes an activity event.
+- **No private identifiers.** `scripts/privacy/scan.mjs` blocks on any finding.
+  Absolute home paths, personal email addresses, secret-shaped strings and
+  private project names do not enter the tree. Its binary policy is fail-closed:
+  an unclassified binary file is a P0 finding unless it is listed in
+  `.superdev-scan-binary-allow`.
+
+The wider constraints, including what each module is allowed to know about the
+others, are in `docs/module-contract.md`. Read it before adding a module.
+
+## The validator rule
+
+Superdev has validators, not tests. A validator's subject is a file already in
+the repository, or one it builds deterministically in a temp directory and
+deletes in the same run. It uses no committed fixture and no sample project, no
+test framework and no test runner. It fails rather than skips when its input is
+absent. It asserts a declared property of an artifact, never the behaviour of a
+simulated product.
+
+`scripts/validate/README.md` documents the finding interface, the full table of
+validators, the `SUPERDEV_DENYLIST` contract, and how to add one.
+
+Two validators are worth knowing about specifically:
+
+- `migrations` is the only one that builds its subject. It creates a throwaway
+  database, applies the ordered migration set forward, runs `integrity_check`
+  and `foreign_key_check`, checks the recorded migrations against the
+  checked-in files by version, name and checksum, then provokes the guard
+  triggers and confirms they refuse. It also proves each constraint permits the
+  mapped case, so "always refuses" cannot read as "correctly refuses".
+- `markdown` inspects nothing when the repository has no initialized project. It
+  reports clean because there is nothing to read, not because generated Markdown
+  was verified. Do not treat its clean row as evidence.
+
+## Before you commit
+
+Run these from the repository root. All of them pass on a clean clone.
+
+`validate` fails the run on an error and reports a warning without failing it. On
+a fresh clone three validators warn that they had nothing to check, because the
+project database is git-ignored by design and they read it. That is the expected
+state of a clone, not a problem with it.
+
+```bash
+npm install
+npm test             # unit tests on pure functions, node --test, no framework
+npm run validate     # fifteen validators, in a fixed order, clean today
+npm run scan         # privacy and leak scan of the working tree
+                     # (the staged scan is a separate `scan.mjs --staged` run)
+npm run ui:check     # committed control center matches ui/ source
+```
+
+Or all of the gate at once, which is what a release runs:
+
+```bash
+npm run check        # tests, validators, doctor, the release conditions
+```
+
+Set `SUPERDEV_DENYLIST` when running `validate` if you have a denylist file.
+The privacy validator reads that variable and is fail-closed: pointing it at a
+file that does not exist produces a finding rather than a quiet pass. Note that
+`npm run scan` does **not** read `SUPERDEV_DENYLIST`, because `scan.mjs` accepts
+a denylist only as a command line flag and the npm script does not pass one.
+
+### Verifying a behaviour change
+
+The validators check properties of files, and the unit tests check pure
+functions. Neither runs the CLI end to end, so a change to runtime behaviour is
+still verified by running it, and nothing will catch you if you skip that. Drive it against a throwaway project outside this
+repository:
+
+```bash
+mkdir ../superdev-trial && cd ../superdev-trial
+SD="node /path/to/superdev/src/cli.mjs"
+$SD init --idea "anything" --apply
+$SD doctor
+$SD status
+```
+
+Not inside the checkout. `init` there finds the existing documentation tree,
+reports `Route adopt` and proceeds rather than refusing, so the mistake is
+quiet. Delete the directory afterwards.
+
+Harness and provider readiness is a different program again:
+`node scripts/doctor/doctor.mjs inspect` reports on your machine, while
+`$SD doctor` reports on a project.
+
+### If you touched `ui/`
+
+`ui/` is a separate npm package, `superdev-control-center`, with its own
+dependencies and lockfile. Its `node_modules` and `dist` are git-ignored.
+
+```bash
+cd ui
+npm install
+npm run typecheck    # tsc --noEmit -p tsconfig.app.json
+npm run lint         # oxlint src
+npm run build        # tsc --noEmit && vite build
+cd ..
+npm run ui:build     # regenerates the committed bundle and its manifest
+npm run ui:check
+```
+
+`npm run ui:build` compiles `ui/`, then inlines exactly one CSS chunk and one JS
+chunk into `src/service/assets/control-center.html` and writes
+`control-center.manifest.json`. If there is more than one chunk of either kind
+it stops and names the cause, `build.modulePreload` in `ui/vite.config.ts`,
+rather than shipping half an application.
+
+`npm run ui:check` does not rebuild, despite what ADR-0020 and the script's own
+header comment say. It recomputes a fingerprint over every file under `ui/` and
+compares it, plus the bundle's own hash, against the committed manifest. That is
+enough to detect drift and it detects it immediately.
+
+**Commit the regenerated bundle.** `npm run validate` has no ui validator, so a
+change under `ui/` will pass `validate` while shipping a stale interface.
+
+### The history scan
+
+`npm run scan:history` runs the same privacy rules across every object in git
+history, and it passes on this repository.
+
+It did not pass on the history this project was developed in. A brand asset
+carried a third party's email address in its PNG metadata, and history cannot be
+cleaned without rewriting it, so the public repository starts from a fresh
+initial commit rather than from a rewritten copy of a history that had already
+been distributed. The development history is not public.
+
+That is worth knowing if you add a binary: a file committed once is in history
+forever, and `.gitignore` excludes `*.png` for exactly this reason. Documentation
+images under `docs/images/` are the deliberate exception, and each was checked
+for metadata before being added.
+
+## Style
+
+- Plain language, short sentences. No marketing adjectives.
+- Never "simply", "just", "easy", "powerful", "seamless", "robust".
+- Sentence case in prose. Title Case only for proper nouns.
+- State what a thing does, why it exists, and what it deliberately does not do.
+  Honesty about limits is the house style, not a caveat appended to it.
+- Never claim a capability without having read the code or run the command. In
+  this project an unverifiable claim in the documentation is a defect, not a
+  rough edge.
+
+## Commit messages
+
+Conventional commits, lower case, always with a scope, and a subject that says
+what changed rather than what you did. No validator enforces this, so it is on
+you. The history is the reference:
+
+```text
+feat(providers): prove the provider route end to end
+chore(package): remove generated distribution output
+docs(rebuild): define the Superdev vNext reset
+```
+
+## Recording a decision
+
+Architectural changes get an ADR in `docs/adr/`. Twenty exist. When one
+supersedes another, the superseded body is left exactly as written and a banner
+naming the replacement is added at the top. Rewriting the old reasoning to match
+the new decision destroys the only record of why the old one looked right.

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy 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 CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,11 @@
+Superdev
+Copyright 2026 Rahul Retnan
+
+This product includes software developed by Rahul Retnan and contributors,
+licensed under the Apache License, Version 2.0. See the LICENSE file for the
+full terms.
+
+The local control centre is a compiled bundle that includes third-party
+components under the MIT, ISC and BSD-3-Clause licences. Their copyright and
+permission notices travel with that file and are reproduced in
+THIRD-PARTY-NOTICES.md, which is part of this distribution.