@functional-systems/srcx 0.1.0-dev.1

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/README.md

@@ -0,0 +1,209 @@
+# srcx
+
+Version-aware code search on LambdaDB. Import a committed Git tree, search its
+chunks, and read exact source pinned to a validated immutable version.
+
+This is an experimental development CLI. Local fixture, fault-injection, SDK transport,
+and opt-in live acceptance checks are available. The npm package is prepared for
+publication but remains unpublished. See [VALIDATION.md](VALIDATION.md) for the latest observed results and
+remaining scope, and [DESIGN.md](DESIGN.md) for the full design.
+
+## Run locally
+
+Requires Node.js 22.14+ and Git. The initial preset uses lexical search with
+`embedding=none`; no embedding account or paid API is needed.
+
+```sh
+npm ci --ignore-scripts
+npm test
+npm run demo
+node dist/cli.js --help
+```
+
+`npm run demo` creates a synthetic two-commit Git repository and exercises the
+publication/search/read workflow through the internal fault-injection store.
+It writes `.srcx/demo-report.json`, including paths to retained local build
+artifacts. It does not contact LambdaDB. The model's lexical matching is a test
+convenience, not a Lucene implementation or a relevance benchmark.
+
+All commands return JSON, except help and errors. Use `node dist/cli.js` in this
+checkout; `srcx` is the configured executable name for future distribution.
+
+For development branches, CI, and installed-package checks, see
+[CONTRIBUTING.md](CONTRIBUTING.md). Version channels, first-publication steps, and
+the initially disabled npm automation are documented in [RELEASING.md](RELEASING.md).
+The project is licensed under [Apache-2.0](LICENSE).
+
+## Preview a committed version without credentials
+
+```sh
+node dist/cli.js import --path /path/to/repo --ref main --dry-run \
+  --output /tmp/srcx-build-a
+
+# Compare a second selected commit with the first artifact.
+node dist/cli.js import --path /path/to/repo --ref <full-commit-B> --dry-run \
+  --previous /tmp/srcx-build-a --output /tmp/srcx-build-b
+```
+
+The output directory must be new and its parent must exist. The command resolves
+the ref once, reads Git tree/blob objects, and ignores working-tree edits. Local
+branches, lightweight/annotated commit tags, and commit OIDs are accepted. Branch
+and tag names that collide require `refs/heads/...` or `refs/tags/...`. No automatic
+fetch, history replay, or revision expressions are supported.
+
+Each artifact contains `build.json` (inventory, configuration, counts, hashes,
+change/deletion plan) and `records.jsonl` (exact file records and retrieval chunks).
+Artifacts contain source code; keep them with the same access policy as the repo.
+Every tree entry is accounted for, including explicit exclusions for symlinks,
+submodules, LFS pointers, dependencies/build output, binary/invalid UTF-8 data,
+invalid UTF-8 paths, and files above 1 MiB. Excluded paths are preserved losslessly
+in `pathBase64`.
+
+Java, TypeScript/TSX, and JavaScript use pinned Tree-sitter WASM grammars. Markdown
+uses heading/paragraph/fence boundaries; configuration text uses section/line
+boundaries. Parse errors and unsupported languages use recorded text fallback.
+Chunks cover the exact source bytes, carry one-based line ranges, target 800 tokens,
+and stay below 1,500 tokens including path/symbol context. The internal window
+baseline is available to the test/build API, not as a public storage backend.
+
+## Explicit live acceptance run
+
+The live harness accepts `LAMBDADB_BASE_URL`, `LAMBDADB_PROJECT_NAME`, and
+`LAMBDADB_PROJECT_API_KEY` from your ignored `.env.local` file:
+
+```sh
+npm run test:live
+# Increase the per-version wait deadline if the service indexes slowly.
+SRCX_LIVE_TIMEOUT_MS=300000 npm run test:live
+```
+
+Node explicitly loads the env file for this command. The application does not
+implicitly source repository env files or save the key. The harness uses only its
+synthetic Git fixture, creates one Collection with test metadata, and retains the
+remote resources, local retry journals, and `.srcx/live/report.json` for review.
+It saves connection settings under `.srcx/live/config.json` and keeps its state
+separate under `.srcx/live/state`. Rerunning resumes the saved synthetic run and
+refuses to reuse it against a different destination.
+
+## Connected workflow
+
+These commands create and write LambdaDB resources. Select an approved project
+and source scope before running them. Start live validation with the synthetic
+fixture, not a production repository.
+
+```sh
+# Supply LAMBDADB_API_KEY through your shell or secret manager.
+node dist/cli.js configure --endpoint https://api.lambdadb.ai --project <project>
+node dist/cli.js doctor
+node dist/cli.js repo add --path /path/to/repo \
+  --description "Repository source, tests, and documentation for code search." \
+  --tag team=search
+node dist/cli.js repo list
+node dist/cli.js repo show --repo <name>
+
+# Import the exact artifact reviewed in the credential-free preview.
+node dist/cli.js import --repo <name> --artifact /tmp/srcx-build-a
+node dist/cli.js versions --repo <name>
+node dist/cli.js search --repo <name> --version <full-commit-A> --query retry
+node dist/cli.js read --result <result-id> --context 20
+node dist/cli.js read --result <result-id> --full-file
+node dist/cli.js read --repo <name> --version <full-commit-A> \
+  --path src/example.ts --lines 10:30
+
+node dist/cli.js import --repo <name> --artifact /tmp/srcx-build-b
+# An old A result still reads A after B is published.
+node dist/cli.js read --result <result-id> --full-file
+
+node dist/cli.js git sync-tags --repo <name>
+node dist/cli.js resolve --repo <name> --ref v1.0.0
+```
+
+`doctor` checks authentication and Collection read access, not write permission
+or indexing/query readiness. `configure --api-key-env NAME` selects another
+credential environment variable; only its name is stored. Endpoint/project changes
+cannot silently redirect result handles or retry journals.
+
+Collection descriptions and metadata labels are used for repository context.
+Discovery reads LambdaDB Collections and main-Branch descriptors, not a local
+repository registry. Short names must be unique; otherwise use the complete source
+identity or Collection name. Registration normalizes the selected Git remote;
+`origin` is default. Use `--remote upstream` explicitly when needed. Repositories
+without remotes receive a persistent local source identity. Repeated registration
+preserves existing descriptions/labels and attaches the local checkout.
+
+Search is literal analyzed lexical text, restricted to `kind=chunk`. Optional
+`--path` and `--language` filters are exact keyword filters. `--limit` is 1–100.
+Search results include a durable local `resultId`, commit, immutable Tag/Snapshot,
+path, lines, and citation. Reads verify the original content hash and refuse
+missing/recreated Tags. A direct path read defaults to the whole file; line ranges
+are one-based and inclusive.
+
+## Publication and recovery
+
+The control Branch `main` holds descriptors/version summaries. `checkpoint-empty`
+is forked before any control write. Each import uses a new `work-*` Branch,
+optionally forked from the last locally retained, remotely validated writer
+baseline. Writers are frozen after publication. A fresh local state can start a
+full import from `checkpoint-empty`; source data is never forked from a Tag.
+
+The importer deletes obsolete IDs, upserts changed records and inventory parts in
+bounded sequential requests, then sends `__manifest__` **alone** after every prior
+ACK. It polls the writer with `consistentRead=false`, creates a unique candidate
+Tag, and checks its marker, complete document IDs/hashes, source coverage, and a
+representative lexical query. Only a validated candidate is copied to the canonical
+`ver-*` Tag and recorded as published. Full candidate validation protects against
+an early/stale snapshot even after the marker is observed.
+
+A per-Collection local lock and durable `pending.json` journal prevent another
+commit from overwriting a partial attempt. Only one importing host is supported.
+After a timeout or unknown write result, retain the artifacts and journal:
+
+```sh
+node dist/cli.js import --repo <name> --artifact /path/from/pending.json \
+  --resume --timeout 180
+```
+
+A write-stage resume replays the same explicit obsolete IDs and replacements under
+exclusive ownership. It needs the pending build's artifact and journal, but not
+the previous published build's local artifact: the journal identifies the immutable
+remote baseline. Build validation checks that the full Git commit OID, repository,
+and configuration agree with the build ID before publication.
+A waiting-stage resume does not rewrite the corpus. SDK
+transparent retries are disabled. If the process crashes while holding
+`writer.lock`, first verify the recorded process is no longer importing, then
+remove that specific lock directory. Do not delete `pending.json` to force a new
+commit over an uncertain workspace. Unexpected baselines fail closed; automatic
+recovery to a new workspace and resource cleanup are not implemented yet.
+
+Git tag synchronization observes local `refs/tags/*` only. Multiple Git tags for
+one commit create separate `rel-*` Aliases targeting the same published Tag.
+An unimported/moved target is pending; the previously pinned version remains usable
+but does not masquerade as the current release. Run `git sync-tags` again after
+importing the target. Absence in a local clone never deletes a remote Alias.
+For search and resolve, a synchronized Git tag name takes precedence over a commit
+prefix, matching Git import's tag-before-OID rule. A pending tag fails explicitly
+instead of falling back to a matching commit prefix. Use `refs/tags/<name>` to
+select a Git tag explicitly.
+Explicit authoritative pruning and persistent tracked-branch synchronization are
+follow-up work; no full history import is required.
+
+## State and implementation map
+
+Configuration: `$XDG_CONFIG_HOME/srcx/config.json` or `~/.config/srcx/config.json`.
+State: `$XDG_STATE_HOME/srcx` or `~/.local/state/srcx`. Test/isolated overrides are
+`SRCX_CONFIG` and `SRCX_STATE_DIR`. State includes checkout attachments, local-source
+IDs, build artifacts, publication journals, and result handles. Remote repository
+and publication records remain authoritative.
+
+| Files                                                                                | Responsibility                                                          |
+| ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------- |
+| [src/cli.ts](src/cli.ts), [src/settings.ts](src/settings.ts)                         | CLI and secret-reference-only configuration                             |
+| [src/git.ts](src/git.ts), [src/chunk.ts](src/chunk.ts), [src/build.ts](src/build.ts) | Git object inventory, bounded chunks, reproducible artifacts            |
+| [src/remote.ts](src/remote.ts), [src/repository.ts](src/repository.ts)               | LambdaDB SDK boundary, provisioning, remote discovery                   |
+| [src/publish.ts](src/publish.ts)                                                     | Journal, ordering barrier, immutable validation/publication             |
+| [src/search.ts](src/search.ts), [src/releases.ts](src/releases.ts)                   | Pinned search/read and Git-tag Aliases                                  |
+| [src/common.ts](src/common.ts)                                                       | Canonical hashing and atomic local JSON writes                          |
+| [test/](test/), [scripts/demo.mjs](scripts/demo.mjs)                                 | Local fixtures, fault injection, SDK loopback contract, repeatable demo |
+
+`npm run typecheck`, `npm test`, and `npm run format:check` are the local checks.
+See the validation record before treating these checks as live-service evidence.

