@niroai/niro 0.15.0 → 0.17.0

package/CHANGELOG.md

@@ -4,6 +4,57 @@ Notable changes to `@niroai/niro`. Dates are release dates.
 
 ## Unreleased
 
+## 0.17.0 — 2026-09-23
+
+### `niro init --defaults` still asks which project
+
+`--defaults` accepts default values: env vars, indexing scope, the project name. It also used to
+skip the "new project, or add to an existing one?" question and always create a new project, which
+put repos in the wrong place for anyone who already had a project for them. Which project is not a
+default value, so in a terminal the question is now asked with `--defaults` too.
+
+Unattended runs are unchanged. With no terminal (CI, a piped script, an agent's shell) there is no
+question and a new project is created, as before. A script that wants an existing project passes
+`--add-to <alias|id>`; `--project-name <name>` still skips the question everywhere.
+
+## 0.16.0 — 2026-09-22
+
+### A reverse proxy's routing table is offered for upload
+
+Most services do not call each other directly. They call a proxy, and a routing table decides who
+really answers. That table is the only place the hop is written down, and the CLI was not offering
+it, so the server never saw it and the graph stopped at the proxy.
+
+Newly offered:
+
+- `nginx.conf`, `haproxy.cfg`, `httpd.conf`, `apache2.conf`
+- compose files named for their environment, not just `docker-compose.yml`: a Traefik routing table
+  lives in container labels, and those labels are routinely in `docker-compose.production.yml`
+- Kubernetes Ingress manifests under the names teams actually use: `ingress.yaml`,
+  `*-ingress.yaml`, `*_ingress.yaml`
+
+Deliberately still NOT offered: every `.yaml`. An Ingress can be in any file, and claiming all of
+them would upload every Helm chart, kustomization and CI file in a repository to find the occasional
+routing table. An Ingress under an unconventional name is a stated limit rather than a silent one.
+
+Envoy was left out on purpose. A file that is uploaded and then read by nothing is cost with no
+benefit, and the server has no Envoy reader yet.
+
+### A drift guard for the config list
+
+`CONFIG_FILENAMES` is a hand-kept copy of the server's list and nothing compared the two.
+`test/configFilenameDrift.test.js` now does, alongside the existing extension guard. This matters
+more than it did: if the copies drift now, the CLI stops offering `nginx.conf`, the server never
+receives it, and every connection through that proxy quietly disappears from the graph. The symptom
+reads as "proxy support is broken" and is nowhere near the list that caused it.
+
+### Upgrade order
+
+The server's filter remains the final say, so either order is safe: an older CLI offers fewer files,
+and a newer CLI against an older server has its extra offers declined. The routing tables reach the
+graph once both sides are current (ai-orchestrator `25131e94` or later). Repositories the server
+clones itself are unaffected by this release; their files never went through the CLI.
+
 ## 0.15.0 — 2026-09-21
 
 ### Twenty more file types are offered for upload

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@niroai/niro",
-  "version": "0.15.0",
+  "version": "0.17.0",
   "description": "Niro \u2014 one package: the niro CLI plus the Niro MCP server (code intelligence for AI coding assistants).",
   "keywords": [
     "niro",

package/src/commands/init.js

@@ -946,10 +946,11 @@ async function scanIndexedChildren(targetDir, opts, resolve = resolveContext) {
  * Decide the TARGET of this onboarding up front, before any repo registration:
  *   - --add-to <alias|id> -> EXISTING: resolve to a real projectId (throws on
  *     ambiguity/not-found via resolveProjectId), attach the new repo to it later.
- *   - --project-name / --defaults / non-interactive -> NEW: derive a free name
- *     exactly as before (unchanged behaviour for scripts and the default path).
+ *   - --project-name / non-interactive -> NEW: derive a free name exactly as
+ *     before (unchanged behaviour for scripts).
  *   - INTERACTIVE with >=1 existing project -> show a numbered menu (new vs each
  *     existing project) so the user can attach instead of always creating new.
+ *     This holds with --defaults too.
  *
  * Returns { projectId, isExisting } or null when the user/flags didn't yield a
  * usable target (caller sets exitCode=1).
@@ -966,10 +967,14 @@ async function resolveTarget({ defaultName, opts }) {
     return { projectId, isExisting: true };
   }
 
-  // Explicit name, --defaults, or a non-interactive shell -> NEW (current path).
+  // Explicit name or a non-interactive shell -> NEW (current path).
   // We only offer the existing-project menu in an interactive shell with at
-  // least one project to pick.
-  if (!opts.projectName && !opts.defaults && !prompt.isNonInteractive()) {
+  // least one project to pick. --defaults does NOT skip it: that flag accepts
+  // default VALUES (env vars, scope, name), and "which project" has no safe
+  // default, so creating a new one silently put repos in the wrong place.
+  // Unattended runs have no terminal, so they still go straight to NEW; a
+  // script that wants an existing project passes --add-to.
+  if (!opts.projectName && !prompt.isNonInteractive()) {
     const existing = await fetchExistingProjects(opts);
     if (existing.length > 0) {
       const chosen = await chooseTarget(existing);

package/src/lib/folderSync.js

@@ -120,6 +120,9 @@ const CONFIG_FILENAMES = new Set([
   "application.yml.example", "application.yml.sample",
   "application.yaml.example", "application.yaml.sample",
   "dockerfile", "docker-compose.yml", "docker-compose.yaml",
+  // A reverse proxy's routing table is the only place the hop from a caller to the service that
+  // really answers is written down. MUST stay in step with SourceFileFilterService.CONFIG_FILENAMES.
+  "nginx.conf", "haproxy.cfg", "httpd.conf", "apache2.conf",
 ]);
 
 const CONFIG_WILDCARD_SUFFIXES = [".properties", ".yml", ".yaml"];
@@ -127,8 +130,19 @@ const CONFIG_WILDCARD_SUFFIXES = [".properties", ".yml", ".yaml"];
 // True for committed config/property/template files that carry env-var DEFAULTS,
 // false for secret-bearing files (bare .env, .env.local, .env.production, and
 // arbitrary *.properties). `lower` is the already-lowercased filename.
+// Routing configs whose filename is a convention rather than a fixed name. Deliberately narrow:
+// making every .yaml eligible would upload every chart and CI file in a repo. MUST stay in step with
+// SourceFileFilterService.isRoutingManifestName.
+function isRoutingManifestName(lower) {
+  if (!lower.endsWith(".yml") && !lower.endsWith(".yaml")) return false;
+  if (lower.startsWith("docker-compose") || lower.startsWith("compose.")) return true;
+  const stem = lower.slice(0, lower.lastIndexOf("."));
+  return stem === "ingress" || stem.endsWith("-ingress") || stem.endsWith("_ingress");
+}
+
 function isConfigName(lower) {
   if (CONFIG_FILENAMES.has(lower)) return true;
+  if (isRoutingManifestName(lower)) return true;
   // Spring profile files: application-<profile>.{properties,yml,yaml}, profile
   // non-empty (reject "application-.properties").
   const prefix = "application-";