Nodal Analytics 1.7.4

Nodal Analytics 1.7.4 fixes merge approval in context repositories scaffolded by 1.7.2 and 1.7.3.

Changes

• Fix merge approval never recording in scaffolded repos. The governed content digest now uses the same file scope as the merge snapshot, so the shipped evals/seeds/_seed-template.yaml (and other non-contract files such as .gitkeep) no longer make the checkout and the merged revision disagree. A regression test covers both files.
• Add README instructions for updating an existing installation.
• Update package and marketplace versions to 1.7.4.

Upgrade notes

Context repositories created from 1.7.2 or 1.7.3 could not record merge approvals: the approval step failed with a generic "authority/evidence unavailable or invalid" error, and governed reads stayed blocked. After updating the plugin and running a support upgrade, merge the next reviewed change to record the first approval.

Content digests change once for repositories with non-contract files under governed directories. Existing freshness records then need one fresh source check: any push to the approval branch or a manual context-drift run.

Validation

All PR checks and post-merge package CI passed, including the 37-file direct test suite and payload synchronization. The fix was confirmed in a live context repository, where the first merge approval was recorded once the template no longer split the digests. The manual install, clean-room and Desktop smoke checks in the release checklist were not run for this release.

Includes #69, #70 and #71.

Full diff: v1.7.3...v1.7.4

Nodal Analytics 1.7.3

Nodal Analytics 1.7.3 removes leftover authored approval-status guidance following the ACF 0.3 merge-approval migration.

Changes

• Remove draft/confirmed approval markers from new Markdown templates and status columns from ownership rosters.
• Update interview, extraction, drift-review, verification and worked-example guidance: analyst answers provide review evidence; protected human-reviewed merge and live authority determine definition approval.
• Track unresolved questions through placeholders, review notes and structured open decisions rather than authored approval labels.
• Prevent drift patches from adding legacy status markers to unmarked query patterns. Explicit legacy markers remain supported for migration handling.
• Regenerate the installed-skill payload and update package and marketplace versions to 1.7.3.

Upgrade notes

Update the installed Nodal Analytics plugin to receive the corrected instructions and templates. Existing customer-authored Markdown is not automatically rewritten. Review any remaining approval-status fields or comments in existing context explicitly; preserve historical review metadata and result-verification evidence.

Runtime eligibility and execution-result statuses remain supported. This release does not remove protected merge approval, live freshness checks, or legacy migration compatibility.

Validation

All PR checks and post-merge package CI passed. Validation includes the 37-file direct test suite, regression tests for unmarked and explicit legacy patterns, generated Markdown/ownership rosters, payload synchronization, skill lint, package validation, and repository/isolated-skill scaffold checks.

Includes #68.

Full diff: v1.7.2...v1.7.3

Nodal Analytics 1.7.2

This release includes all changes since 1.6.4: the ACF 0.3 migration,
merge-based approval, adversarial-review fixes and customer workflow relocation.
Versions 1.7.0 and 1.7.1 were superseded before publication.

• Move customer approval and drift workflows into the context template so they
  no longer execute in the package source repository. Fresh scaffolds and support
  upgrades still install both workflows under .github/workflows/ in customer
  repositories, with their existing approval and freshness behavior unchanged.

• Correct adversarial-review regressions in CI revision identity and skip exits,
  clearance inheritance, post-merge freshness, deterministic/clean exports, scoped
  governed consumption, dbt lineage, method literals, merge approval history,
  notebook rollback, routing, simulation and numeric snapshot row keys.

• Replace authored definition approval with protected human-reviewed merge and
  revision-bound live authority checks. Keep branch testing explicitly unapproved.

• Persist stale blocks independently of repair PRs; propagate through dependencies
  and require reviewed, checked, revision-specific clearance with retained history.

• Migrate shipped legacy content with owner-authorized admission, preserve review
  history, separate result verification, and verify exports against approved sources.

• Adopt ACF 0.3 per-metric YAML, shared fragments, aliases and families, review
  history, explicit blockers, ratio policies and cross-domain dependencies.
  Retire ACF 0.2 and legacy metric layouts immediately; provide a one-time,
  comment-preserving YAML converter with backups and conflict protection.

• Add governed methods, static notebook import, and independent notebook/method
  execution comparisons with separate human confirmation and revision checks.

• Match questions structurally and report definition, slicing and verification
  coverage separately. Add negative seeds, reviewed variants and resumable
  observed-demand interviews; keep answer keys out of answer generation.

• Add encrypted approved SQL, customer-controlled regression execution,
  dependency-aware drift review proposals, gated seed re-grading and optional
  semantic warnings. Missing capabilities are reported, never counted as passes.

