@flancer32/skill-adsm-ctx 0.2.1

package/.github/workflows/flows-app.yaml

@@ -0,0 +1,95 @@
+name: Upload Flows App Config
+
+on: workflow_dispatch
+
+env:
+  PRJ: flows-cfg-skill-adsm-ctx
+  CFG_SRC_DIR: ctx/agent/flows/cfg
+  CFG_ARCHIVE: flows-cfg-skill-adsm-ctx.tar.gz
+  CFG_TARGET_DIR: ${{ vars.FLOWS_CFG_DIR }}
+
+jobs:
+  upload:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+
+      - name: Validate source directory
+        run: |
+          set -e
+
+          if [ ! -d "${{ env.CFG_SRC_DIR }}" ]; then
+            echo "Source directory does not exist: ${{ env.CFG_SRC_DIR }}"
+            exit 1
+          fi
+
+          find "${{ env.CFG_SRC_DIR }}" -mindepth 1 -print -quit | grep -q . || {
+            echo "Source directory is empty: ${{ env.CFG_SRC_DIR }}"
+            exit 1
+          }
+
+      - name: Build configuration archive
+        run: |
+          set -e
+
+          tar -C "${{ env.CFG_SRC_DIR }}" -czf "${{ env.CFG_ARCHIVE }}" .
+
+          ls -lh "${{ env.CFG_ARCHIVE }}"
+
+      - name: Copy archive to server
+        uses: appleboy/scp-action@master
+        with:
+          host: ${{ vars.FLOWS_HOST }}
+          username: ${{ vars.FLOWS_USER }}
+          key: ${{ secrets.FLOWS_SSH_KEY }}
+          source: ${{ env.CFG_ARCHIVE }}
+          target: /tmp
+
+      - name: Replace configuration on server
+        uses: appleboy/ssh-action@master
+        with:
+          host: ${{ vars.FLOWS_HOST }}
+          username: ${{ vars.FLOWS_USER }}
+          key: ${{ secrets.FLOWS_SSH_KEY }}
+          script: |
+            set -e
+
+            TARGET_DIR="${{ env.CFG_TARGET_DIR }}"
+            ARCHIVE="/tmp/${{ env.CFG_ARCHIVE }}"
+
+            if [ -z "$TARGET_DIR" ]; then
+              echo "CFG_TARGET_DIR is empty."
+              exit 1
+            fi
+
+            if [ "$TARGET_DIR" = "/" ]; then
+              echo "Refusing to replace root directory."
+              exit 1
+            fi
+
+            if [ ! -f "$ARCHIVE" ]; then
+              echo "Archive does not exist: $ARCHIVE"
+              exit 1
+            fi
+
+            PARENT_DIR="$(dirname "$TARGET_DIR")"
+            TARGET_NAME="$(basename "$TARGET_DIR")"
+            TIMESTAMP="$(date +%Y%m%d-%H%M%S)"
+            STAGING_DIR="$PARENT_DIR/.${TARGET_NAME}.new-$TIMESTAMP"
+
+            mkdir -p "$PARENT_DIR"
+
+            rm -rf "$STAGING_DIR"
+            mkdir -p "$STAGING_DIR"
+
+            tar -xzf "$ARCHIVE" -C "$STAGING_DIR"
+
+            rm -rf "$TARGET_DIR"
+            mv "$STAGING_DIR" "$TARGET_DIR"
+
+            rm -f "$ARCHIVE"
+
+            echo "Configuration uploaded to: $TARGET_DIR"
+            find "$TARGET_DIR" -maxdepth 3 -type f | sort

package/AGENTS.md

