# Reported issues for ark

Pod holds 6 of 6 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to [ark](/mcp/ark).

## Most discussed

### Dogfood: start --apply exits 0 when pnpm install fails (minimumReleaseAge / workspace)

## Correction (dogfood instrumentation)
Re-ran without `| tee`. Real: `arkgate start --apply` → **exit 1** when `pnpm add` fails on `minimumReleaseAge`. Exit-code claim was wrong (tee mask).

## Still real — keep open for UX/docs
1. Docs “Start in one minute” leads with `npm install -D arkgate` which hard-fails on `workspace:*` monorepos (`EUNSUPPORTEDPROTOCOL`). Stranger path needs `npx` / `pnpm add -w` first.
2. On `ERR_PNPM_NO_MATURE_MATCHING_VERSION`, recovery text is honest but still dumps…

[Read the thread](https://github.com/pedroknigge/arkgate/issues/268) · 2026-09-17 · closed · 2 comments

### upgrade --apply refuses with an empty reason when a gitignored per-machine managed asset (.mcp.json) is missing in a fresh worktree

**Priority:** P1 · Contener (keep the pin current) · blocks upgrade in every fresh git worktree

## What happens

Field session in a user repo (git worktree, pnpm, hosts claude/codex/cursor/grok), `arkgate upgrade` 4.8.18 → 4.8.20, 2026-09-25 ~12:55 UTC-3.

`.mcp.json` is a managed asset, but the repo gitignores it (`.gitignore:40: .mcp.json`) because it is per-machine. A new worktree therefore never has it.

1. Preview: `summary.states = {current: 20, customized: 5, missing: 1}`, `blocked: 1`.…

[Read the thread](https://github.com/pedroknigge/arkgate/issues/311) · 2026-09-25 · closed · 1 comment

### start --apply can succeed while package install fails; next doctor command 404s

## Summary
On a brownfield tree that already has a yarn lockfile, `arkgate start --apply` can write host/CI mutations successfully, edit `package.json` to pin arkgate, then run the detected package manager (`yarn add -D arkgate@…`) and get a non-zero exit. Apply still exits 0 and prints that mutations were applied. After that failed install, local `node_modules` may lack the arkgate bins, so the documented next step `npx arkgate-check --doctor` fails with an npm 404 for a phantom package named…

[Read the thread](https://github.com/pedroknigge/arkgate/issues/258) · 2026-09-15 · closed · 1 comment

### Write hook denies imports that ark-check allows: layer resolution ignores explicit file patterns when a broader glob also matches

> Written by a Claude Code agent run by @pedroknigge, from a real session on a private repo (Amarilla Platform, arkgate `4.8.14`). Everything below was measured in that session, not inferred.

## Summary

The **write hook** (`arkgate-mcp --hook`) and **`ark-check`** disagree on layer resolution when a path is matched by *both* an explicit file pattern and a broader glob. The hook resolves by the broad glob; `ark-check` gives precedence to the explicit file pattern. So the hook denies writes…

[Read the thread](https://github.com/pedroknigge/arkgate/issues/237) · 2026-09-08 · closed · 1 comment

### Dogfood: published README dual-truth — claims npm latest is 4.8.16 while package is 4.8.17

## Context
Published npm package `arkgate@4.8.17` (verified via `npm view` / `npx arkgate --version`).

## Observed
Packaged README still says:
> **ArkGate 4.8.17** is prepared on this tree; npm `latest` remains **4.8.16** until `publish-npm` for `v4.8.17`.

Reality: `dist-tags.latest = 4.8.17`.

## Why it matters
Classic dual-truth pin. Strangers (and dogfood) cannot trust version banners on the published artifact.

## Suggested fix
Publish-time rewrite / CI check that forbids “latest remains…

[Read the thread](https://github.com/pedroknigge/arkgate/issues/270) · 2026-09-17 · closed · 0 comments

### Dogfood: monorepo start over-broad DomainModel globs → dual-match noise + false-green coverage

## Context
Field dogfood on a large third-party TS monorepo (anonymized). `arkgate start --apply` + monorepo preset.

## Observed
Generated `ark.config.json` put extremely broad DomainModel patterns (e.g. whole app roots like `api/**` and `client/**` alongside finer globs). Doctor then reported:
- Governed 98% (looks healthy)
- Dual-match: **265** files match multiple layers
- Hundreds of `DomainModel → ambient global` / cross-layer findings that are mostly misclassification noise

Coverage %…

[Read the thread](https://github.com/pedroknigge/arkgate/issues/269) · 2026-09-17 · closed · 0 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/pedroknigge/ark-runtime-kernel/issues).