package/RELEASING.md

@@ -0,0 +1,137 @@
+# Releasing srcx
+
+## Current state
+
+The source is prepared as `@functional-systems/srcx@0.1.0-dev.1` under Apache-2.0.
+It has not been published to npm. `private: false` permits a reviewed first
+publication; it does not establish registry availability or distribution readiness.
+`NPM_DEV_PUBLISH_ENABLED` is initially `false`. No stable/rc release or Homebrew
+formula has been published. Local/live application evidence is in
+[VALIDATION.md](VALIDATION.md); it is separate from package publication evidence.
+
+This workflow follows [LambdaDB CLI](https://github.com/lambdadb/lambdadb-cli/blob/develop/RELEASING.md).
+The repository keeps Prettier plus strict TypeScript checks as its existing lint
+baseline rather than adding a second style system.
+
+## Branches, versions, and channels
+
+| Source                  | Package version | Trigger                                         | npm dist-tag |
+| ----------------------- | --------------- | ----------------------------------------------- | ------------ |
+| `develop`               | `X.Y.Z-dev.N`   | Successful push CI, with dev publishing enabled | `dev`        |
+| Reviewed `main` history | `X.Y.Z-rc.N`    | Published GitHub prerelease `vX.Y.Z-rc.N`       | `rc`         |
+| Reviewed `main` history | `X.Y.Z`         | Published GitHub release `vX.Y.Z`               | `latest`     |
+
+Only these version forms are accepted. Update `package.json` and both root
+version entries in `package-lock.json` together, for example using
+`npm version VERSION --no-git-tag-version`. CLI `--version` reads package metadata.
+For explicit releases, add a dated `## [VERSION] - YYYY-MM-DD` changelog section.
+The GitHub tag must match the version, and the prerelease flag must match its channel.
+`latest`, not the tip of `main`, identifies the stable npm release.
+
+The checked-in development base starts at `0.1.0-dev.1`. During an eligible push,
+`scripts/dev-release.mjs` replaces `N` with the full history's first-parent commit
+count, updating package/lock versions and `gitHead` only in the runner. It creates
+no version-bump commit, Git tag, or GitHub Release. The same commit yields the same
+version; counters may skip unpublished commits. Change the release base through
+a reviewed PR when starting the next line. Preserve branch history.
+
+## CI and publication gates
+
+`.github/workflows/publish.yaml` validates PRs and pushes to `main`/`develop`,
+manual CI runs, and published GitHub Releases. Node 22/24 validation must succeed
+before publishing. PRs, main pushes, and manual CI runs cannot publish dev builds.
+Only the publishing job receives `id-token: write`; validation has read-only
+GitHub permissions and no LambdaDB service keys.
+
+Publication packs once, tests that exact tarball through a clean installation,
+and publishes the same file with provenance. Do not replace it with a repacked
+artifact after testing. The package includes runtime JavaScript, source maps and
+their source files, and public docs/license; it excludes tests, workflows,
+scripts, `.env`, and `.srcx` state. Production dependencies supply the parser
+WASM assets; package tests exercise parsing with install scripts disabled.
+
+Dev jobs are serialized without canceling an active registry write. They check
+the current remote develop head and existing registry artifact/tag state before
+publication, skip stale or superseded work, and reject conflicting artifacts.
+An identical rerun skips writing only when source SHA, tarball integrity, version,
+and `dev` tag agree. `latest` is not changed by ordinary development publication.
+
+Registry writes are never automatically retried. Successful dev writes are
+followed by bounded reads for up to five minutes, checking commit, integrity, and
+dist-tag. A `published-verification-pending` failure means publication succeeded
+but verification is incomplete: inspect registry state before retrying the job.
+Do not republish, overwrite versions, or move release tags to work around lag.
+
+## First publication and Trusted Publisher setup
+
+Complete these steps from a reviewed, validated commit after this setup PR merges:
+
+1. Verify npm ownership for the `functional-systems` scope and the package name.
+   GitHub organization membership does not establish npm permissions.
+2. Run the validation commands in [CONTRIBUTING.md](CONTRIBUTING.md). Retain
+   credentialed live acceptance evidence for the exact release candidate; PR CI
+   deliberately does not run service checks.
+3. Prepare the first actual `0.1.0-dev.1` tarball, inspect its inventory, and test
+   it with `npm run test:package -- /absolute/path/to/package.tgz`.
+4. With explicit release authorization and npm login/MFA, publish that tested
+   artifact using `npm publish /absolute/path/to/package.tgz --access public --tag dev`.
+   This one-time local bootstrap does not have GitHub Actions provenance.
+   Check all dist-tags afterward: initial publication can also create `latest`.
+   Do not represent that prerelease as a stable release or silently rewrite tags.
+5. Configure this package's npm Trusted Publisher with the values below. Enable
+   direct `npm publish` permission for the workflow, which does not use staged
+   publication. Another LambdaDB package's trust configuration does not cover srcx.
+6. After registry and trust setup are verified, enable the GitHub repository
+   variable `NPM_DEV_PUBLISH_ENABLED=true`. This authorizes ongoing publication
+   from eligible develop pushes; enabling the variable alone does not trigger one.
+   Verify the first subsequent dev workflow, registry metadata, provenance, and
+   clean consumer install before reporting automatic publication as operational.
+
+| Setting                   | Value                      |
+| ------------------------- | -------------------------- |
+| npm package               | `@functional-systems/srcx` |
+| GitHub organization       | `lambdadb`                 |
+| Repository                | `srcx`                     |
+| Workflow filename         | `publish.yaml`             |
+| GitHub environment        | None configured            |
+| Allowed publish operation | `npm publish`              |
+
+Use GitHub-hosted runners and npm >=11.5.1. The workflow uses Node 24 for publishing
+and checks npm's version. See the current [npm Trusted Publishing documentation](https://docs.npmjs.com/trusted-publishers/)
+and [npm trust command](https://docs.npmjs.com/cli/v11/commands/npm-trust/) when
+configuring the package; registry requirements can change independently.
+Do not store long-lived npm write tokens or LambdaDB keys in this workflow.
+
+## Explicit rc/stable release
+
+1. Prepare the version, lockfile, changelog, dependency changes, and migration notes
+   on a release branch. Pass local/CI/package checks and live acceptance for the
+   candidate. Preserve the tested artifact and evidence.
+2. Promote through a reviewed PR into `main`. Revalidate if release contents change.
+3. After explicit authorization, tag the verified commit as `vVERSION`, push it,
+   and publish a GitHub Release. Use prerelease=true for rc and false for stable.
+   A draft Release does not publish npm. Development versions use the dev workflow.
+4. The workflow verifies main ancestry and metadata, tests the exact packed
+   artifact, and publishes to `rc` or `latest` with provenance.
+5. Verify the registry version/dist-tag, integrity, provenance repository/commit,
+   and clean installed binary. Synchronize release-only changes back to develop
+   with the next intended development base.
+
+Read-only verification:
+
+```sh
+npm view @functional-systems/srcx dist-tags --json
+npm view @functional-systems/srcx@VERSION version gitHead dist.integrity dist.attestations --json
+```
+
+For a bad release, stop promotion and prepare a new patch. Deprecation and dist-tag
+changes require explicit maintainer action; do not silently downgrade consumers.
+
+## Homebrew
+
+Add a formula to `lambdadb/homebrew-tap` after the first verified stable npm release.
+Follow the CLI pattern: exact npm tarball and checksum, lockfile from the matching
+immutable source commit, production dependencies installed without scripts,
+and an exposed `srcx` executable. Validate installation on macOS and Linux before
+a separate tap PR. No placeholder formula, tap write, or automatic Homebrew update
+is part of this setup. Dev and rc builds do not update Homebrew.