@@ -0,0 +1,112 @@
+# Root Level
+
+- Path: `AGENTS.md`
+- Template Version: `20260702`
+- Changed: `20260702`
+
+## Purpose
+
+This file defines the root-level working rules for the project repository.
+
+This file is the first instruction source for every agent operating within the repository.
+
+## Level Boundary
+
+Defines:
+
+- Root-level working boundaries between the repository, the cognitive context, and the software product.
+- Repository-topology rules needed to work safely when `ctx/` may be mounted separately.
+- Root-level protection and escalation rules for this project.
+
+Does NOT define:
+
+- Product-specific meaning, requirements, or domain knowledge.
+- Implementation-level structure such as source code, runtime details, or filesystem layout.
+- Task-specific instructions, workflows, or local operational procedures.
+
+## ADSM Project Model
+
+An ADSM project consists of two interconnected spaces:
+
+- the **Cognitive Context** located in `./ctx/`
+- the **Software Product** located outside `./ctx/`
+
+The cognitive context is the long-term textual memory of the project.
+
+The cognitive context is the primary communication medium between Humans and Agents working on the project.
+
+The cognitive context is the authoritative knowledge source used by Agents when modifying the project.
+
+The software product is the implementation that must be kept consistent with the cognitive context.
+
+## Human and Agent Roles
+
+The Human defines goals, authorizes work, evaluates outcomes, and evolves the project.
+
+The Agent interprets the cognitive context, performs assigned tasks, modifies the project within task boundaries, and maintains consistency between the cognitive context and the software product.
+
+The Agent operates through text and must treat project documentation as operational memory, not as secondary commentary.
+
+## Cognitive Context
+
+The canonical execution location of the cognitive context is `./ctx/`.
+
+Project-specific knowledge, requirements, architecture, environment descriptions, and implementation guidance are defined within the cognitive context.
+
+The Agent must consult `./ctx/AGENTS.md` for project-specific instructions when `./ctx/` exists.
+
+The Agent must consult `./ctx/docs/filesystem.md` for the project filesystem structure and documentation layout when that file exists.
+
+Documentation distributed with the software product may exist outside `./ctx/`, but it does not replace, redefine, or supersede the cognitive context.
+
+## Bootstrap and Repository Topology
+
+An ADSM project may use one repository or two repositories.
+
+In a one-repository topology, the software product and the cognitive context are versioned together.
+
+In a two-repository topology, the software product and the cognitive context are independent version-controlled repositories, and the cognitive context repository is mounted under `./ctx/`.
+
+The Agent must detect whether `./ctx/` is part of the current repository or an independent repository.
+
+The Agent must preserve repository boundaries.
+
+The Agent must not mix changes between independent repositories.
+
+The Agent must not remove, replace, relocate, or unmount `./ctx/`.
+
+If `./ctx/` does not exist, the Agent may perform bootstrap operations required to create the initial cognitive context structure.
+
+After bootstrap is complete, `./ctx/AGENTS.md` becomes the entry point for project-specific instructions.
+
+## Context and Product Consistency
+
+The cognitive context is the source of truth for the project.
+
+If the cognitive context and the software product diverge, the Agent must treat the cognitive context as authoritative.
+
+The Agent must maintain consistency between the cognitive context and the software product.
+
+The Agent may modify the cognitive context when required by the assigned task and when the modification remains consistent with higher-level context constraints.
+
+The Agent may modify the software product when required by the assigned task and when the modification remains consistent with the cognitive context.
+
+## AGENTS.md Hierarchy
+
+Additional `AGENTS.md` files may exist in subdirectories.
+
+The effective working context of the agent is the aggregate of all `AGENTS.md` files located along the path from the repository root to the target directory.
+
+Rules:
+
+- deeper levels override higher levels within their scope
+- root-level invariants cannot be overridden
+- all levels must remain mutually consistent
+
+## Root File Protection
+
+This file defines root-level project control rules.
+
+The agent must not modify, replace, delete, relocate, or reinterpret this file unless explicitly instructed by the human.
+
+Violation of this rule constitutes an execution error.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,246 @@
+# skill-adsm-ctx
+
+Build and evolve project cognitive context for Agent-Driven Software Management (ADSM).
+
+## Overview
+
+`@flancer32/skill-adsm-ctx` is a private ADSM skill package for initializing, designing, validating, auditing, compressing, and upgrading project cognitive context.
+
+It manages the lifecycle of project context as its primary object. It does not define business requirements, backend architecture, browser architecture, deployment logic, or domain-specific documentation on its own.
+
+This package is developed according to the [ADSM methodology](http://fly.wiredgeese.com/flancer/leanpub/adsm-en/).
+
+The package includes:
+
+- the `adsm-ctx` CLI for lifecycle operations;
+- the `adsm-ctx` skill payload for AI agents;
+- reusable `ctx/` templates for bootstrapping ADSM-compatible projects.
+- working templates for agent-produced reports.
+
+## Purpose
+
+Use this package when you need to:
+
+- initialize a new ADSM-compatible project context;
+- design the context structure for a concrete project;
+- validate whether an existing context follows expected ADSM structure;
+- audit a documentation corpus against ADSM documentation quality criteria;
+- compress a documentation corpus while preserving accepted project meaning;
+- upgrade a context when ADSM conventions evolve.
+
+This package acts as an orchestration layer. It provides generic structure, lifecycle guidance, validation, documentation quality audit guidance, documentation compression guidance, and upgrade entry points. When project-specific context is required, it should direct the agent to use specialized skills when they are available.
+
+The bundled baseline now covers both:
+
+- product-level context, which defines what the system is;
+- architecture-level context, which defines how product intent is realized through structure, behavior, state ownership, integrations, constraints, decisions, and supervision.
+
+## Non-Goals
+
+This package does not:
+
+- invent project requirements or business rules;
+- replace specialized documentation skills;
+- write domain-specific architecture content as if it knew the project;
+- perform automatic semantic scoring or correction of documentation quality;
+- change project meaning during documentation compression;
+- perform destructive upgrades without explicit review.
+
+## Requirements
+
+- Node.js with npm.
+- GitHub SSH access to the repository for global installation from GitHub.
+
+## Global Installation
+
+Install the package globally from GitHub:
+
+```sh
+npm install -g git+ssh://git@github.com/flancer32/skill-adsm-ctx.git
+```
+
+This provides the CLI command:
+
+```sh
+adsm-ctx
+```
+
+To install the skill payload for agent use:
+
+```sh
+adsm-ctx install-skill "$HOME/.agents/skills"
+```
+
+This copies the payload to:
+
+```text
+$HOME/.agents/skills/adsm-ctx
+```
+
+## CLI Usage
+
+Show help:
+
+```sh
+adsm-ctx --help
+```
+
+Initialize a context in the current directory:
+
+```sh
+adsm-ctx init
+```
+
+Design guidance for a project context:
+
+```sh
+adsm-ctx design
+```
+
+Validate an existing project context:
+
+```sh
+adsm-ctx validate
+```
+
+Validate a specific path:
+
+```sh
+adsm-ctx validate <project-root>
+```
+
+Run the upgrade entry point:
+
+```sh
+adsm-ctx upgrade
+```
+
+Install the bundled skill payload:
+
+```sh
+adsm-ctx install-skill <skills-root>
+```
+
+## Lifecycle Modes
+
+### `init`
+
+Creates the minimal ADSM-compatible context structure, starter documents, and `ctx/adsm.json` metadata.
+
+### `design`
+
+Provides guidance for classifying the project, choosing relevant documentation branches, and identifying when specialized ADSM skills should be used.
+
+### `validate`
+
+Checks baseline paths, required documentation levels, required `AGENTS.md` files, metadata, body/skin projection shape, local markdown document links, and lightweight skin-shape heuristics. When the repository provides a deterministic validator, run it and report errors and warnings separately. Validation reports findings without modifying project content.
+
+### `quality-audit`
+
+Guides an agent through evidence-backed review of a documentation corpus against ADSM documentation quality criteria. This is a skill mode, not a CLI command.
+
+The default audit corpus is `ctx/docs/`. Operational context such as `ctx/agent/`, workflow configuration, prompt assets, and generated reports is outside the default corpus unless explicitly requested.
+
+### `documentation-compression`
+
+Guides an agent through controlled rewrite of a documentation corpus to reduce size, improve density, and remove duplication without changing accepted project meaning. This is a skill mode, not a CLI command.
+
+The default compression corpus is `ctx/docs/`. Operational context such as `ctx/agent/`, workflow configuration, prompt assets, generated reports, and runtime materials is outside the default corpus unless explicitly requested.
+
+### `upgrade`
+
+Reads context metadata and reports or applies non-destructive migrations when available. The initial implementation provides the migration mechanism and reports when no migrations apply.
+
+## Workflow
+
+Recommended sequence:
+
+1. Run `adsm-ctx init` in a new project repository.
+2. Run `adsm-ctx design` to shape the context for the actual project.
+3. Use specialized skills where the project needs domain-specific documentation.
+4. Run `adsm-ctx validate` as the deterministic preflight as the context evolves.
+5. Use the skill's `quality-audit` mode only after structural validation passes or leaves warnings only.
+6. Use the skill's `documentation-compression` mode when accepted documentation meaning is stable but the corpus has high attention cost.
+7. Run `adsm-ctx upgrade` when template conventions or schema versions change.
+
+## Documentation Levels
+
+The recommended documentation dependency is:
+
+```text
+product
+  -> architecture
+  -> environment
+  -> code
+```
+
+Use the architecture level once product meaning is clear enough to define stable engineering guardrails.
+
+The bundled architecture templates expect these top-level documents:
+
+- `overview.md`
+- `structure.md`
+- `behavior.md`
+- `state.md`
+- `integration.md`
+- `constraints.md`
+- `decisions.md`
+- `supervision.md`
+
+They are designed for one human plus many agents: body documents stay precise for agentic implementation work, and optional skins stay concise for human semantic control.
+
+## Semantic Skin Languages
+
+Canonical agent-facing documents use ordinary names such as `overview.md` and are written in English unless a project rule says otherwise. Human-facing skins use an explicit language suffix:
+
+```text
+overview.md
+overview.skin.en.md
+overview.skin.ru.md
+```
+
+Use lowercase ISO 639-1 codes (`en`, `ru`, `es`); add a regional tag only for a genuine regional distinction. `overview.skin.md` is invalid. All skins with the same basename form one group with the canonical document, and may adapt the presentation for people rather than be literal translations.
+
+For `AGENTS.md` authoring, `Level Boundary` sections should stay compact and guardrail-oriented. They are intended to prevent likely scope drift, not to become exhaustive specifications.
+
+## Skill And CLI Relationship
+
+The CLI performs local filesystem operations and structural validation.
+
+The skill in `skill/SKILL.md` instructs an AI agent how to use the lifecycle modes, how to avoid inventing project content, how to audit documentation quality, how to compress documentation without changing meaning, and how to route documentation work toward specialized skills when needed.
+
+Documentation quality audit uses `skill/references/documentation-quality-audit.md` and the working report template at `skill/templates/work/report/documentation-quality-audit.md`.
+
+Documentation compression uses `skill/references/documentation-compression.md` and the working report template at `skill/templates/work/report/documentation-compression.md`.
+
+The skill does not directly invoke other skills. It instructs the agent to select and use them when relevant.
+
+## Specialized Skill Orchestration
+
+`adsm-ctx` is intentionally generic. Its design mode should recognize when a project needs specialization such as browser-side web documentation, backend service documentation, data-model documentation, or deployment context.
+
+When a specialized ADSM skill is available, the agent should use it for that area after the generic context baseline is in place.
+
+When no specialized skill is available, this package should create only generic structure and record the specialization gap instead of inventing domain-specific content.
+
+## Local Development
+
+Run the CLI directly from the repository:
+
+```sh
+node ./bin/cli.mjs --help
+```
+
+Run the tests:
+
+```sh
+npm test
+```
+
+## Status
+
+This repository contains a working skeleton intended as a foundation for future ADSM context lifecycle tooling.
+
+## License
+
+Apache-2.0