TinyChain-Inc / TinyChain-Inc/client
[JS][J2] Implement Library, Service, Class manifest authoring and lifecycle helpers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 32
Description
Objective
Implement typed JavaScript authoring and supported install/invoke/inspect lifecycle helpers for Library, Service, and Class without duplicating Rust authorization or deployment semantics.
Acceptance criteria
- Builders default to no dependencies/capabilities and serialize canonically.
- Dependency locks, artifact identity and authorization declarations consume normative fixtures.
- Supported install/invoke/inspect/uninstall operations match Python behavior and typed errors.
- Unsupported backend lifecycle operations fail visibly and remain marked blocked in the matrix.
- Node and browser bundles expose only appropriate credential/session options.
Parent: #74
Tembo execution contract
automation:
eligible: true
executor_profile: tembo
readiness: blocked
primary_repository: TinyChain-Inc/client
base_branch: main
writable_scope:
- js/src/**
- js/tests/**
- js/README.md
- js/ROADMAP.md
- web/tests/**
prerequisites:
- "#85"
- "TinyChain-Inc/tcv2#53"
- "TinyChain-Inc/tcv2#56"
concurrency_group: js-library-lifecycle
required_commands:
- "cd web && npm ci"
- "cd web && npm run test:all"
external_actions: none
draft_pr_only: true
completion_authority: human
visual_validation:
required: false
evidence: []
budget:
size: large
max_revisions: 3
max_wall_minutes: 120
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the prerequisites (#85, tcv2#53, and tcv2#56), then inspect js/src and js/tests alongside the Python behavior referenced by the issue. Run cd web && npm ci and cd web && npm run test:all; done means the listed Library, Service, and Class authoring and lifecycle criteria pass, unsupported operations remain visibly blocked, and Node/browser credential options are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, python, rust
- Domain
- api, backend-api-design, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100