• Preserve quick simulated-analyst runs and resume, with private draft-capture
  summaries and no fabricated approval or execution evidence. Update package
  guidance and scaffolds, and add a complete fictional ACF 0.3 worked example.

• Report incoming authoring-template differences during support upgrades while
  preserving customer instructions, configuration, evidence and lineage baseline.

• Add behavioral evals for family choices, method fidelity, open-decision blockers
  and missing-data declines, retaining the should-not-fire control and ablation.

• Live host, warehouse, dashboard and customer notebook acceptance remains an
  opt-in maintainer check; offline tests do not establish those results.

Upgrade notes:

• Existing context repositories need an explicit ACF 0.3 migration and support
  upgrade; updating the plugin alone does not migrate authored context. Back up
  existing content and review the conversion before merging. Admission of legacy
  drafts requires each repository owner's authorization.
• Production consumers require the protected approval branch, governance state,
  workflow identity and trusted live reader described in
  GOVERNANCE.md. Conversion alone grants no live approval.
• ACF_BRANCH_TEST=1 permits local testing of proposed context only. Remove it
  for production use and verify approval and freshness through the live authority.

Validation: all 37 direct test files passed, along with package validation, payload synchronization and repository/isolated-skill scaffold checks. The maintainer reported successful manual Claude/Codex and simulated-analyst testing. Live production governance, warehouse/dashboard/notebook acceptance and the full behavioral ablation suite are not claimed by these checks.

Includes #65, #66 and #67.

Nodal Analytics 1.6.4

1.6.4

• Preserve the original substantive business request through clarification and approval, including later acknowledgments such as “yes, continue.”
• Record the approved clarified interpretation separately when the tool permits question text.
• Carry supplied question/plan references and native client lineage across delegated analytics work. Unknown IDs remain omitted; transcripts are never collected.

Validation: all 16 executable test files, skill lint, ACF validation, payload synchronization, strict Claude plugin validation, Codex package validation, and repository/isolated-skill scaffold checks passed. Tool package CI passed on the tagged main commit.

Attribution remains optional and depends on advertised gateway fields and supplied context. Live native multi-agent correlation and conversation-resume acceptance remain operator-run.

Nodal Analytics 1.6.3

1.6.3

• Add privacy policy and support links to the Claude plugin manifest for the
  plugin directory listing.

Nodal Analytics 1.6.2

1.6.2

• Declare the Nodal logo as the Claude plugin directory listing icon.

1.6.1

• Prepare OpenAI directory metadata with a compliant subtitle, support link,
  desktop-only execution requirement, and guided setup after installation.
• Refresh submission instructions and release notes, including clean-package
  checks and the separate user-configured warehouse connection requirement.
• Point the Launch subscription link at the Nodal-branded checkout domain.

Nodal Analytics 1.6.0

v1.6.0

Nodal Analytics 1.6.0: ACF 0.2 expressions

Nodal Analytics 1.5.4

Nodal Analytics 1.5.4 adds portable Agent Plugins packaging for OpenAI’s universal plugin directory while retaining Codex and Claude compatibility.

• Add the portable manifest and production-ready Nodal logo.
• Add public privacy, terms, and support pages.
• Add OpenAI listing copy, starter prompts, release notes, and reproducible reviewer cases for the skills-only submission.
• Cross-link the README and docs to the quickstart and live verification demo.

Validation: all 15 direct test files passed. Skill lint, ACF schema validation, payload synchronization, strict Claude marketplace validation, Codex manifest/marketplace validation and plugin listing, and repository plus isolated installed-skill scaffold smoke tests passed. Tool package CI passed on the release commit. Authenticated host, warehouse, and dashboard integration checks were not run in this release pass.

Full changelog: v1.5.3...v1.5.4

Nodal Analytics 1.5.3

Interview progress instructions now require a fresh indicator immediately before every question, including selection dialogs, follow-ups, and verification prompts.

• Reinforce the answer → update counts → display progress → ask loop in full interviews and test drives.
• Show a fallback when counts need rebuilding, including after interruptions.
• Preserve domain-round estimates across stage transitions.

Validation: all 15 direct test files passed, including plugin/marketplace and isolated scaffold checks. Skill lint, schema validation, payload synchronization, and strict Claude marketplace validation passed. Live interview adherence and host/warehouse integration were not tested in this release pass.

Nodal Analytics 1.5.2

Full interviews and quick test drives now show a combined text progress indicator with the current stage, answered questions or completed core topics, and an adaptive estimate of questions remaining.

• Explain increases when answers introduce follow-ups.
• Keep deferred topics outside the quick-test budget.
• Show live-verification progress separately from interview questions.

Validation: all 15 direct test files passed, including plugin/marketplace and isolated scaffold checks. Skill lint, schema validation, payload synchronization, and strict Claude marketplace validation passed. Live host and warehouse integration tests were not run.