Skip to content

As a developer, I want to set up nabledge-1.x knowledge generation infrastructure so that kc.sh gen 1.4/1.3/1.2 can run #189

@kiyotis

Description

@kiyotis

Situation

nabledge-6 and nabledge-5 knowledge generation works end-to-end with `kc.sh gen 6` and `kc.sh gen 5`. Nablarch 1.x (v1.4, v1.3, v1.2) are legacy versions still used in production, but no infrastructure exists to run the same pipeline for these versions.

Pain

`kc.sh gen 1.4` cannot run because:

  • `.lw/nab-official/v1.4/` does not exist (no symlink to local docs)
  • knowledge-creator does not accept `--version 1.4`, `1.3`, or `1.2`
  • No catalog files (.cache/v1.4/catalog.json, etc.)
  • No mapping files (mappings/v1.4.json, etc.)
  • No skill structures (.claude/skills/nabledge-1.4/, etc.)

Benefit

Success Criteria

  • Symlinks exist: `.lw/nab-official/v1.4/1.4_maintain`, `.lw/nab-official/v1.3/1.3_maintain`, `.lw/nab-official/v1.2/1.2_maintain`
  • knowledge-creator accepts `--version 1.4`, `--version 1.3`, `--version 1.2` (run.py choices updated)
  • kc.sh passes 1.x versions through to run.py correctly
  • Catalog files created: `.cache/v1.4/catalog.json`, `.cache/v1.3/catalog.json`, `.cache/v1.2/catalog.json`
  • Mapping files created: `mappings/v1.4.json`, `mappings/v1.3.json`, `mappings/v1.2.json`
  • Skill structures created: `.claude/skills/nabledge-1.4/`, `.claude/skills/nabledge-1.3/`, `.claude/skills/nabledge-1.2/`
  • E2E tests cover v1.4/v1.3/v1.2 with same assertions as v5/v6
  • `kc.sh gen 1.4 --dry-run` completes without error
  • README and setup.sh document the symlink process for 1.x versions

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions