docs: restore legacy task backing and document successor transition
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e77b-9d43-7432-9301-e5cb6ad05ef6
This commit is contained in:
parent
d741661679
commit
8b9f599931
6 changed files with 189 additions and 1 deletions
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
## Repo Identity
|
||||
|
||||
**Purpose:** Markitect Main - (fill in purpose)
|
||||
**Purpose:** Legacy markdown and knowledge-artifact platform; preserve migration evidence and maintain remaining integrations during the successor transition (see INTENT.md).
|
||||
|
||||
**Domain:** communication
|
||||
**Repo slug:** markitect-main
|
||||
|
|
|
|||
33
INTENT.md
Normal file
33
INTENT.md
Normal file
|
|
@ -0,0 +1,33 @@
|
|||
# Markitect Main — intent
|
||||
|
||||
Markitect Main is the legacy integrated markdown and knowledge-artifact
|
||||
platform. It preserves implementation history, examples, and evidence needed
|
||||
to finish migration to the successor repositories.
|
||||
|
||||
The May 23 [successor gap assessment](docs/successor-gap-assessment.md) records
|
||||
the retirement direction. Retirement is **not complete**: the disposition of
|
||||
the render/asset stack, the older `markitect/spaces/` abstraction, and the
|
||||
project-operations modules still needs explicit decisions. This document does
|
||||
not authorize deleting those components or claim successor feature parity.
|
||||
|
||||
New core development belongs with the relevant successor:
|
||||
|
||||
| Repository | Responsibility |
|
||||
| --- | --- |
|
||||
| `markitect-tool` | Markdown syntax and structured-document primitives; adapter contracts |
|
||||
| `kontextual-engine` | Headless knowledge operations, persistence, workflows, query and assessment |
|
||||
| `infospace-bench` | Concrete infospaces, evaluation methodology and reference pilots |
|
||||
| `markitect-filter` | Source-format ingestion adapters |
|
||||
| `markitect-quarkdown` | Quarkdown rendering/export adapter |
|
||||
| `testdrive-jsui` | Standalone JavaScript editor library and its package releases |
|
||||
|
||||
Work retained here is maintenance needed for existing consumers, evidence-based
|
||||
migration and retirement decisions, and verification of Markitect's integration
|
||||
with pinned dependencies. The current publication coordination is tracked in
|
||||
[MARKITECT-WP-0002](workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md).
|
||||
Package repair and publication belong to `testdrive-jsui`; Markitect view/edit
|
||||
integration evidence belongs here.
|
||||
|
||||
Keep historical evidence and existing task identities intact. Prefer finishing
|
||||
existing work over expanding the monolith. Scope changes and retirement require
|
||||
an explicit decision rather than an inference from an old roadmap.
|
||||
36
README.md
Normal file
36
README.md
Normal file
|
|
@ -0,0 +1,36 @@
|
|||
# Markitect Main
|
||||
|
||||
Legacy Python markdown and knowledge-artifact platform, with a JavaScript
|
||||
editor integration. The repository is transitioning to successor repositories;
|
||||
it has not been fully retired. Start with [INTENT.md](INTENT.md) for current
|
||||
responsibilities and the successor map.
|
||||
|
||||
## Current work
|
||||
|
||||
- [Publication coordination](workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md)
|
||||
is blocked on TestDrive package and release evidence plus Markitect integration
|
||||
verification. Its readiness definition and repository-structure decision are
|
||||
complete. The remaining tasks retain their original State Hub identities.
|
||||
- [Successor gap assessment](docs/successor-gap-assessment.md) identifies pending
|
||||
decisions about rendering/assets, the older spaces abstraction, and
|
||||
project-operations code. It is an assessment, not permission to remove code.
|
||||
- [WORK-RECORDS.md](WORK-RECORDS.md) is the generated task index;
|
||||
[workplans/](workplans/) contains the authoritative task records.
|
||||
|
||||
## Working with the legacy code
|
||||
|
||||
The [Makefile](Makefile) defines `make setup`, `make test`, `make lint`, and
|
||||
`make build`; `make help` lists the available commands. These describe the
|
||||
legacy workflow, not a claim that the full suite passes in a fresh checkout.
|
||||
|
||||
Capabilities are Git submodules. Inspect `git submodule status` before using
|
||||
capability targets. The TestDrive submodule was uninitialized during the
|
||||
September 28 review, so `make testdrive-jsui-test-all` was unavailable. Its
|
||||
legacy URL in [.gitmodules](.gitmodules) may need a local override to the
|
||||
current forge before initialization. Verify the pinned commit and dependency
|
||||
setup before running the integration checks. Do not publish the root npm
|
||||
package as the TestDrive library.
|
||||
|
||||
See [AGENTS.md](AGENTS.md) for repository and State Hub procedures,
|
||||
[INTRODUCTION.md](INTRODUCTION.md) for historical product concepts, and
|
||||
[SCOPE.md](SCOPE.md) for the legacy capability inventory.
|
||||
5
SCOPE.md
5
SCOPE.md
|
|
@ -1,5 +1,10 @@
|
|||
# SCOPE
|
||||
|
||||
> Current disposition (2026-09-28): this is the legacy capability inventory.
|
||||
> [INTENT.md](INTENT.md) governs the retirement transition and successor
|
||||
> responsibilities. The historical activity and version statements below are
|
||||
> not current release or migration-completion evidence.
|
||||
|
||||
> This file helps you quickly understand what this repository is about,
|
||||
> when it is relevant, and when it is not.
|
||||
> It is intentionally lightweight and may be incomplete.
|
||||
|
|
|
|||
|
|
@ -14,3 +14,12 @@
|
|||
| task | MARKITECT-WP-0001-T02 | done | — | workplans/MARKITECT-WP-0001-statehub-bootstrap.md |
|
||||
| task | MARKITECT-WP-0001-T03 | done | — | workplans/MARKITECT-WP-0001-statehub-bootstrap.md |
|
||||
| task | MARKITECT-WP-0002-T01 | done | — | workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md |
|
||||
| task | MARKITECT-WP-0002-T02 | done | — | workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md |
|
||||
| task | MARKITECT-WP-0002-T03 | wait | — | workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md |
|
||||
| task | MARKITECT-WP-0002-T04 | wait | — | workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md |
|
||||
| task | MARKITECT-WP-0002-T05 | wait | — | workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md |
|
||||
| task | MARKITECT-WP-0002-T06 | wait | — | workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md |
|
||||
| task | MARKITECT-WP-0002-T07 | wait | — | workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md |
|
||||
| task | MARKITECT-WP-0002-T08 | wait | — | workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md |
|
||||
| task | MARKITECT-WP-0002-T09 | wait | — | workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md |
|
||||
| task | MARKITECT-WP-0002-T10 | wait | — | workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md |
|
||||
|
|
|
|||
|
|
@ -43,3 +43,108 @@ package owner must resolve its missing advertised declaration file, validate
|
|||
packed consumer entry points, and supply release evidence. Markitect's pinned
|
||||
submodule must also be initialized and its view/edit integration verified.
|
||||
No release tag, registry publication, or browser acceptance is claimed.
|
||||
|
||||
|
||||
The following blocks restore file backing for the nine **existing** legacy P.1–P.9
|
||||
tasks. Their State Hub UUIDs are preserved verbatim; no task is being created.
|
||||
The file record IDs provide stable local references. The roadmap retains the
|
||||
historical checklist and the current release acceptance criteria.
|
||||
|
||||
## P.1 — Decide repository structure (monorepo vs standalone)
|
||||
|
||||
```task
|
||||
id: MARKITECT-WP-0002-T02
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "81c03377-9083-42eb-be33-d202069afc02"
|
||||
```
|
||||
|
||||
2026-09-28: Done: `.gitmodules` and the existing standalone checkout establish Option B. Publish the library from `testdrive-jsui`, not the Markitect root package.
|
||||
|
||||
## P.2 — Verify Markitect integration still works
|
||||
|
||||
```task
|
||||
id: MARKITECT-WP-0002-T03
|
||||
status: wait
|
||||
priority: high
|
||||
state_hub_task_id: "f518601b-396a-46a3-a5af-152bde48c313"
|
||||
```
|
||||
|
||||
2026-09-28: Waiting for the pinned TestDrive submodule to be initialized and the JS/Python checks and actual Markitect view/edit behavior to be verified. The current checkout has no discoverable integration make target.
|
||||
|
||||
## P.3 — Resolve STANDALONE_PLAN.md status
|
||||
|
||||
```task
|
||||
id: MARKITECT-WP-0002-T04
|
||||
status: wait
|
||||
priority: medium
|
||||
state_hub_task_id: "d700098c-449d-44ba-ab02-cc3571bf6587"
|
||||
```
|
||||
|
||||
2026-09-28: Waiting for the standalone package owner to reconcile its Python standalone plan. npm bundles do not establish Python packaging acceptance.
|
||||
|
||||
## P.4 — Pack and dry-run publish
|
||||
|
||||
```task
|
||||
id: MARKITECT-WP-0002-T05
|
||||
status: wait
|
||||
priority: high
|
||||
state_hub_task_id: "94dd2a30-fa38-471e-b19a-ed0913579524"
|
||||
```
|
||||
|
||||
2026-09-28: Waiting for P.2/P.3 and standalone package fixes: resolve the missing advertised declaration file and verify ESM, CommonJS, browser and CSS consumption from an actual packed tarball. Run lint, tests, production build and publish dry-run; retain artifact evidence.
|
||||
|
||||
## P.5 — Create v1.0.0 release tag
|
||||
|
||||
```task
|
||||
id: MARKITECT-WP-0002-T06
|
||||
status: wait
|
||||
priority: medium
|
||||
state_hub_task_id: "d7c2ce00-00ad-431c-b036-64e727e49e48"
|
||||
```
|
||||
|
||||
2026-09-28: Waiting for a verified candidate. Create the matching release tag only in the standalone repository after checking version availability and aligning manifest, lockfile and changelog.
|
||||
|
||||
## P.6 — Publish to npm and verify CDN
|
||||
|
||||
```task
|
||||
id: MARKITECT-WP-0002-T07
|
||||
status: wait
|
||||
priority: high
|
||||
state_hub_task_id: "8bcde75e-bca2-428e-893f-1d88036f746c"
|
||||
```
|
||||
|
||||
2026-09-28: Waiting for package and integration gates, a verified tag, registry ownership/access, and npm/CDN publication receipts from the standalone maintainer.
|
||||
|
||||
## P.7 — Fresh install test in clean environment
|
||||
|
||||
```task
|
||||
id: MARKITECT-WP-0002-T08
|
||||
status: wait
|
||||
priority: high
|
||||
state_hub_task_id: "61d14b53-4ecf-4c0a-a676-b5530f706378"
|
||||
```
|
||||
|
||||
2026-09-28: Waiting for publication. Install the published version and supported marked peer in an isolated consumer; verify initialization, edit/view behavior and styles without source-checkout references.
|
||||
|
||||
## P.8 — Create GitHub release
|
||||
|
||||
```task
|
||||
id: MARKITECT-WP-0002-T09
|
||||
status: wait
|
||||
priority: medium
|
||||
state_hub_task_id: "22d0cf0e-34a1-49f7-b1c1-7c5a1ae9ce16"
|
||||
```
|
||||
|
||||
2026-09-28: Waiting for publication evidence. Use the standalone repository’s actual forge; the historical GitHub destination is not established.
|
||||
|
||||
## P.9 — Add npm badges to README and monitor
|
||||
|
||||
```task
|
||||
id: MARKITECT-WP-0002-T10
|
||||
status: wait
|
||||
priority: low
|
||||
state_hub_task_id: "75e785ac-4e35-4789-bcc2-d542db96d998"
|
||||
```
|
||||
|
||||
2026-09-28: Waiting for verified publication. Add accurate badges in the standalone README and name responsibility for the one-week follow-up.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue