pi-jscpd 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,99 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and
+published releases use [Semantic Versioning](https://semver.org/).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-09-05
+
+### Added
+
+- Pi-native `jscpd_run` tool and namespaced `/jscpd` command surface.
+- Pinned jscpd `5.1.2` runtime dependency with project-local, `PATH`, and bundled
+  resolution, plus bounded shell-free process ownership and no runtime download.
+- Exact Effect `3.22.1` runtime foundation with declarative process, filesystem,
+  clock, and Pi service tags, stable typed expected failures, bounded public
+  mapping intent, deterministic test layers, and an AST runtime-boundary gate.
+- Effect-owned bounded child processes, process-tree escalation, serialized jscpd
+  execution, temporary report workspaces, capability probing/caching, and scoped
+  service layers.
+- A shared live bounded-filesystem layer for trusted configuration, canonical
+  path validation, report normalization, exact clone-source ranges, and supported
+  Fallow signal reads, with typed failures and deterministic test layers.
+- Effect-owned baseline generations, changed-file attribution, acknowledgement
+  transactions, verification checkpoints, and typed branch-snapshot persistence,
+  with immutable values and lifecycle-scoped state owners.
+- Scoped Effect scheduling for dirty-generation coalescing, automatic changed
+  checks, interruption-safe cancellation, and acknowledgement-after-delivery Pi
+  transactions without unmanaged background promises or timers.
+- Effect-composed scan, changed, status/session-control, Fallow coexistence,
+  report-decoding, and verification workflows with unchanged bounded public
+  results.
+- One managed Effect runtime and production process/filesystem/clock layer graph
+  per extension instance, with native Pi cancellation, effectful dispatch,
+  idempotent finalizer-aware shutdown, and no nested command/overlay runtimes.
+- Strict normalized jscpd JSON report validation and scope-safe explicit scans.
+- Trusted extension configuration, session controls, branch-local state, and
+  changed-file attribution.
+- Ephemeral session baselines, content-aware clone identity, changed-only
+  findings, acknowledgements, and quiet automatic settled checks.
+- Responsive `/jscpd` overview, shared actionable finding presentation, and
+  ephemeral refactor verification.
+- TUI root-subcommand autocomplete for `/jscpd ` with labeled scan, changed,
+  status, session-control, and help suggestions.
+- Packaged on-demand `jscpd` skill with polyglot scan routing, result
+  interpretation, verification, configuration, Fallow-coexistence, and advisory
+  safety guidance.
+- Conservative Pi Fallow coexistence policy with explicit on-demand and allow
+  choices.
+- Confirmed `pi-jscpd` package identity and a tested Node/Pi/TypeBox
+  compatibility policy.
+- Public CI, dependency-update policy, contribution guidance, security policy,
+  issue forms, pull-request guidance, and release ownership.
+- Exact packed-artifact certification with isolated Pi RPC/tool/TUI-compatible,
+  JSON, print, process-tree shutdown, and temporary-report cleanup checks.
+- Non-publishing release-readiness workflow, provenance/access intent,
+  documentation-link validation, repository-hygiene guards, and release,
+  rollback, and post-release policy.
+- A tag-triggered npm trusted-publishing and GitHub Release workflow based on
+  `pi-fallow`, protected by release metadata and maintainer-approval guards. Its
+  first-publication bootstrap credential is isolated to the lifecycle-disabled
+  publish step and removed after `0.1.0`.
+
+### Changed
+
+- Reworked the `/jscpd` overlay into a Pi Fallow-style findings navigator with
+  framed status/count hierarchy, responsive two-location rows, inline detail,
+  search, scrolling, multi-selection, and bounded editor prompt handoff. The
+  overlay now retains up to 100 findings in memory, initially reveals 10, and
+  loads subsequent 10-item pages manually or when navigation crosses the shown
+  boundary without enlarging configured model/tool output or persisted state.
+- Accepted valid jscpd v5 reports whose token-equivalent second occurrence spans
+  fewer physical lines than the reporter's first-occurrence line count.
+- Added repository jscpd ignore policy for dependency/build artifacts, caches,
+  generated source maps/snapshots, archives, and common polyglot lockfiles.
+- Kept packed-artifact cleanup verification bounded while allowing slower Node 22
+  CI runners enough time to observe completed temporary-directory finalization.
+- Removed superseded process, capability, analyzer, configuration,
+  Fallow-coexistence, baseline, changed-file, command/status, and
+  scheduler/automatic Promise facades; removed the parallel Promise report
+  consumer, direct analyzer filesystem workflow, production test runtime, and
+  filesystem-backed clone/report test facades. Service workflows now expose only
+  their Effect-native production paths; Promise orchestration remains confined to
+  reviewed Pi/TUI and filesystem-infrastructure boundaries.
+- Locked existing command/tool, lifecycle, persistence, cancellation, and bounded
+  presentation behavior before production Effect workflow migration.
+- Completed the ordered Effect runtime migration, legacy-removal audit,
+  documentation pass, supported-Node validation, security checks, and
+  exact-tarball recertification required for the first public release.
+
+### Security
+
+- Project paths, child output, reports, temporary directories, cancellation,
+  configuration trust, and lifecycle cleanup are bounded and fail open.
+
+[Unreleased]: https://github.com/revazi/pi-jscpd/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/revazi/pi-jscpd/releases/tag/v0.1.0

package/CONTRIBUTING.md

@@ -0,0 +1,144 @@
+# Contributing to pi-jscpd
+
+Thanks for helping improve `pi-jscpd`. Changes should preserve the extension's
+quiet, advisory, read-only, bounded, and fail-open behavior. jscpd remains the
+authority for tokenization, clone detection, supported formats, and duplication
+statistics. The Effect runtime architecture is documented in
+[Effect architecture and conformance](docs/effect-architecture.md). Changes must
+preserve those product contracts and the completed runtime boundaries.
+
+## Before opening a change
+
+1. Search the [issue tracker](https://github.com/revazi/pi-jscpd/issues).
+2. Open or select a focused issue before substantial implementation work.
+3. Discuss changes to public commands/tools, configuration, persisted session
+   state, process ownership, or product invariants before coding.
+4. For changes to Effect-owned workflows or runtime boundaries, open a focused
+   issue and preserve the architecture documented in this repository.
+5. Report suspected vulnerabilities privately according to
+   [SECURITY.md](SECURITY.md), not in a public issue.
+
+Feature requests should explain why normal jscpd configuration or Pi's ordinary
+agent flow is insufficient. Do not propose an independent clone detector,
+automatic source edits, surprise binary installation, or mandatory
+JavaScript-only parsing in the core workflow.
+
+## Development setup
+
+Use a host from the [compatibility matrix](docs/compatibility.md). Install the
+locked dependencies without changing global Pi configuration:
+
+```text
+npm ci --ignore-scripts
+npm run docs:check
+npm run repo:hygiene
+npm run check
+npm run pack:certify
+npm run pack:dry-run
+```
+
+`npm run check` validates the active Node/Pi/Effect fixtures, enforces the
+approved Effect runtime boundary, type checks strict ESM TypeScript, runs
+Biome's formatting/lint checks, and executes the network-free test suite. The
+documentation and hygiene checks validate public local links, release metadata,
+ignored/private path policy, package metadata, and the non-publishing readiness
+workflow. `pack:certify` installs and exercises the exact tarball.
+CI repeats those checks on Node 22.19.0 and 24.12.0.
+
+Tests must not require network access, read or modify global Pi configuration,
+write reports into a source tree, or depend on a separately installed jscpd
+binary. Use deterministic fake executables for controlled reports and process
+lifecycle cases. Capability and packed-artifact checks also probe the exact
+jscpd runtime dependency declared by the package. The repository's Fallow
+configuration records that indirect CLI use and disables Fallow clone detection
+so jscpd remains this project's single duplication authority.
+
+## Effect migration rules
+
+- Use Effect for fallible async work, resources, cancellation, concurrency, and
+  shared service state—not to decorate pure functions.
+- Declare capabilities with services/layers and keep the single production
+  runtime in the Pi composition boundary. Process and filesystem services provide
+  live layers but create no independent runtime.
+- Keep `Effect.run*` out of infrastructure, domain, and application modules.
+  Only `src/effect/runtime-boundary.ts` may execute production Effect programs;
+  do not add another runtime bridge.
+- Add characterization tests before converting a boundary, deterministic test
+  layers with the conversion, and interruption/finalizer tests for resources.
+  Filesystem changes must preserve trust gating, canonical containment,
+  no-follow opens, exact byte bounds, atomic decode rejection, and body-free
+  diagnostics. Stateful domain changes must use one owner per layer/facade,
+  preserve immutable snapshots and generation/revision checks, and test stale
+  completion plus competing updates. Scheduler and automatic-check changes must
+  use scoped fibers, preserve explicit-work priority and retry eligibility, and
+  commit acknowledgements only after successful quiet Pi delivery. Application
+  workflows must compose existing service effects, keep public result mapping at
+  one boundary, and leave deterministic comparison/presentation code pure. Only
+  `src/effect/runtime-boundary.ts` may execute Effect; production work must use
+  the single runtime passed from extension composition.
+- Do not add Promise service facades. Promise workflow orchestration is limited
+  to reviewed Pi/TUI host adapters and the filesystem infrastructure boundary;
+  characterization adapters belong under `test/support/`.
+- Do not combine a migration slice with unrelated public behavior changes.
+
+## Pull requests
+
+Keep one concern per pull request and include:
+
+- the problem and user-visible behavior;
+- the issue it closes;
+- tests for success, no-findings, and relevant failure/cancellation paths;
+- documentation for behavior or compatibility changes;
+- for Effect slices, the prerequisite issue, removed legacy path, typed failures,
+  layer graph, interruption/finalizer evidence, and approved runtime boundary;
+  and
+- exact validation performed.
+
+Before requesting review, run:
+
+```text
+npm run format
+npm run docs:check
+npm run repo:hygiene
+npm run check
+npm run pack:certify
+npm run pack:dry-run
+```
+
+The protected `main` branch requires the branch to be current and both
+`Validate (Node 22.19.0)` and `Validate (Node 24.12.0)` to pass. The rule applies
+to administrators, requires resolved review conversations, and blocks force
+pushes and branch deletion. Reviews and CI are evidence, not authorization to
+publish.
+
+Keep credentials, proprietary source, source fragments from jscpd reports,
+private paths, generated reports, local overrides, `.agents/`, and `AGENTS.md`
+out of commits. Contributors remain responsible for reviewing and understanding
+all submitted changes, including AI-assisted changes.
+
+## Dependency updates
+
+Repository vulnerability alerts and Dependabot security updates are enabled.
+Dependabot also checks direct npm dependencies and GitHub Actions monthly. Pi
+0.84 patches and compatible development-tooling updates are grouped. Major
+updates to development tools and Pi minor/major updates are ignored because they
+need deliberate recertification. The minimum TypeBox fixture is excluded from
+scheduled version updates and changes only through a focused compatibility
+review; vulnerability alerts and security updates remain enabled. The Effect
+runtime must be exact-pinned and updated only through a focused architecture and
+compatibility review. GitHub Actions are SHA-pinned and updates must retain
+least-privilege permissions.
+
+A dependency PR must pass both Node jobs. Pi, TypeBox-major, Node-range, and
+workflow changes also require the manual compatibility evidence described in
+[`docs/compatibility.md`](docs/compatibility.md).
+
+## Release ownership
+
+Only [Revaz Zakalashvili](https://github.com/revazi), as package maintainer and
+repository owner, may approve a version, create a tag, configure registry
+publishing, or publish. The manual readiness workflow has no registry credentials
+or write permission and cannot release anything; tagged releases use the
+protected npm workflow. Follow [the release policy](docs/release.md). A
+contributor, reviewer, CODEOWNERS approval, or passing CI does not grant
+publication authority.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Revaz Zakalashvili
+
+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

@@ -0,0 +1,231 @@
+# pi-jscpd
+
+[![CI](https://github.com/revazi/pi-jscpd/actions/workflows/ci.yml/badge.svg)](https://github.com/revazi/pi-jscpd/actions/workflows/ci.yml)
+[![npm](https://img.shields.io/npm/v/pi-jscpd.svg)](https://www.npmjs.com/package/pi-jscpd)
+[![license: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)
+[![GitHub issues](https://img.shields.io/github/issues/revazi/pi-jscpd.svg)](https://github.com/revazi/pi-jscpd/issues)
+
+A quiet, read-only duplication guardrail for the [Pi coding agent](https://github.com/earendil-works/pi), powered by [jscpd](https://github.com/kucherenko/jscpd).
+
+`pi-jscpd` detects duplicate blocks introduced during a Pi session, shows both
+locations, and helps you inspect, refactor, test, and verify the result. jscpd
+remains the source of truth for tokenization, clone detection, supported
+languages, and statistics.
+
+## Install
+
+```sh
+pi install npm:pi-jscpd
+```
+
+The package includes pinned jscpd `5.1.2` and Effect `3.22.1` runtime
+dependencies plus an on-demand `jscpd` agent skill—there is no separate analyzer
+installation and no runtime download.
+Effect owns bounded process execution, analyzer probing, temporary report
+workspaces, adapter serialization, trusted configuration and signal reads,
+canonical source-path validation, baseline generations, changed-file attribution,
+acknowledgement transactions, verification checkpoints, scoped scheduling,
+automatic finding delivery, scan/changed/status/Fallow application workflows,
+and one managed runtime/layer graph per extension instance. Legacy Promise/service
+paths are removed from those layers, and host-launched baseline work is settled at
+lifecycle boundaries. If your project already installs
+a compatible jscpd locally, or `jscpd`/`cpd` is available on `PATH`, the
+extension uses that installation first and keeps the bundled version as a
+fallback.
+
+Start Pi in your project and verify the setup:
+
+```text
+/jscpd status
+```
+
+If no compatible binary is available, the extension stays dormant and Pi
+continues normally.
+
+## Usage
+
+Run `/jscpd` to open the interactive overview. Opening it shows status only; it
+never starts an implicit scan.
+
+| Command | Purpose |
+| --- | --- |
+| `/jscpd` | Open the responsive overview |
+| `/jscpd changed` | Show unacknowledged duplication introduced this session |
+| `/jscpd scan` | Scan the whole project |
+| `/jscpd scan src tests` | Scan specific in-project files or directories |
+| `/jscpd status` | Show binary, configuration, mode, and last-check status |
+| `/jscpd off` | Disable scans for the current session |
+| `/jscpd on` | Re-enable scans for the current session |
+| `/jscpd help` | Show command help |
+
+Pi can use the same operations through the `jscpd_run` tool:
+
+```json
+{
+  "command": "scan",
+  "args": ["src"]
+}
+```
+
+Supported tool commands are `scan`, `changed`, `status`, `off`, `on`, and
+`help`. In TUI mode, `/jscpd ` provides subcommand autocomplete with labels and
+descriptions; selecting `scan` leaves the editor ready for an optional target.
+
+The package also exposes `/skill:jscpd`. Pi advertises only the skill's concise
+description at startup and loads its full workflow guidance on demand when a
+duplication task matches or the user invokes the skill command. The extension
+and `jscpd_run` tool remain usable when skills are disabled.
+
+## How session checks work
+
+At session start, the extension captures one bounded, in-memory project baseline.
+It then tracks successful writes and edits made through Pi's built-in `write`
+and `edit` tools.
+
+After Pi settles, one coalesced background check compares the current project
+with the baseline:
+
+- clean checks stay out of model context;
+- failures remain advisory and available through `/jscpd status`;
+- new duplicate blocks are reported with both locations;
+- existing repository duplication is omitted from changed-only results; and
+- actionable automatic findings never trigger a surprise model turn.
+
+Displayed findings are acknowledged for the active conversation branch so the
+same unchanged block is not repeatedly reported. Baselines, source bytes,
+verification checkpoints, and reports are never persisted.
+
+Manual edits, shell commands, custom mutation tools, deletes, and renames are not
+attributed because Pi does not provide a stable structured file list for them.
+Use `/jscpd scan` when changes happened outside built-in `write` or `edit`.
+
+## Interactive overview
+
+Bare `/jscpd` opens a status-first, Fallow-style bounded TUI with:
+
+- a framed overview of mode, binary, configuration, last check, and explicit
+  changed/project scan actions;
+- a searchable, scrollable findings navigator that retains up to 100 findings,
+  initially shows 10, and reveals the next 10 with `L` or by navigating past the
+  last shown row—without rescanning or changing configuration;
+- both duplicate locations, size, format, session relationship, inline detail,
+  verification, and omission/ambiguity context;
+- `j`/`k`, arrows, Home/End, paging, expand/collapse, search, and multi-selection
+  controls consistent with Pi Fallow's navigator; and
+- a bounded `e`/`a` handoff that closes the overlay and loads selected findings
+  into Pi's editor for user review.
+
+The extra overlay cache is in-memory and TUI-only. `maxFindings` still caps
+model/tool and explicit-command output, and cached findings are not added to
+persisted session state or acknowledgement records. The editor handoff never
+submits a prompt. The overview never edits source, writes jscpd configuration,
+runs project tests, or refactors automatically. In RPC, JSON, and print modes,
+explicit subcommands remain available and the bare command uses a bounded
+non-interactive fallback.
+
+## Configuration
+
+Project configuration is optional:
+
+```text
+.pi/jscpd-guardrail.json
+```
+
+Use `.pi/jscpd-guardrail.local.json` for an ignored local override. Configuration
+is read only after Pi trusts the project.
+
+```json
+{
+  "enabled": true,
+  "timeoutMs": 30000,
+  "maxFindings": 10,
+  "fallowCoexistence": "auto"
+}
+```
+
+| Setting | Default | Allowed values |
+| --- | ---: | --- |
+| `enabled` | `true` | Boolean |
+| `timeoutMs` | `30000` | Integer from `100` to `300000` |
+| `maxFindings` | `10` | Integer from `1` to `100` |
+| `fallowCoexistence` | `auto` | `auto`, `on-demand`, or `allow` |
+
+Clone thresholds, formats, ignore rules, and other detection policy belong in
+jscpd's normal configuration, such as `.jscpd.json` or package-level jscpd
+settings. The extension does not maintain a parallel clone policy.
+
+## Fallow coexistence
+
+Pi Fallow can also detect duplication. With the default `auto` policy,
+`pi-jscpd` conservatively detects supported signs of active Fallow duplication
+analysis and moves automatic jscpd checks to on-demand mode to avoid duplicate
+warnings.
+
+Explicit `/jscpd changed`, project scans, and scoped scans remain available. Set
+`fallowCoexistence` to `allow` when both automatic analyzers are intentional, or
+`on-demand` to disable automatic jscpd checks explicitly.
+
+See [Fallow coexistence](docs/fallow-coexistence.md) for the supported signals
+and limitations.
+
+## Safety and privacy
+
+- Advisory and read-only by default.
+- Never downloads packages at runtime or mutates source.
+- Invokes binaries with argument arrays, never a shell command string.
+- Keeps reports in restrictive temporary directories and removes them after
+  success, failure, timeout, cancellation, or shutdown.
+- Bounds process time, output, report size, findings, paths, and persisted state.
+- Omits source fragments, raw child output, temporary paths, and internal
+  fingerprints from results.
+- Reads extension configuration only for trusted projects.
+- Fails open so analyzer problems do not break the Pi session.
+
+## Requirements
+
+| Component | Supported |
+| --- | --- |
+| Node.js | `>=22.19.0 <23` or `>=24 <25` |
+| Pi packages | `>=0.84.4 <0.85.0` |
+| TypeBox | `>=1.3.7 <2` |
+| Effect | Exact reviewed `3.22.1` runtime foundation |
+| jscpd | Bundled `5.1.2`; compatible project-local or `PATH` v5 installations are preferred |
+
+See the [compatibility policy](docs/compatibility.md) for the exact tested
+fixtures and certification matrix.
+
+## Development
+
+```sh
+npm ci --ignore-scripts
+npm run format
+npm run docs:check
+npm run repo:hygiene
+npm run check
+npm run pack:certify
+```
+
+`npm run check` includes the Effect runtime-boundary architecture gate.
+`npm run release:check` runs the complete documentation, hygiene, compatibility,
+architecture, test, and packed-artifact release gate. Tests are network-free and
+use deterministic fake jscpd executables and Effect layers.
+The repository-owned `.jscpd.json` excludes dependency/build
+artifacts, caches, source maps, snapshots, archives, and common package-manager
+lockfiles while continuing to analyze `src`, `test`, scripts, documentation, and
+workflow files.
+
+Useful documentation:
+
+- [Effect architecture and conformance](docs/effect-architecture.md)
+- [Automatic checkpoint lifecycle](docs/automatic-checkpoint.md)
+- [`/jscpd` overlay contract](docs/overlay-interaction.md)
+- [Fallow coexistence](docs/fallow-coexistence.md)
+- [Compatibility and packed-artifact certification](docs/compatibility.md)
+- [Release preparation and publication policy](docs/release.md)
+- [Contributing](CONTRIBUTING.md)
+- [Security policy](SECURITY.md)
+- [Changelog](CHANGELOG.md)
+
+## License
+
+[MIT](./LICENSE) © 2026 Revaz Zakalashvili

package/SECURITY.md

@@ -0,0 +1,93 @@
+# Security policy
+
+## Supported versions
+
+Security fixes target the latest `0.1.x` release and the `main` branch. Older
+minor lines are unsupported unless this table explicitly says otherwise. The
+manual release-readiness workflow cannot publish or create a release; the
+[release policy](docs/release.md) defines approval, rollback, and post-release
+checks.
+
+| Version | Supported |
+| --- | --- |
+| `0.1.x` | Yes |
+| `< 0.1.0` | No |
+
+The host-version contract is documented in
+[`docs/compatibility.md`](docs/compatibility.md). Forced installations outside
+that contract are unsupported, but reports of issues that affect a supported
+configuration are welcome.
+
+## Reporting a vulnerability
+
+Do **not** open a public issue for a suspected vulnerability. Use GitHub's
+[private vulnerability reporting](https://github.com/revazi/pi-jscpd/security/advisories/new)
+to contact the maintainer. If GitHub does not offer the form, contact the
+repository owner privately through their GitHub profile and ask for a secure
+reporting channel without including vulnerability details in the first message.
+
+Include only what is needed to reproduce and assess the problem:
+
+- affected commit or version;
+- supported Node and Pi versions;
+- operating system;
+- bounded reproduction steps using synthetic source where possible;
+- expected and observed security impact; and
+- whether disclosure is already public or time-sensitive.
+
+Do not send credentials, tokens, proprietary source, full environment dumps,
+raw jscpd fragments, or unrelated filesystem paths. Replace them with minimal
+fixtures and redacted diagnostics.
+
+The maintainer aims to acknowledge a complete report within five business days,
+will coordinate validation and remediation privately, and will discuss a safe
+disclosure timeline with the reporter. This is a best-effort open-source target,
+not a guaranteed service-level agreement. Please allow a reasonable remediation
+window before public disclosure.
+
+## Security boundaries
+
+Security-sensitive behavior includes:
+
+- shell-free executable invocation and cancellation of owned child processes;
+- containment and validation of user-controlled paths;
+- restrictive temporary report ownership and cleanup;
+- bounded child output and strict jscpd report parsing;
+- trusted-only project configuration reads;
+- omission of source fragments and private process output from findings; and
+- exclusion of local overrides, credentials, and private coding-agent context
+  from Git history and npm packages.
+
+The extension is advisory and installs jscpd only as an explicit package
+dependency; it never downloads packages during a Pi session, rewrites project
+configuration, edits source automatically, or treats scan success as permission
+to publish data. Security fixes must preserve those boundaries.
+
+The completed [Effect architecture](docs/effect-architecture.md) preserves and
+strengthens resource ownership. Child-process, temporary-report, and bounded
+filesystem resources now use typed Effect services and scoped file/process
+ownership. Baseline, changed-file, acknowledgement, verification, and session
+snapshot state now use generation/revision-checked Effect owners with bounded
+values. Automatic scheduling uses scoped fibers, interruption-linked abort
+signals, and acknowledgement commit only after successful quiet delivery.
+Scan, changed, status, and Fallow application workflows compose these typed
+services without nested Promise error handling; bounded public failures remain
+the only operational output. Trusted configuration, report paths, clone source
+ranges, and Fallow signals retain no-follow, containment, and byte-limit checks.
+The Pi host owns one managed runtime; cancellation interrupts native command
+fibers and shutdown awaits tracked baseline plus bounded scheduler, process, and
+workspace finalizers before closing its layer scope. The source conformance audit
+restricts Promise workflows to reviewed Pi/TUI and filesystem infrastructure
+boundaries and found no unmanaged service runtimes. Final supported-host,
+dependency/security, and packed-artifact recertification gates protect the
+release branch. Migration must not turn defects or sensitive exception details
+into user-facing output.
+
+## Release authority
+
+Only [Revaz Zakalashvili](https://github.com/revazi) may authorize an npm
+publication or security release. A pull request, automated dependency update,
+CI result, readiness run, Effect migration completion, or third-party review
+does not itself authorize a release. If a vulnerability affects a published
+version, coordinate any deprecation, corrected release, advisory, and bounded post-release verification
+privately before disclosure; npm versions must never be overwritten.