@cad0p/pi-steering 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,36 @@
+# Changelog
+
+All notable changes to `@cad0p/pi-steering` are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project will adhere to [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
+once `v0.1.0` publishes to npm.
+
+## [0.1.0] — 2026-08-10
+
+### Added
+
+- First public npm release as `@cad0p/pi-steering` (scoped — reverses the ADR's unscoped-name decision per maintainer request).
+- `publishConfig.access: public` for OIDC/CLI publishing.
+
+### Changed
+
+- `unbash-walker` dependency: `github:cad0p/unbash-walker` → `@cad0p/unbash-walker ^0.1.0`.
+
+## [Unreleased] — pre-publish (v0.1.x)
+
+### Changed
+
+- Monorepo split (2026-08-10): this repo is now `cad0p/pi-steering` (renamed from `pi-steering-hooks`); `unbash-walker`, `pi-steering-commit-format`, and `pi-steering-flags` moved to their own repos. The git plugin is now **opt-in** — `DEFAULT_PLUGINS` is empty; declare `plugins: [gitPlugin]` (import from `pi-steering/plugins/git`) to register it. This restores compile-time typo-checking on `disabledRules` / `disabledPlugins` for configs that declare their plugins (runtime defaults and type-level visibility can no longer diverge).
+
+### Breaking
+
+- Factory-time throw on any warning-class loader/merger diagnostic by default. Opt out via `defineConfig({ failOnWarnings: false })`.
+- Tracker-name collisions are now detected at config-load time and surfaced as an `error`-class diagnostic that aggregates with other diagnostics (single thrown error per factory invocation, not multiple sequential throws). Errors always throw regardless of `failOnWarnings` (see schema JSDoc).
+- `disabledPlugins` / `disabledRules` are now applied BEFORE cross-layer collision detection in `buildConfig`. A user resolving a duplicate-plugin warning by adding the plugin to `disabledPlugins` now sees the warning go away.
+- `loadConfigs(cwd)`, `buildConfig(layers, defaults?)`, `loadSteeringConfig(cwd, defaults?)` return shape changed (now include `diagnostics` field). Internal `buildSessionRuntime` return shape changed. Bridge default factory is now async.
+- `PluginResolveWarning` interface renamed to `SteeringDiagnostic` with extended `kind` union (covers loader-side categories) and required `type: "warning" | "error"` field.
+
+### Changed
+
+Visibility improvement: some plugin-merger warnings (predicate / observer / rule / extension-orphan collisions) were previously collected internally and never logged. They now flow through the same `failOnWarnings` policy as loader-side warnings: aggregated into the factory throw under the default, or emitted to `console.warn` with the opt-out.

package/LICENSE

@@ -0,0 +1,29 @@
+MIT License
+
+Copyright (c) 2026 Pier Carlo Cadoppi (cad0p)
+  — monorepo scaffolding, effective-cwd walker, and unbash-walker packaging
+
+Copyright (c) 2026 Jason Diamond (jdiamond)
+  — portions of unbash-walker ported from jdiamond/pi-guard (MIT)
+
+Copyright (c) 2026 samfp
+  — fork parent: samfoy/pi-steering-hooks (original sources not currently
+    present in this codebase; retained for git-fork-history)
+
+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.